2 Answers
- Newest
- Most votes
- Most comments
2
For operations that involve large volumes that result in timeouts in Lambda, consider the following alternatives:
- Ensure your Lambda function has the maximum allowed execution time (15 minutes) and sufficient memory.
- Use AWS Step Functions to orchestrate workflows that exceed Lambda's 15-minute limit by breaking the process into smaller steps.
- Look into AWS DataSync for efficient data transfer tasks, especially for large datasets.
- Employ AWS Elastic File System (EFS) with Lambda for handling large datasets beyond Lambda’s storage limit.
If this has answered your question or was helpful, accepting the answer would be greatly appreciated. Thank you!
0
I would use StepFunctions instead of Lambda. There is no need to pay for the Lambda duration while it is waiting for the snapshot to finish. You can have a state to snapshot the volume directly, no need to invoke a Lambda function.
Relevant content
- asked 2 years ago
- Accepted Answerasked 5 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 8 months ago