The following Amazon US locations and associated IX's carry routes/traffic specific only to the services with infrastructure in that metro. For example, Jacksonville is CloudFront only, whereas Ashburn is CloudFront, EC2, S3, etc.)
- Seattle
- Palo Alto
- San Jose
- Los Angeles 
- Dallas
- St Louis
- South Bend
- Jacksonville
- Miami
- Ashburn
- Vienna
- Newark
- New York

The following locations and associated IX's are part of Amazon's European Backbone, carrying routes/traffic for other AWS services (e.g. EC2, S3), Amazon retail, as well as local CloudFront caching. For each of these locations, Amazon will provide local routes/traffic for all services within that locality unless peers are able to meet in at least two diverse locations within the region, in which case, routes/traffic for all services within that region will be provided.
- Dublin
- Amsterdam
- London
- Frankfurt
- Paris

The following Amazon EU locations and associated IX's carry routes/traffic specific only to CloudFront services in that metro.
- Stockholm
- Milan
- Madrid
- Marseille
- Warsaw

The following Amazon AP locations and associated IX's carry routes/traffic specific only to the services with infrastructure in that metro. For example, Hong Kong is CloudFront only, whereas Sydney is CloudFront, EC2, S3, etc.)
- Tokyo 
- Osaka
- Hong Kong
- Singapore
- Sydney

When new peering sessions are established, they will initially be configured to not announce or accept any prefixes. Sessions will be normalized in a maintenance window the following evening, usually centered around 11:00 PM to 3:00 AM local time.