[CodeBuild] [request]: Pull images through VPC ENI
- Dominant language
- Shell
- Stars
- 5.4k
- Forks
- 334
- 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**
Codebuild can be configured to pull images from a private repository as well as being configured to run in your VPC. But Codebuild always pulls images through the public internet rather than the configured VPC subnet/security group.
Please allow pulling images through a VPC ENI to allow for IP range enforcement/accessing registries on private networks.
**Which service(s) is this request for?**
Codebuild
**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
Pulling images from a private repository which doesn't allow wide internet access
**Are you currently working around this issue?**
Manually copying images to an ECR
**Additional context**
N/A
**Attachments**
N/A
Contributor guide
Research direction
The request concerns AWS CodeBuild image pulls, private repositories, VPC subnets, security groups, and VPC ENIs; it names no repository files or tests. Start by reviewing the CodeBuild image-pull and VPC configuration entry points. Done means private images can be pulled through the configured VPC ENI while respecting network access controls.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100