Does this mean that I can deploy the same API code in two regions that sends a request for Lambda firmware? (These will be two different Https endpoints)
It was already possible. You can already deploy the same API code in several regions and create different HTTPS endpoints using the Gateway API.
, , API Gateway API - , , - API Gateway.
, " " - API- API Gateway , CloudFront. API , CloudFront, API - - API AWS Edge Network, , CloudFront, Route 53 S3 Transfer Acceleration.
, , .
, API, CloudFront Edge Network... API ( ).
API :
EC2 , , API EC2.
API CloudFront, (, , , API ), , CloudFront CloudFront, API Gateway, , CloudFront , .
API CloudFront API.
API , CloudFront , Edge-Optimized - .
API , . API- (, api.example.com) AWS - API Gateway CloudFront. CloudFront - , - CloudFront . API CloudFront, API- AWS.
, , api.example.com us-east-2 us-west-2, API, api.example.com API, ACM . ( ACM , API, us-east-1.)
: , DNS. :
d-aaaaaaaaaa.execute-api.us-east-2.amazonaws.com
d-bbbbbbbbbb.execute-api.us-west-2.amazonaws.com
, ?
Route 53 Latency-based CNAME api.example.com - - -2, - -2 - , . 53 DNS- , . , , API us-east-1, DNS- Route 53, -east-1, Route 53 , us-east-2 - , us-east-2 . 53 DNS, d-aaaaaaaaaa.execute-api.us-east-2.amazonaws.com.
, API AWS, , Endpoint Optimized Endpoints ( ).
CloudFront ?
. , , . CloudFront , Lambda @Edge ( , API CloudFront, ).
, , Route 53 Latency-based routing . , - CloudFront, ... , ...
, , DNS, , , , Java, , Java, , DNS-. . CloudFront DNS , DNS-, CloudFront . TTL Route 53, CloudFront, , , .
CloudFront - , Edge Network. AWS, API, , .
, -, API Gateway - , . , , , IAM . X-Amz-Credential , , , , Signature V4 //// ( , ), , . . Cognito . API, , .., .
, , , - API- , , , . , , .