Does anyone know if we can integrate AWS so that we can push Binder images into ECR?
I have seen few PRs trying implement AWS ECR but none of them have make them to master. Here’s an example:
opened 09:39PM - 24 Oct 18 UTC
I am trying to use ECR as the docker image registry for a BinderHub deployment. … I was looking at the different settings in the helm chart and I am not sure how they map from the GCR examples provided in the docs to ECR.
When explicitly pushing images to a registry, this is the command I use for ECR:
```
docker push 1234567890.dkr.ecr.region.amazonaws.com/repo:tag
```
How to translate this into the various components requested in the values file. Specifically the following in the values that are being set in `configmap.yaml`.
```
registry:
enabled: true
prefix: binderhub-local/
host: https://gcr.io
authHost:
authTokenUrl: https://gcr.io/v2/token?service=gcr.io
username: _json_key
password:
```
For authentication, the nodes in our Kubernetes cluster are allowed to pull from ECR as they have IAM roles configured. Can I leave the authentication options blank here.
Really appreciate the guidance.
So, I would like to know if someone has managed to integrate AWS
manics
July 26, 2024, 6:14am
2
It’s possible, mybinder.org has a member running on AWS EKS.
You’ll need this helper service to handle the AWS specific ECR API calls
A microservice to help BinderHub work with Public cloud container registries
Your can see the mybinder.org configuration in
mybinder.org-deploy/config/curvenote.yaml at 84cecfbdf9258383fcd738d84b9fc895e1e0d5e4 · jupyterhub/mybinder.org-deploy · GitHub
1 Like