You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Instead of either that or particular library or this one for custom resources, I would suggest that it's now much better to create a resource provider than to use a custom resource Lambda function. Resource providers become proper CloudFormation types, and the AWS-provided resource provider framework is much more robust and capable of handling things like long-running operations that go beyond the 15-minute timeout for Lambda functions. Here's a tutorial on creating a resource provider in Python: https://www.cloudar.be/awsblog/writing-an-aws-cloudformation-resource-provider-in-python-step-by-step/
Just wondering whether this has any advantages over the one AWS are pushing?
The text was updated successfully, but these errors were encountered: