Lambda Timeout

[turbocrow]

Hi,

I am having an issue with this timing out after the 5 mins it could be done to how large my environment is.

(thousands of snapshots and hundreds of instances)

Is there anything I can do to fix this ? Thanks

[joseph-holland]

Hi,

Yes, I was having this issue previously. The 5min timeout was a limitation in the AWS Lambda service. I just ran it several times manually and eventually it kind of caught up and only had to update some tags and it was able to do it in under the 5min timeout period.

Great news though, AWS recently (yesterday) upped the timeout to 15mins. So you shoudl try again and see if this completes the tagging run.

Joe

[swe-ds]

Even with 15 minutes and maximized memory, the utility does not finish in very large environments. it would be great to build in fan out, allow the instance propagation and volume propagation to occur or not occur based on ENV variables, or to store state in a Systems manager parameter/S3/dynamodb to allow the next run to resume from where it left off.