[ECR] [request]: support custom domains, or alternate URIs for repositories
**Tell us about your request** Currently a repository URI looks like this: `<account_id>.dkr.ecr.<region>.amazonaws.com/<repository>`. Account ID and region might be movable parts which has negative effects for the following scenarios described. It would be helpful to be able to define an alternate URI for ECR repositories. **Which service(s) is this request for?** ECR, (.. and maybe other container services?) **Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?** Our team provides a docker image for ~12 other teams that acts as a build tool for frontend resources within their pipelines. We identified different disaster recovery scenarios where the current ECR URI is a disadvantage: (1) Unavailability of ECR within the specified region - For this case *all* teams would have to change the URI of our repository or won`t be able to deploy frontend resources instead, until ECR is reachable again. (2) Disaster recovery for the ECR account - When the account which contains the ECR repository is (e.g.) compromised or we have to do a complete disaster recovery for other reasons, then *all* teams would have to change the URI of our repository. This is a dependency we could prevent.. An alternate repository URI could be a fixed interface for other consumers. Changes for account ID or region behind this part would not affect them anymore. **Are you currently working around this issue?** One way we had seen to "solve" this, is to use an
Posted by philippmoehler0440 on May 20, 2019, 8:26 AM
Tags
Related issues
- some bike vendor told me that the biggest problem with regular to ebike conversion was that regular bike frames were not strong enough to...
- I think of this as the kiosk economy.
- What a goofy comment.
- There's lots of evidence for positive influences of Caffeine on the body (some negative as well), especially the brain.
- Compose support in WSLc
- [RFC] Roadmap to v2.0
Raise real-world problems, find people facing the same issue, and discuss solutions.4,000 issues0 comments
support (Other)
some bike vendor told me that the biggest problem with regular to ebike conversion was that regular bike frames were not strong enough to...
I think of this as the kiosk economy.
What a goofy comment.
There's lots of evidence for positive influences of Caffeine on the body (some negative as well), especially the brain.
Compose support in WSLc
[RFC] Roadmap to v2.0
[Feature]: Add TurboQuant Support for KV Cache Quantization
Support for AGENTS.md and .agents/skills/, the community has been asking since August 2025
[ECR] [request]: support custom domains, or alternate URIs for repositories
**Tell us about your request** Currently a repository URI looks like this: `<account_id>.dkr.ecr.<region>.amazonaws.com/<repository>`. Account ID and region might be movable parts which has negative effects for the following scenarios described. It would be helpful to be able to define an alternate URI for ECR repositories. **Which service(s) is this request for?** ECR, (.. and maybe other container services?) **Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?** Our team provides a docker image for ~12 other teams that acts as a build tool for frontend resources within their pipelines. We identified different disaster recovery scenarios where the current ECR URI is a disadvantage: (1) Unavailability of ECR within the specified region - For this case *all* teams would have to change the URI of our repository or won`t be able to deploy frontend resources instead, until ECR is reachable again. (2) Disaster recovery for the ECR account - When the account which contains the ECR repository is (e.g.) compromised or we have to do a complete disaster recovery for other reasons, then *all* teams would have to change the URI of our repository. This is a dependency we could prevent.. An alternate repository URI could be a fixed interface for other consumers. Changes for account ID or region behind this part would not affect them anymore. **Are you currently working around this issue?** One way we had seen to "solve" this, is to use an
Comments (0)
No comments yet. Start the discussion.