AR -> Use Lambda@Edge for API vanity url
Open
A&R
- Dominant language
- JavaScript
- Stars
- 2
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
At the moment, we are using a Cloudfront origin to redirect traffic going /api/ to our API Gateway. We want to use Lambda@Edge for this functionality.
Acceptance criteria:
- /api/ sends you to API Gateway via Lamda@Edge
- Update SAM template
Note:
- Refer to https://github.com/bcgov/parks-data-register/issues/376
- Blocked by #291
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the current CloudFront origin redirect for /api/ and the SAM template, then review the related parks-data-register issue #376 and resolve the dependency on #291. The work is done when /api/ reaches API Gateway through Lambda@Edge and the SAM template reflects that setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, javascript, nodejs
- Domain
- api, backend, cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100