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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deploy docker image to AWS Container Service #76

Open
Townsheriff opened this issue Dec 11, 2021 · 4 comments
Open

Deploy docker image to AWS Container Service #76

Townsheriff opened this issue Dec 11, 2021 · 4 comments

Comments

@Townsheriff
Copy link
Contributor

Townsheriff commented Dec 11, 2021

Hey,

I'm using this library in the CI and it is running very frequent. I have migrated all my docker images to AWS CS, because Docker requires paid subscription. This is not an issue with AWS CS. It would be awesome to see image on there.

Example of redeploying from docker registry to AWS registry.

TOKEN=$(aws ecr-public get-authorization-token --region us-east-1 --output=text --query 'authorizationData.authorizationToken')

skopeo sync --all --src docker --dest docker jagregory/cognito-local public.ecr.aws/xxx --dest-registry-token $TOKEN

Tool to sync images: https://github.com/containers/skopeo

As of now I have built image locally and deployed to my account - https://gallery.ecr.aws/s3m2t6e7/cognito-local (actual version 3.10.0 + these changes)

@jagregory
Copy link
Owner

Hey, do you know if there's any precedent for this with other OSS projects?

I'm a bit wary of doing this because it can incur costs for me. There's a good free tier, but it's still a risk that someone could do something stupid in their CI server and start costing me money.

I'd be interested in seeing how other OSS projects have solved this issue.

@Townsheriff
Copy link
Contributor Author

Townsheriff commented Dec 12, 2021

I understand your concern.

You can check out the gallery to see which companies/organizations/projects are pushing to the registry.

As I read the pricing section I see that public repositories allow to have 50 GB per month and costs for transfer for anonymous users are 0.

I would guess that others are creating organisations account and have IAM users with restricted rights to push the repository.

Also I would guess they are controlling what is published to the registry, in similar fashion as with npm (I can't publish cognito-local to npm, only you can).

@jagregory
Copy link
Owner

Yeah locking down writes sounds easy, it's those anonymous reads I'm a bit hesitant about. My read of the pricing page is as you said "costs for transfer for anonymous users are 0" but only for the first 500gb per month.

Realistically, I can't see this little project hitting 500gb per month any time soon. It's a 50mb image so I'd need 10k downloads a month to hit that.

I'll have a play with it and see if I can set up a mirror.

@Townsheriff
Copy link
Contributor Author

Townsheriff commented Dec 13, 2021

As I understand *** Data transferred out from public repositories is limited by source IP when an AWS account is not used. part from pricing - people won't be able to pull the image down when they reach 500gb.

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

No branches or pull requests

2 participants