Considerations for Cloud Control API VPC endpoints Creating an interface VPC endpoint for Cloud Control API Creating a VPC endpoint policy for Cloud Control API See also

Cloud Control API and interface VPC endpoints (Amazon PrivateLink)

You can use Amazon PrivateLink to create a private connection between your VPC and Amazon Cloud Control API. You can access Cloud Control API as if it were in your VPC, without the use of an internet gateway, NAT device, VPN connection, or Amazon Direct Connect connection. Instances in your VPC don't need public IP addresses to access Cloud Control API.

You establish this private connection by creating an interface endpoint, powered by Amazon PrivateLink. We create an endpoint network interface in each subnet that you enable for the interface endpoint. These are requester-managed network interfaces that serve as the entry point for traffic destined for Cloud Control API.

Cloud Control API supports making calls to all of its API actions through the interface endpoint.

Considerations for Cloud Control API VPC endpoints

Before you set up an interface VPC endpoint for Cloud Control API, first make sure you have met the prerequisites in the Access an Amazon service using an interface VPC endpoint topic in the Amazon PrivateLink Guide.

Creating an interface VPC endpoint for Cloud Control API

You can create a VPC endpoint for Cloud Control API using either the Amazon VPC console or the Amazon Command Line Interface (Amazon CLI). For more information, see Create a VPC endpoint in the Amazon PrivateLink Guide.

Create an interface endpoint for Cloud Control API using the following service name:

cn.com.amazonaws.region.cloudcontrolapi

If you enable private DNS for the endpoint, you can make API requests to Cloud Control API using its default DNS name for the Region.

For more information, see Access an Amazon service using an interface VPC endpoint in the Amazon VPC User Guide.

Creating a VPC endpoint policy for Cloud Control API

You can attach an endpoint policy to your VPC endpoint that controls access to Cloud Control API. The policy specifies the following information:

The principal that can perform actions.
The actions that can be performed.
The resources on which actions can be performed.

For more information, see Control access to VPC endpoints using endpoint policies in the Amazon PrivateLink Guide.

Important

VPCE endpoint policy details are not passed to any downstream services invoked by Cloud Control API for evaluation. Because of this, policies specifying actions or resources that belong to downstream services are not enforced.

For example, suppose you created an Amazon EC2 instance in a VPC instance with a VPC endpoint for Cloud Control API in a subnet with no Internet access. Next, you attach the following VPC endpoint policy to the VPCE:


{
  "Statement": [
    {
      "Action": [
        "cloudformation:*",
        "ec2:*",
        "lambda:*"
      ]
      "Effect": "Allow",
      "Principal": "*",
      "Resource": "*"
    }
  ]
}

If a user with administrator access then sends a request to access an Amazon S3 bucket in the instance, no service error would be returned, even though Amazon S3 access is not granted in the VPCE policy.

Example: VPC endpoint policy for Cloud Control API actions

The following is an example of an endpoint policy for Cloud Control API. When attached to an endpoint, this policy grants access to the listed Cloud Control API actions for all principals on all resources. The following example denies all users the permission to create resources through the VPC endpoint, and allows full access to all other actions on the Cloud Control API service.


{
  "Statement": [
    {
      "Action": "cloudformation:*",
      "Effect": "Allow",
      "Principal": "*",
      "Resource": "*"
    },
    {
      "Action": "cloudformation:CreateResource",
      "Effect": "Deny",
      "Principal": "*",
      "Resource": "*"
    }
  ]
}