Skip to content
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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Cross-account updates for AMI ID distribution to SSM Param store #83

Open
sholtomaud opened this issue Dec 9, 2022 · 0 comments
Open

Comments

@sholtomaud
Copy link

Community Note

  • Please vote on this issue by adding a 馃憤 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Tell us about your request
image-builder-lambda-update-ssm.py in the samples repo is nice if you only have one account and ImageBuilder is in that account. But ImageBuilder pipelines offer AMI distribution feature to distribute AMIs across accounts which is a typical enterprise use case.

We want a boolean switch feature that, if set to true will automatically update SSM Params with the AMI ID. The feature will be an option in the distribution config on an ImageBuilder pipeline which will also have the option of setting the value of the ssm param key.

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
We want a feature that will automatically update SSM Params with the AMI ID. Currently AWS provide no documentation or guidance on how to do this and we get into all sorts of arguments about the most reliable, secure, efficient and least complex way of achieving this, so it needs a solution.

Are you currently working around this issue?
How are you currently solving this problem? We are not and our solution will be complex.

Additional context
Anything else we should know?

Attachments
If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

No branches or pull requests

2 participants