blocks|key|430460|text|您将需要运行在VPC中的NAT服务器来路由VPC之外的流量。AWS现在提供了一个托管NAT业务，使这更容易。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|430461|entityMap|0|LINK|mutability|MUTABLE|url|https://aws.amazon.com/blogs/aws/new-managed-nat-network-address-translation-gateway-for-aws/^0|14|7|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

You will need a NAT server running in your VPC to route traffic outside of the VPC. AWS now offers a <a href="https://aws.amazon.com/blogs/aws/new-managed-nat-network-address-translation-gateway-for-aws/" rel="noreferrer">managed NAT service</a> that makes this easier.

blocks|key|427798|text|更新|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|427799|截至2018年4月，SNS通过AWS+PrivateLink支持PrivateLink。因此，不需要设置Internet网关或NAT实例，就可以让VPC中的Lambda函数发布SNS通知。|427800|有关更多细节，请参见这博客文章。|427801|entityMap|0|LINK|mutability|MUTABLE|url|https://aws.amazon.com/blogs/security/securing-messages-published-to-amazon-sns-with-aws-privatelink/^0|0|2|0|0|A|1|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@$9|S|A|T|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|U|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|V|8|@]|D|@$9|W|A|X|1|Y]]|E|$]]|$1|J|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]]|K|$L|$5|M|N|O|E|$P|Q]]]]

UPDATE

As of April 2018, SNS supports <a href="https://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/vpc-endpoints.html" rel="noreferrer">VPC Endpoints</a> via AWS PrivateLink. So, there will be no need to set up an Internet Gateway or a NAT instance in order for a Lambda function inside your VPC to publish SNS notifications.

See <a href="https://aws.amazon.com/blogs/security/securing-messages-published-to-amazon-sns-with-aws-privatelink/" rel="noreferrer">this</a> blog post for more details.

blocks|key|46118|text|我终于让它起作用了..。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|46119|诀窍是你必须有两个子网。|46120|一个公共的，有一个路由表，发送流量到您的VPC的因特网网关。把纳特放进去。|46121|和一个私人的，有一个路由表，把流量发送给NAT。把兰巴达放进去。(顺便说一句，公开子网意味着将自动分配公共IP选项设置为Yes。)|46122|这个概览图是从AWS文档中概述的：|46123|Scenario2.html#配置-2|offset|length|46124|entityMap|0|LINK|mutability|MUTABLE|url|http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_Scenario2.html#Configuration-2^0|0|0|0|0|0|0|J|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|X|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Y|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|Z|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|10|8|@]|9|@$L|11|M|12|1|13]]|A|$]]|$1|N|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|O|$P|$5|Q|R|S|A|$T|U]]]]

I finally managed to get it working...

The trick is that you MUST have 2 subnets.

A public one, with a routing table that sends traffic to the Internet Gateway of your VPC. Put the NAT in there.

And a private one, with a routing table that sends traffic to the NAT. Put the Lambdas in there. (BTW Making a public subnet means setting the Auto-assign Public IP option to Yes.)

It is outlined in this overview diagram from the AWS docs:

<a href="http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_Scenario2.html#Configuration-2" rel="nofollow noreferrer">http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_Scenario2.html#Configuration-2</a>

blocks|key|46134|text|我知道这是旧的，但是对于那些不想配置NAT的人来说，这是另一个可行的选择。与其尝试在VPC中使用与SNS交互的lambda函数，不如将其拆分为2个lambda函数，如下所示。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|46135|Function+1位于VPC中并与数据库交互，返回数据库交互的结果(例如，与某些条件匹配的ID列表)。|offset|length|style|CODE|46136|Function+2位于VPC之外，调用Function+1，然后处理值数组并发布适当的SNS通知(例如，根据列表中的每个ID发送消息)。|46137|如果有一个SNS的VPC端点，那就更好了，但2016年末似乎并非如此。|46138|entityMap^0|0|0|A|0|0|A|K|A|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@$D|P|E|Q|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@$D|S|E|T|F|G]|$D|U|E|V|F|G]]|9|@]|A|$]]|$1|J|3|K|5|6|7|W|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|M|$]]

I know this is old, but here's another option that works, for those who don't want to configure a NAT. Instead of trying to have a lambda function inside the VPC that interacts with SNS, split into 2 lambda functions, as follows. 

<code>Function 1</code> sits inside the VPC and interacts with the database, returning the result of your database interaction (eg, a list of IDs matching some criteria).

<code>Function 2</code> sits outside the VPC, invokes <code>Function 1</code>, then processes the array of values and publishes the appropriate SNS notifications (eg, sends a message based on each ID in the list).

Would be nice if there was a VPC endpoint for SNS, but still in late 2016 this does not seem to be the case.

I have a lambda function that accesses my Postgres db in RDS via VPC. After it queries the db, I want to post a notification to SNS. Because my lambda function exists in my VPC, it cannot access SNS. I have an internet gateway on my VPC. I read through the VPC endpoint documentation and currently only s3 is supported.

Is there anyway to publish to SNS in a lambda function in a VPC?

How to let AWS lambda in a VPC to publish SNS notification?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我有一个lambda函数，它通过VPC访问RDS中的Postgres db。在查询db之后，我想向SNS发送通知。因为我的lambda函数存在于我的VPC中，所以它不能访问SNS。我的VPC上有一个互联网网关。我阅读了VPC端点文档，目前只支持s3。是否有在VPC中的lambda函数中发布到SNS？

问如何让AWS在VPC中发布SNS通知？
EN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何让AWS在VPC中发布SNS通知？EN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何让AWS在VPC中发布SNS通知？
EN