쿠키 기본 설정 선택

당사는 사이트와 서비스를 제공하는 데 필요한 필수 쿠키 및 유사한 도구를 사용합니다. 고객이 사이트를 어떻게 사용하는지 파악하고 개선할 수 있도록 성능 쿠키를 사용해 익명의 통계를 수집합니다. 필수 쿠키는 비활성화할 수 없지만 '사용자 지정' 또는 ‘거부’를 클릭하여 성능 쿠키를 거부할 수 있습니다.

사용자가 동의하는 경우 AWS와 승인된 제3자도 쿠키를 사용하여 유용한 사이트 기능을 제공하고, 사용자의 기본 설정을 기억하고, 관련 광고를 비롯한 관련 콘텐츠를 표시합니다. 필수가 아닌 모든 쿠키를 수락하거나 거부하려면 ‘수락’ 또는 ‘거부’를 클릭하세요. 더 자세한 내용을 선택하려면 ‘사용자 정의’를 클릭하세요.

Multi-region API Gateway with CloudFront - Multi-region API Gateway with CloudFront
이 페이지는 귀하의 언어로 번역되지 않았습니다. 번역 요청

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.

프라이버시사이트 이용 약관쿠키 기본 설정
© 2025, Amazon Web Services, Inc. 또는 계열사. All rights reserved.