Skip to content

Architecture

One account holds two buckets. Consumers do not call S3 across Regions: each uses a gateway VPC endpoint
S3 gateway VPC endpoint. Route-table target that keeps S3 traffic on the AWS network; no hourly charge for the gateway itself.
in its own Region and the local bucket hostname. Replication
Cross-Region Replication. S3 copies objects (and versions) from a primary bucket to a replica in another Region.
copies objects from Sydney to Auckland after you publish.

Lab architecture: private S3 artifact store Publish to an S3 primary bucket in Sydney; CRR copies objects to an Auckland replica. Consumer VPCs in each Region read via regional S3 gateway VPC endpoints. Sydney primary → Auckland replica, regional S3 gateways ap-southeast-2 (Sydney) ap-southeast-6 (Auckland) publish S3 primary bucket Replication demo/ S3 replica bucket Gateway VPCE S3 Consumer VPC Gateway VPCE S3 Consumer VPC

Same key, regional URL:

https://<primary>.s3.ap-southeast-2.amazonaws.com/demo/...
https://<replica>.s3.ap-southeast-6.amazonaws.com/demo/...
Piece Account Region
Primary bucket (source) Shared ap-southeast-2
Replica bucket Shared ap-southeast-6
Syd gateway + probe EC2 Same account in this lab ap-southeast-2
Akl gateway + probe EC2 Same account in this lab ap-southeast-6

Bucket policies deny access unless aws:SourceVpce matches an allowlisted endpoint. Publish, admin, and replication principals get a bypass.

  • CloudFront / public CDN
  • One global hostname (MRAP)
  • S3 interface endpoints for cross-Region reads
  • Package-manager repodata (plain objects only)