Spotlight
How to Use IPv6 With AWS Services That Don't Support It
Build an IPv6-to-IPv4 proxy using CloudFront to enable connectivity with IPv4-only AWS services.
My single largest complaint with the entire AWS Serverless ecosystem was that running a multi-region API Gateway was impossible to do. Well, impossible without servers. You could do it if you were willing to run a few nginx reverse proxies and some load balancers for a production quality setup.
This time is over. With the new launch of Regional API Endpoints for API Gateway, the nightmare is over. You can now do Active/Active or Active/Passive failover with ease.
regional.example.com
*.example.com
d-tt654494hgf.execute-api.us-east-1.amazonaws.com
d-k39fj3lfkkf.execute-api.us-west-2.amazonaws.com
weighted
, latency
, failover
or geolocation
based routing for each of your endpointslatency
or geolocation
are probably the bestweighted
is the easiest especially if you just want round robin styleWith this being the small potatoes stuff that gets announced now, re:Invent is gonna be a heck of show. We'll see you there, reach out if you want to meet for a drink.
Build an IPv6-to-IPv4 proxy using CloudFront to enable connectivity with IPv4-only AWS services.