0% found this document useful (0 votes)
165 views

Aws Reference Architecture Multi Region Cloudfront Api Gateway Ra

The document describes a multi-region API Gateway architecture using API Gateway endpoints in multiple AWS regions with an Aurora global database to synchronize data. Custom domains are supported using ACM and CloudFront with Route 53 for DNS resolution and latency-based routing of clients to the nearest region.

Uploaded by

Coco Lulu
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
165 views

Aws Reference Architecture Multi Region Cloudfront Api Gateway Ra

The document describes a multi-region API Gateway architecture using API Gateway endpoints in multiple AWS regions with an Aurora global database to synchronize data. Custom domains are supported using ACM and CloudFront with Route 53 for DNS resolution and latency-based routing of clients to the nearest region.

Uploaded by

Coco Lulu
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

Multi-region API Gateway with CloudFront 1 Deploy an API endpoint in two or more

AWS Regions using Amazon API


Reduce latency for end-users, while increasing an application’s availability by providing API Gateway endpoints in multiple AWS Gateway, then handle requests using
Regions. Each endpoint offers read-local write-global data synchronization supported by the Amazon Aurora global database. AWS Lambda connected to an Amazon
Aurora relational database.

To keep data in sync across all AWS


2 Regions, enable the Aurora Global
AWS Cloud Database feature. Aurora automatically
3 routes write requests to the primary node
Region A to support data transactions, and
4 SSL replicates the changes to all nodes across
certificate AWS Regions.
AWS Lambda
To support custom domains, upload the
handlers 3
1 domain’s SSL Certificate into AWS
Amazon Route 53 AWS Certificate Certificate Manager (ACM) and attach it
to an Amazon CloudFront distribution.
DNS name resolution Manager (ACM)
custom domain Point your domain name to CloudFront
4 by using Amazon Route 53 as your DNS
Amazon API Gateway Amazon Aurora name resolution service.
API endpoint relational database
7 8
Set up a routing rule on Route 53 to route
5 your global clients to the AWS Region
Region B global with least latency to their location.
2
global AWS Lambda database
Amazon CloudFront Ensure clients can authenticate seamlessly
clients handlers 6
CDN distribution to API Gateway endpoints in any Region
by using AWS Lambda @Edge to query
Route 53 for the best AWS Region to
5 6 forward the request to. This normalizes
authorization by abstracting the specifics
Amazon API Gateway Amazon Aurora of each regional endpoint.
API endpoint relational database Clients across the globe can then
Amazon Route 53 AWS Lambda @Edge 7
connect to your APIs using a single
latency routing routing logic endpoint available in edge locations.
CloudFront will seamlessly route client
8
requests from edge locations to the API
Reviewed for technical accuracy April 19, 2022
© 2022, Amazon Web Services, Inc. or its affiliates. All rights reserved. AWS Reference Architecture in the AWS Region with the lowest
latency to the client’s location.

You might also like