serverless / serverless/examples
CORS error for ALB + Lambda
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 11.5k
- Forks
- 4.4k
- Avg merge
- 2h 55m
- Merged PRs (30d)
- 3
Description
I'm using the Lambda +ALB for by post api and is getting the CORS error when calling from a different domain where my frontend code is deployed. I did fix it when this lambda was integrated with API Gateway, but dont see any similar approach for ALb + Lambda. Can you please let me know how to fix CORS error for a path based routing in ALB which points the target to a lambda ?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names an AWS Application Load Balancer path-based route targeting Lambda and a frontend on another domain, but names no repository files or tests. Start by reviewing the existing issue context and reproducing the cross-origin request with the described ALB and Lambda setup. Done means documenting or demonstrating the supported handling for this route.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, javascript
- Domain
- api, backend, cloud, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100