[Lambda] [request]: Cross-region cross-account ECR images
- Dominant language
- Shell
- Stars
- 5.4k
- Forks
- 334
- PR merge metrics
- No merged PRs in 30d
Description
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment
**Tell us about your request**
What do you want us to build?
The possibility to use cross region cross account ECR images for Lambda.
**Which service(s) is this request for?**
This could be for ECR and Lambda
**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
Back in the days if someone wants to use a Lambda functions in cross account and cross region the Lambda Zip have to be copied into that account and that region, consumeing S3 buckets per every region. What is the reason we have to do the same procedure for container images by replicating them into specific regions? The dockerhub isn't bounded to any AWS region so they can be used as well for Lambdas.
The ECR private repository should be used for Lambdas with the freedom of cross region and cross account, without unecessary cost by the unwanted replications.
So I want to use Lambdas with container images as the following workflow:
(MyPrivate-ECR at eu-central-1 in Account A) --> (XYZ Lambda function at eu-west-1 in Account B)
Contributor guide
Research direction
Review the requested workflow in issue #1281: an ECR image in eu-central-1 and Account A used by a Lambda in eu-west-1 and Account B. No implementation files, tests, or entry points are identified in the issue; done would mean cross-region, cross-account ECR images can be used by Lambda without regional replication.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100