Seleccione sus preferencias de cookies

Usamos cookies esenciales y herramientas similares que son necesarias para proporcionar nuestro sitio y nuestros servicios. Usamos cookies de rendimiento para recopilar estadísticas anónimas para que podamos entender cómo los clientes usan nuestro sitio y hacer mejoras. Las cookies esenciales no se pueden desactivar, pero puede hacer clic en “Personalizar” o “Rechazar” para rechazar las cookies de rendimiento.

Si está de acuerdo, AWS y los terceros aprobados también utilizarán cookies para proporcionar características útiles del sitio, recordar sus preferencias y mostrar contenido relevante, incluida publicidad relevante. Para aceptar o rechazar todas las cookies no esenciales, haga clic en “Aceptar” o “Rechazar”. Para elegir opciones más detalladas, haga clic en “Personalizar”.

Multi-region API Gateway with CloudFront - Multi-region API Gateway with CloudFront
Esta página no se ha traducido a su idioma. Solicitar traducción

Multi-region API Gateway with CloudFront

Publication date: April 19, 2022 (Diagram history)

This architecture shows how you can reduce latency for end-users, while increasing an application’s availability by providing API Gateway endpoints in multiple AWS Regions. Each endpoint offers read-local write-global data synchronization supported by the Amazon Aurora Global Database.

Multi-region API Gateway with CloudFront

Reference architecture diagram showing how you can reduce latency for end-users, while increasing an application’s availability by providing API Gateway endpoints in multiple AWS Regions. Each endpoint offers read-local write-global data synchronization supported by the Amazon Aurora Global Database.
  1. Deploy an API endpoint in two or more AWS Regions using Amazon API Gateway, then handle requests using AWS Lambda connected to an Amazon Aurora relational database.

  2. To keep data in sync across all AWS Regions, enable the Aurora Global Database feature. Aurora automatically routes write requests to the primary node to support data transactions, and replicates the changes to all nodes across AWS Regions.

  3. To support custom domains, upload the domain’s SSL Certificate into AWS Certificate Manager (ACM) and attach it to an Amazon CloudFront distribution.

  4. Point your domain name to CloudFront by using Amazon Route 53 as your DNS name resolution service.

  5. Set up a routing rule on Route 53 to route your global clients to the AWS Region with least latency to their location.

  6. Ensure clients can authenticate seamlessly to API Gateway endpoints in any Region by using AWS Lambda @Edge to query Route 53 for the best AWS Region to forward the request to. This normalizes authorization by abstracting the specifics of each regional endpoint.

  7. Clients across the globe can then connect to your APIs using a single endpoint available in edge locations.

  8. CloudFront will seamlessly route client requests from edge locations to the API in the AWS Region with the lowest latency to the client’s location.

Download editable diagram

To customize this reference architecture diagram based on your business needs, download the ZIP file which contains an editable PowerPoint.

Create a free AWS account

Sign up for a free AWS account

Sign up for an AWS account. New accounts include 12 months of AWS Free Tier access, including the use of Amazon EC2, Amazon S3, and Amazon DynamoDB.

Further reading

For additional information, refer to

Diagram history

To be notified about updates to this reference architecture diagram, subscribe to the RSS feed.

ChangeDescriptionDate

Initial publication

Reference architecture diagram first published.

April 19, 2022

Note

To subscribe to RSS updates, you must have an RSS plugin enabled for the browser you are using.

PrivacidadTérminos del sitioPreferencias de cookies
© 2025, Amazon Web Services, Inc o sus afiliados. Todos los derechos reservados.