AWS PrivateLink now supports native cross-region connectivity to AWS services. Until now, Interface VPC endpoints only supported connectivity to AWS services in the same Region. This launch enables customers to connect to select AWS services hosted in other Regions of the same AWS partition over Interface endpoints.
As a service consumer, you can access Amazon S3, Route53, Elastic Container Registry (ECR) and other services, privately without the need to setup cross-region peering or exposing your data over the public internet. These services can be accessed through Interface endpoints at a private IP address in your VPC, enabling simpler and more secure inter-region connectivity. This feature helps you build globally distributed private networks that comply with data residency requirements, while accessing supported AWS Services through PrivateLink
To learn about pricing for this feature, please see the AWS PrivateLink pricing page. For a complete list of supported AWS services and Regions, please refer to our documentation [link TBD]. To learn more, visit AWS PrivateLink in the Amazon VPC Developer Guide.
Categories: marketing:marchitecture/networking-and-content-delivery,general:products/aws-privatelink
Source: Amazon Web Services
Latest Posts
- Amazon CloudWatch Logs now supports log ingestion using HTTP-based protocol
- Microsoft 365 Copilot Chat – Updates to Copilot in Word, Excel, and PowerPoint [MC1253863]
- Amazon CloudWatch introduces organization-wide EC2 detailed monitoring enablement
- SageMaker HyperPod now supports idle resource sharing for dynamic cluster utilization
