To avoid CORS, i've had to create my own OPTIONS handler for each function. The cheapest is just to echo the ORIGIN header back as authorized via CORS. The better way is to have the api gateway on the same domain as the rest of the product. So in order to get rid of CORS errors I've used Cloudfront to forward requests to the API gateway.
The explanation of your setup is a little vague, it shouldn't matter if its in a container or not. CORS is all about browser action and if you are accessing a resource outside of the domain of your main web page.
If you are using a program outside of a web browser-like interface then you wouldn't have any CORS issues.
Don't bother answering.
This product is effectively unusable. I will find another solution.
Which AWS load balancer type is the best for directing geographically different traffic to the nearest server?asked 10 months ago
The web acl is associated with the Application Load Balancer in the AWS region. After a few hours, it is found that the association has been cancelledasked 5 months ago
i have 1 instances and i am using application load balancerasked 2 months ago
Penetration testing for Amazon API Gateway and AWS Lambda FunctionsAccepted Answerasked 3 years ago
API Gateway, Lambda and CORSasked 2 years ago
What is the main differences between an load balancer and a autoscaling groupAccepted Answerasked 4 months ago
ASP.NET Web API on AWS Lambda CORSasked 9 months ago
Can a network load balancer front an API Gateway?asked 9 months ago
Load Balancer and API GatewayAccepted Answerasked 10 months ago
Load Balancer host based on User's CloudFront-Viewer-Countryasked 3 months ago