Posted On: Sep 29, 2022
AWS Cloud Control API now supports AWS PrivateLink, providing access for customers to leverage AWS Cloud Control API through private Virtual Private Cloud (VPC) endpoints within their virtual private network. Customers can now manage their cloud infrastructure in a consistent manner and use the latest AWS capabilities faster using Cloud Control API’s common application programming interfaces (APIs) through private IP addresses in their Amazon VPC. These customers can use AWS Cloud Control API without having to use public IPs, firewall rules, or an internet gateway.
With AWS PrivateLink, you can provision and use VPC endpoints to access supported AWS services. AWS PrivateLink provides private connectivity between VPCs, AWS services, and your on-premises networks, without exposing your traffic to the public internet. For example, customers from regulated industries that prefer to keep their VPCs private with no internet connectivity can now use Cloud Control API to create, read, update, delete, and list (CRUDL) AWS and third-party service resources with a consistent API. These customers can now benefit from a uniform method to manage hundreds of AWS resources and over a dozen third-party solutions available on the CloudFormation Registry spanning monitoring, databases, or security management resources. Furthermore, as Cloud Control API is up to date with the latest AWS resources as soon as they are available on the CloudFormation Registry, you can now adopt the latest AWS innovation through private VPC endpoints.
AWS Cloud Control API support for AWS PrivateLink is generally available in all AWS Regions where Cloud Control API is available. These include the following AWS Regions: US East (Ohio, N. Virginia), US West (Oregon, N. California), Canada (Central), Europe (Ireland, Frankfurt, London, Stockholm, Paris, Milan), Asia Pacific (Jakarta, Hong Kong, Mumbai, Osaka, Singapore, Sydney, Seoul, Tokyo), South America (Sao Paulo), Middle East (Bahrain), Africa (Cape Town), and AWS GovCloud (US).
There is no additional charge for using AWS Cloud Control API with native AWS resource types. You will only pay for the usage of underlying AWS resources. When you use AWS Cloud Control API with third-party resource types, you will incur charges based on the number of handler operations you run per month and handler operation duration (refer to the pricing page for more details). To learn more about AWS PrivateLink pricing, please refer to its pricing page.
You can get started with creating a AWS PrivateLink VPC interface endpoint for AWS Cloud Control API by using the AWS CLI or AWS SDKs. To learn more, refer to Cloud Control API’s user guide.