Bring your own container registry
- Dominant language
- No language data
- Stars
- 196
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
**Note**
> * Please vote on this issue by adding a 👍 reaction 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 providing additional feedback, please leave a comment
**Description**
Add support to create Lambda functions from container images hosted in third-party container registries.
**Additional Context**
1. What authentication methods should we support?
2. What container registries do you use?
3. How would you expect Lambda to connect to your network?
Contributor guide
Research direction
Start with the issue description and its authentication, registry, and network-connectivity questions. Determine which third-party registries and authentication methods should be supported, then define completion as Lambda functions being creatable from images hosted in those registries.
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
- Needs clarification
- Newbie friendliness
- 25/100