You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Feature- Private endpoints for Lambda Web Functions #114
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 private endpoints for Lambda Web Functions. A private endpoint would be reachable only from your Amazon VPCs and not from the public internet. You could then expose internal web applications and APIs to clients in your VPCs, in connected on-premises networks, and in other accounts that you allow. You would use network-level controls, such as VPC endpoint policies and security groups, together with IAM authorization.
Tell us how you would use this: whether your clients are in the same account, in other accounts, or on premises; whether you need private DNS names or custom domain names; Please add details as comments.
Activity