aws / aws/ec2-image-builder-roadmap

Infrastructure Configuration support for Tags in Metadata

Open
#73 0 comments 6 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**
[Instance Tags now available on the Amazon EC2 Instance Metadata Service](https://aws.amazon.com/about-aws/whats-new/2022/01/instance-tags-amazon-ec2-instance-metadata-service/) is a great enhancement, and we're taking advantage of it where we can to make various automation easier. We'd like Image Builder Infrastructure Configurations to support it.

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
An Image Builder Component we're working on creates a script file in the image that reads tags from metadata. We'd really like to use a `test` phase for this component, verifying that the tags are properly read by the script. However as far as I can tell, Infrastructure Configurations don't currently support that attribute (it would probably be [here](https://docs.aws.amazon.com/imagebuilder/latest/APIReference/API_CreateInfrastructureConfiguration.html#API_CreateInfrastructureConfiguration_RequestSyntax)). We'd love if an instance used in both the `build` and `test` phases had access to tags in metadata.

**Are you currently working around this issue?**
We _could_ work around it by reaching out to the EC2 API and querying tags for the current instance, but that introduces additional permission requirements that shouldn't be necessary. We want to use tags-in-metadata.

**Additional context**

**Attachments**

Contributor guide

Open the contributing guide

Research direction

Start with the AWS Image Builder CreateInfrastructureConfiguration API documentation linked in the issue, then trace how Infrastructure Configurations expose instance metadata during build and test phases. Done means an infrastructure configuration can enable EC2 instance tags in metadata without requiring extra EC2 API permissions, with coverage for both phases.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
cloud, infrastructure
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.