I've found a fairly workable solution is to have an origin for the API in CloudFront and a behaviour to route /api/* to that origin. Saves any CORS headaches. Obviously this won't work in all cases.
Just remember, the route prefix you use to define the CloudFront behavior will also be added to the request sent to the origin server. So in this case, all routes defined by the API must be prefixed with `/api/`. This makes it hard to refactor existing APIs with many routes and dependencies, but works great in a greenfield scenario.
(Of course, you can rewrite the URL on the fly via Lambda@Edge but that's a PITA to maintain)
saidmasoud|6 years ago
(Of course, you can rewrite the URL on the fly via Lambda@Edge but that's a PITA to maintain)
hkchad|6 years ago
wefarrell|6 years ago