Fixing CORS in AWS CDK Without Guesswork

I’ve seen a weird pattern with CORS on AWS projects: the infrastructure is “fully automated,” but CORS is still handled like a last-minute checkbox. Somebody adds '*', the browser still fails, and the team burns half a day staring at DevTools. This case study is from a setup that’s very common: React frontend hosted on S3 + CloudFront API on API Gateway + Lambda Infrastructure managed with AWS CDK in TypeScript Cookies used for auth in production Separate frontend domains for local, staging, and prod The team thought they had CORS configured. They did not. ...

November 19, 2026 · 7 min · headertest.com

CORS Mistakes with AWS Lambda Function URLs

AWS Lambda Function URLs are one of those features that feel almost suspiciously easy. Click a checkbox, get a public HTTPS endpoint, ship it. Then the browser starts yelling about CORS. I’ve seen this catch people because Function URLs blur two layers together: AWS can add CORS headers for you at the Function URL level. Your Lambda code can also return CORS headers. Mix those carelessly and you get flaky behavior, broken preflights, and confusing browser errors that look unrelated to the actual bug. ...

October 21, 2026 · 7 min · headertest.com

CORS for AWS CloudFront: Practical Setup and Gotchas

CORS on CloudFront looks simple until caching gets involved. That’s the part that bites people. You add Access-Control-Allow-Origin, test once, it works, then a different origin starts failing or getting the wrong response from cache. If you’ve ever had a “works in curl, fails in browser” day with CloudFront, this is usually why. I’m going to show the setups that actually work in production: static assets behind CloudFront APIs behind CloudFront S3 origins custom origins like ALB, EC2, or API backends dynamic origin allowlists preflight caching without poisoning your edge cache What CloudFront does in a CORS flow CloudFront is a cache and proxy sitting between the browser and your origin. ...

October 14, 2026 · 7 min · headertest.com

CORS Mistakes in AWS AppSync and How to Fix Them

AWS AppSync looks simple from the browser: send a GraphQL POST, get JSON back, move on. Then CORS shows up and burns half a day. I’ve seen the same pattern over and over: the GraphQL API works in Postman, works in the AWS console, maybe even works from a local script, but the browser throws a CORS error that tells you almost nothing useful. AppSync is especially good at this because the problem is often not “CORS in AppSync” by itself. It’s usually some combination of custom domains, auth mode, preflight behavior, CloudFront, cookies, or headers your frontend is trying to send. ...

July 1, 2026 · 7 min · headertest.com

CORS with AWS API Gateway: REST, HTTP APIs, and gotchas

If you’ve ever shipped a frontend against AWS API Gateway, you’ve probably had that moment: the API works fine in Postman, maybe even with curl, but the browser throws a CORS error and gives you almost nothing useful. That’s the thing about CORS with API Gateway: the browser enforces it, API Gateway partially helps, and your backend can still ruin everything. I’ve seen teams lose hours because they enabled “CORS” in the console and assumed they were done. Usually they weren’t. ...

April 28, 2026 · 7 min · headertest.com

CORS for Pulumi: copy-paste recipes for real stacks

CORS gets weird fast when you move from app code into infrastructure. In Pulumi, that usually means you’re not “fixing a header bug” — you’re wiring behavior across buckets, CDNs, API gateways, Lambda responses, and sometimes the browser cache too. I’ve seen teams burn hours changing app code when the real problem was an S3 bucket CORS rule, an API Gateway preflight route, or CloudFront stripping Origin from the cache key. ...

April 27, 2026 · 7 min · headertest.com

CORS for AWS ECS Fargate

CORS on AWS ECS Fargate usually goes wrong for one boring reason: people configure it in the wrong layer. I’ve seen teams add CORS headers in app code, then put an ALB, CloudFront, Nginx, or API Gateway in front of it and accidentally strip or duplicate headers. Then the browser says “CORS failed” and everybody starts guessing. Here’s the practical way to think about it: Browser enforces CORS Your backend must return the right headers Every proxy in front of your app must preserve them Preflight OPTIONS requests must succeed You cannot “fix CORS” from frontend code If your app runs on ECS Fargate, CORS is not an ECS feature. ECS just runs containers. The actual CORS behavior comes from whatever is serving traffic: ...

April 26, 2026 · 8 min · headertest.com

CORS for AWS API Gateway HTTP APIs

CORS on AWS API Gateway HTTP APIs looks simple right up until your browser starts throwing No 'Access-Control-Allow-Origin' header and your backend logs show everything is “working fine.” I’ve hit this enough times that I now treat CORS as part browser contract, part API Gateway feature, and part trap. This guide is about API Gateway HTTP APIs specifically, not the older REST API product. The behavior is different enough that mixing them up causes bad advice and wasted hours. ...

April 23, 2026 · 7 min · headertest.com

CORS for Terraform API Gateway: Copy-Paste Reference

CORS on API Gateway looks easy until the browser starts throwing vague errors and Terraform happily deploys a broken setup. I’ve hit this enough times that I now treat CORS as a first-class part of the API contract, not a checkbox. If you manage AWS API Gateway with Terraform, the main thing to remember is this: CORS is enforced by browsers, but you implement it in API Gateway and your backend responses. ...

April 21, 2026 · 6 min · headertest.com