aws-cloudformation / aws-cloudformation/custom-resource-helper
VPC lambda timeout failure
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 382
- Forks
- 61
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
The behavior for a in-VPC Lambda function with no internet access lacks error messages and timeout.
- there's no timeout, it should try (eventually retry) and fail with an error message, here:
https://github.com/aws-cloudformation/custom-resource-helper/blob/006d4e92ebba11c2b1635962262b12f00983416c/crhelper/utils.py#L25
- It should be clear (documentation and error message) that the Lambda function needs access to S3 to report the status, by either full internet access or by having an S3 endpoint in the VPC
Bastien(AWS)
Contributor guide
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
Start in crhelper/utils.py at line 25 and investigate the in-VPC Lambda path when there is no internet access. Reproduce the missing timeout and error behavior, then verify that the documentation and error message explain the need for S3 access through internet connectivity or a VPC S3 endpoint.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, python
- Domain
- cloud, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100