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
Hi,
I’m using a custom AMI that I built with Packer and Ansible. Once the new image is uploaded, I noticed that the Lambda runner still checks/gets the EC2 info (AMI ID) from the launch template. Therefore, I had to manually edit the template with the new AMI ID.
I have a lot of experience with Kubernetes environments using ARC, but I need help with some best practices here. Should I create a custom flow that creates the AMI and updates the launch template? If I need to go in a different direction, it would be nice to get feedback here.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
I’m using a custom AMI that I built with Packer and Ansible. Once the new image is uploaded, I noticed that the Lambda runner still checks/gets the EC2 info (AMI ID) from the launch template. Therefore, I had to manually edit the template with the new AMI ID.
I have a lot of experience with Kubernetes environments using ARC, but I need help with some best practices here. Should I create a custom flow that creates the AMI and updates the launch template? If I need to go in a different direction, it would be nice to get feedback here.
Beta Was this translation helpful? Give feedback.
All reactions