aws / aws/ec2-image-builder-roadmap

Integrate with AWS ServiceCatalog

Open
#65 1 comment 3 reactions 0 assignees View on GitHub
Proposed Usability
Dominant language
No language data
Stars
35
Forks
7
PR merge metrics
No merged PRs in 30d

Description

### Community Note

* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) 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**
What do you want us to build?

Integration with AWS ServiceCatalog

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
The problem we have is how to publish/promote a GOLD AMI internally within our organisation.
There are a number of methods using AWS services that are apparently available:

* Landing Zones Manifests
* Service Catalog
* Distribution Config
* Resource Access Manager

However it is unclear what the best practice is for using ImageBuilder to release approved GOLD AMIs to the organisation.

We currently have over 20 accounts, so distributing AMIs to all 20 would prove to be a burden in terms of the cost of AMIs and the management of AMI lifecycles (ie. cleanup when they expire). Hence ImageBuilder Distribution does not seem like the appropriate tool.

Should ImageBuilder promote/publish/share AMIs through RAM or through ServiceCatalog, or both, or something other?

Likewise for updating and managing LaunchTemplates which reference the AMI id.

**Are you currently working around this issue?**
How are you currently solving this problem?
We are not and need both features and guidance.

**Additional context**
Anything else we should know?
Help us.

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the requested AWS Service Catalog integration alongside Landing Zones Manifests, Distribution Config, and Resource Access Manager. The issue does not identify repository files, tests, or an implementation entry point. Done would require an agreed approach for publishing approved AMIs across accounts and managing related LaunchTemplates and AMI lifecycles.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
cloud, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.