Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Feature- Private endpoints for Lambda Web Functions

未关闭
#114 0 条评论 1 个 reaction 已指派 1 人 在 GitHub 查看

@sam-karak 已经在做这个了。

开始于 2026年10月14日。

评估

这个 Issue 还没有评估数据。

描述

Lambda/Web Functions

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 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.

主要语言
没有语言数据
星标
198
派生
5
PR 合并指标
30 天内没有已合并 PR

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

aws/aws-lambda-roadmap 的其他 Issue

查看 aws/aws-lambda-roadmap 的全部 Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。