We've seen this test fail in a couple of regions with the error Request to ... failed with status: 403, expected status: 200. This is also a known flaky test which we've seen fail before and succeed after a simple retry.
After investigation we concluded that the error is likely because the endpoint configuration is automatically set to EDGE which routes requests to a CloudFront Point of Presence. We suspect the test is calling the endpoint right after the stack is deployed but before the routing can take place. To mitigate this we set the endpoint configuration to REGIONAL for now.
Description of how you validated changes
Ran the test locally, it deployed and everything passed as before.
Issue #, if available
N/A
Description of changes
We've seen this test fail in a couple of regions with the error
Request to ... failed with status: 403, expected status: 200. This is also a known flaky test which we've seen fail before and succeed after a simple retry.After investigation we concluded that the error is likely because the endpoint configuration is automatically set to EDGE which routes requests to a CloudFront Point of Presence. We suspect the test is calling the endpoint right after the stack is deployed but before the routing can take place. To mitigate this we set the endpoint configuration to REGIONAL for now.
Description of how you validated changes
Ran the test locally, it deployed and everything passed as before.
Checklist
Examples?
Please reach out in the comments if you want to add an example. Examples will be added to
sam initthrough aws/aws-sam-cli-app-templates.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.