-
Notifications
You must be signed in to change notification settings - Fork 9.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: AWS Lambda SnapStart needs Lambda Versions #28559
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
Hey @faxx1080 👋 Thank you for taking the time to raise this! I think the |
Thanks! That did work for me. A question though: is there an ability to delete old versions of functions? |
Hey @faxx1080 👋 Glad that helped! As far as deleting old versions of functions, I don't believe there's a way to do so via Terraform (aside from deleting the function itself), but it appears to be possible via the CLI or via the API. Since we've resolved the root of the issue, I'll go ahead and close it out. If you do have any other general use questions, they'll be more suited for the AWS Provider forum. |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Terraform Core Version
1.25
AWS Provider Version
4.48.0
Affected Resource(s)
I understand from AWS that to use SnapStart, just setting "snap_start" to PublishedVersions is not enough, one also needs to publish a lambda version, then SnapStart is enabled on the version, as the version is immutable.
Source: https://docs.aws.amazon.com/lambda/latest/dg/snapstart.html
Currently, I don't see much documentation on managing lambda versions using Terraform, are versions supported?
Expected Behavior
SnapStart should be enabled and used, and I should see RESTORE lines in AWS Lambda logs
Actual Behavior
I do not see RESTORE lines in Lambda logs
Relevant Error/Panic Output Snippet
No response
Terraform Configuration Files
main.tf
Steps to Reproduce
Then in AWS Console create a version of test-1 lambda. Then test it.
Debug Output
Logs
NOTE: I modified the role in the console to add CloudWatch permissions afterward.
CloudWatch Logs:
What I expect to see:
Panic Output
No response
Important Factoids
It's a basic-do-nothing Java lambda to test SnapStart. Whether it completes successfully or not is not what I was testing.
References
#28097
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: