Automate the generation of the ECR token in Serverless endpoint?
I want to use AWS ECR to store my serverless images. However, the token expires and I do not find the way to automate the regeneration. Please, let me know if there is a way of doing this.
8 Replies
Any solution for this yet?
If runpod can take a access ID and key for a User, that it can use to re-authenticate to AWS ECR using get-login-password or whatever fit's runpod implementation. Or is it not viable or required at the moment?
I'm also interested in a potential solution for this, I can use graphQL to save new registry credentials but unfortunately can't update them if they have the same name.
I am also using ECR and was thinking of using a CRON to update the creds but can't because 'update' is not supported yet.
I am also looking for the solution for this. So far from the threads here I gathered that you can use
saveRegistryAuth graphQL method (https://discord.com/channels/912829806415085598/1196527741974106223) to post new set of credentials. So this means taht I can potentially create CI/CD workflow that uses it and creates new set of ECR credentials. But then I am not sure how to update my serverless endpoint, as there seems to be no endpoints for serverless managementHey, any solution to this? I wonder why this issue is so unpopular, everybody is using docker hub?
Unknown User•15mo ago
Message Not Public
Sign In & Join Server To View
Are there any plans to add better support for ECR, or it's low priority?
Unknown User•15mo ago
Message Not Public
Sign In & Join Server To View
Many private container registries use token-based authentication, and we plan to add support for this to our roadmap next quarter. In the meantime, for ECR, a simple approach would be to create a Lambda function or a cron job that generates a new token. then call our GraphQL endpoint to update the container registry authentication.