Make AWS AMI's accessible by the public #238
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cevich
force-pushed
the
public_images
branch
2 times, most recently
from
4f80d2e to
95b31b7
Compare
Commit containers/podman@c782795 altered the way tooling is installed for podman making it incompatible with a c/automation_images pre-install. Several attempts were made to update podman's scripts and Makefile to de-hardcode this. All failed and/or were too complex. Instead, abandon the effort entirely, allowing podman to suffer any consequential runtime-install flakes or other bad behaviors. Signed-off-by: Chris Evich <cevich@redhat.com>
Fixes: containers#191 On at least two occasions I can remember, users outside the containers-team have requested access to our CI VM images. Unfortunately doing this for the GCE images has some security-interest conflicts with our build automation. However, making the AWS AMI's public is rather easy to do. In fact it's the default unless they are specifically locked down. Simply remove the private restrictions and allow access to `"all"` AWS groups. Signed-off-by: Chris Evich <cevich@redhat.com>
|
Apparently there's a limit of --> 5 <-- public AWS EC2 images 🫣 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes: #191
On at least two occasions I can remember, users outside the containers-team have requested access to our CI VM images. Unfortunately doing this for the GCE images has some security-interest conflicts with our build automation. However, making the AWS AMI's public is rather easy to do. In fact it's the default unless they are specifically locked down. Simply remove the private restrictions and allow access to
"all"AWS groups.Signed-off-by: Chris Evich cevich@redhat.com