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
{{ message }}
This repository has been archived by the owner on Nov 1, 2023. It is now read-only.
It appears that the AMI ids in the mapping of the vault stack for CIS images are incorrect (at least in us-west-2 and us-east-1). The correct AMI for us-west-2 CIS Ubuntu 2004 is ami-02d086f8cc9c67825, but the mapping has it as ami-0050ca8a652e205b2
The text was updated successfully, but these errors were encountered:
Hi @gargana , looks like AMI on eu-central-1 is incorrect, is there any way to override this without the need for you to actively update the mapping?
Edit: I was also unable to deploy from the S3 bucket after I forked and updated this repo, since it looks like it looks for a zip file I don't have on my dedicated s3 bucket:
"functions/packages/LeaderElection/lambda.zip",
"functions/packages/ClusterBootstrap/lambda.zip"
Edit2: I successfully deployed the stack after I added the lambda.zip files and corresponding folders manually to my S3 bucket which had the template edited with the correct AMI.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It appears that the AMI ids in the mapping of the vault stack for CIS images are incorrect (at least in us-west-2 and us-east-1). The correct AMI for us-west-2 CIS Ubuntu 2004 is ami-02d086f8cc9c67825, but the mapping has it as ami-0050ca8a652e205b2
The text was updated successfully, but these errors were encountered: