Connecting an origin group to a resource

If you do not have the Yandex Cloud command line interface yet, install and initialize it.

The folder specified in the CLI profile is used by default. You can specify a different folder using the --folder-name or --folder-id parameter.

1. View a description of the CLI create resource command:

   yc cdn resource create --help
   

2. Get a list of all origin groups in the default folder:

   yc cdn origin-group list --format yaml
   

   Result:

   - id: "90209"
     folder_id: b1g86q4m5vej********
     name: test-group-1
     use_next: true
     origins:
     - id: "561547"
       origin_group_id: "90209"
       source: www.example2.com
       enabled: true
       backup: true
     - id: "561546"
       origin_group_id: "90209"
       source: www.example1.com
       enabled: true
   - id: "90208"
     folder_id: b1g86q4m5vej********
     name: test-group
     use_next: true
     origins:
     - id: "561545"
       origin_group_id: "90208"
       source: www.a2.com
       enabled: true
       backup: true
     - id: "561544"
       origin_group_id: "90208"
       source: www.a1.com
       enabled: true
   

3. Create a resource with the connected origin group:

   yc cdn resource create --cname <resource_domain_name> \
     --origin-group-id <origin_group_ID> \
     --origin-protocol https
   

   Where:

   • --origin-group-id: Origin group ID.
   • --origin-protocol: Protocol for origins.

   Result:

   id: bc855oumelrq********
   folder_id: b1g86q4m5vej********
   cname: res1.example.com
   created_at: "2022-01-15T15:13:42.827643Z"
   updated_at: "2022-01-15T15:13:42.827671Z"
   active: true
   options:
     edge_cache_settings:
       enabled: true
       default_value: "345600"
     cache_http_headers:
       value:
       - accept-ranges
       - cache-control
       - connection
       - content-encoding
       - content-length
       - content-type
       - date
       - etag
       - expires
       - keep-alive
       - last-modified
       - server
       - vary
     stale:
       enabled: true
       value:
       - error
       - updating
     allowed_http_methods:
       value:
       - GET
       - POST
       - HEAD
       - OPTIONS
   origin_group_id: "90208"
   origin_group_name: test-group-22
   origin_protocol: HTTPS
   ssl_certificate:
     type: DONT_USE
     status: READY
   

   For more information about the yc cdn resource create command, see the CLI reference.

If you don't have Terraform, install it and configure the Yandex Cloud provider.

1. Describe the parameters of the yandex_cdn_resource resource in the configuration file:

   Here is an example of the configuration file structure:

   provider "yandex" {
     token     = "<OAuth_token>"
     cloud_id  = "<cloud_ID>"
     folder_id = "<folder_ID>"
     zone      = "<default_availability_zone>"
   }
   
   resource "yandex_cdn_resource" "my_resource" {
     cname = "<resource_domain_name>"
     active = true
     origin_protocol = "https"
      origin_group_id = <origin_group_ID>
   }
   

   For more information about the resources you can create with Terraform, see the provider documentation.

2. Make sure the settings are correct.

   1. Using the command line, navigate to the folder that contains the up-to-date Terraform configuration files with an infrastructure plan.

   2. Run the command:

      terraform validate
      

      If there are errors in the configuration files, Terraform will point to them.

3. Create an origin group.

   1. Run the command to view planned changes:

      terraform plan
      

      If the resource configuration descriptions are correct, the terminal will display a list of the resources to modify and their parameters. This is a test step. No resources are updated.

   2. If you are happy with the planned changes, apply them:

      1. Run the command:

         terraform apply
         

      2. Confirm the update of resources.

      3. Wait for the operation to complete.

To add an origin group when creating a resource, use the create REST API method for the Resource resource or the ResourceService/Create gRPC API call.

If you do not have the Yandex Cloud command line interface yet, install and initialize it.

The folder specified in the CLI profile is used by default. You can specify a different folder using the --folder-name or --folder-id parameter.

1. View a description of the CLI update resource command:

   yc cdn resource update --help
   

2. Get a list of all resources in the default folder:

   yc cdn resource list --format yaml
   

   Result:

   - id: bc82xll34xuc********
     folder_id: b1g86q4m5vej********
     cname: res1.example.com
     created_at: "2022-01-21T08:17:48.850086Z"
     updated_at: "2022-01-21T08:17:48.850125Z"
     active: true
     options:
       edge_cache_settings:
         enabled: true
         default_value: "345600"
       cache_http_headers:
         value:
         - accept-ranges
         - cache-control
         - connection
         - content-encoding
         - content-length
         - content-type
         - date
         - etag
         - expires
         - keep-alive
         - last-modified
         - server
         - vary
       stale:
         enabled: true
         value:
         - error
         - updating
       allowed_http_methods:
         value:
         - GET
         - POST
         - HEAD
         - OPTIONS
     origin_group_id: "90208"
     origin_group_name: test-group
     origin_protocol: HTTPS
     ssl_certificate:
       type: DONT_USE
       status: READY
   

3. Get a list of all origin groups in the default folder and select the relevant group's ID:

   yc cdn origin-group list --format yaml
   

   Result:

   - id: "90209"
     folder_id: b1g86q4m5vej********
     name: test-group-1
     use_next: true
     origins:
     - id: "561547"
       origin_group_id: "90209"
       source: www.example2.com
       enabled: true
       backup: true
     - id: "561546"
       origin_group_id: "90209"
       source: www.example1.com
       enabled: true
   - id: "90208"
     folder_id: b1g86q4m5vej********
     name: test-group
     use_next: true
     origins:
     - id: "561545"
       origin_group_id: "90208"
       source: www.a2.com
       enabled: true
       backup: true
     - id: "561544"
       origin_group_id: "90208"
       source: www.a1.com
       enabled: true
   

4. Update resource settings by specifying the ID of the origin group:

   yc cdn resource update \
     --id <resource_ID> \
     --origin-group-id <origin_group_ID>
   

   Result:

   id: bc8krsk72icw********
   folder_id: b1g86q4m5vej********
   cname: res2.example.com
   created_at: "2022-01-15T15:29:19.103653Z"
   updated_at: "2022-01-15T15:33:22.819916Z"
   active: true
   options:
     edge_cache_settings:
       enabled: true
       default_value: "345600"
     cache_http_headers:
       value:
       - accept-ranges
       - cache-control
       - connection
       - content-encoding
       - content-length
       - content-type
       - date
       - etag
       - expires
       - keep-alive
       - last-modified
       - server
       - vary
     stale:
       enabled: true
       value:
       - error
       - updating
     allowed_http_methods:
       value:
       - GET
       - POST
       - HEAD
       - OPTIONS
   origin_group_id: "90209"
   origin_group_name: test-group-1
   origin_protocol: HTTPS
   ssl_certificate:
     type: DONT_USE
     status: READY
   

   For more information about the yc cdn resource update command, see the CLI reference.

To add an origin group when editing resource settings, use the update REST API method for the Resource resource or the ResourceService/Update gRPC API call.