Is there an existing issue for this?

• I have searched the existing issues

Feature description

We're running Localstack inside our development environments, which runs the main container behind a reverse proxy on a custom domain. This works pretty well for what I've been working on until now, but as I attempted to deploy a Next.js app on Fargate behind an ALB, but without CloudFront, I keep getting CORS errors. The app is reachable on something like lb-12345678.elb.localstack.project-domain.dev. The problem is that I cannot add this domain to the EXTRA_CORS_ALLOWED_ORIGINS list as it changes whenever I restart LocalStack and redeploy the app, and EXTRA_CORS_ALLOWED_ORIGINS currently does not support wildcards at all. At this time, my only option seems to be to set DISABLE_CORS_CHECKS=1, but I'd prefer not to do that.

🧑‍💻 Implementation

No response

Anything else?

No response