Access AWS Control Catalog using an interface endpoint (AWS PrivateLink)

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

You establish this private connection by creating an interface endpoint, powered by AWS 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 AWS Control Catalog.

For more information, see Access AWS services through AWS PrivateLink in the AWS PrivateLink Guide.

Considerations for AWS Control Catalog

Before you set up an interface endpoint for AWS Control Catalog, review Considerations in the AWS PrivateLink Guide.

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

Create an interface endpoint for AWS Control Catalog

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

Create an interface endpoint for AWS Control Catalog using the following service name:

com.amazonaws.region.controlcatalog

If you enable private DNS for the interface endpoint, you can make API requests to AWS Control Catalog using its default Regional DNS name. For example, service-name.us-east-1.amazonaws.com.

Create an endpoint policy for your interface endpoint

An endpoint policy is an IAM resource that you can attach to an interface endpoint. The default endpoint policy allows full access to AWS Control Catalog through the interface endpoint. To control the access allowed to AWS Control Catalog from your VPC, attach a custom endpoint policy to the interface endpoint.

For more information, see Control access to services using endpoint policies in the AWS PrivateLink Guide.

Example: VPC endpoint policy for AWS Control Catalog actions

The following is an example of a custom endpoint policy. When you attach this policy to your interface endpoint, it grants access to the listed AWS Control Catalog actions for all principals on all resources.

{
   "Statement": [
      {
         "Principal": "*",
         "Effect": "Allow",
         "Action": [
            "controlcatalog:ListDomains",
            "controlcatalog:ListObjectives",
            "controlcatalog:ListCommonControls"
         ],
         "Resource":"*"
      }
   ]
}