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. This will be essential for when DR's API goes public.
Allows us to have better control over our vanity URLS. This will also help with the Hold Pass feature.
Acceptance criteria:
/api/ sends you to API Gateway via Lamda@Edge
Update SAM template
all requests go through the data.bcparks.ca domain (including API calls)
Development Checklist:
[ ] API calls in the front-ends need to be redirected to use the vanity domain instead of the API gateway URL
[ ] A check in the lambda functions themselves need to check to ensure they were called via the vanity URL instead of the API gateway. This can be done a few ways, but creating a session identifier that would not be present unless they loaded the webpage would be a good start.
Note:
The work from this ticket will be applied to:
danieltruong
commented
7 months ago
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. This will be essential for when DR's API goes public.
Allows us to have better control over our vanity URLS. This will also help with the Hold Pass feature.
Acceptance criteria:
Development Checklist:
Note: The work from this ticket will be applied to: