大网数据广告活动
服务器运维问答

Instance in private AWS subnet with NAT gateway can't access AWS services

· 52CE 我爱测

We have an instance within a private subnet that has a managed NAT gateway. On that instance, we are able to access the internet: $ curl https://www.google.com/ <!doctype html><html itemscope="" itemtype="http://schema.org/WebPag…

问题原文

原帖链接 · JustinHK · CC BY-SA 3.0

We have an instance within a private subnet that has a managed NAT gateway. On that instance, we are able to access the internet:

$ curl https://www.google.com/
<!doctype html><html itemscope="" itemtype="http://schema.org/WebPage" lang="en"><head>...

However, we are not able to access the cloudwatch endpoint, e.g. the following times out: (EDIT: My mistake, not the cloudwatch endpoint, but rather the site storing the cloudwatch monitoring scripts.)

$ curl https://cloudwatch.s3.amazonaws.com

DNS is not the problem:

$ dig cloudwatch.s3.amazonaws.com
cloudwatch.s3.amazonaws.com. 2303 IN    CNAME   s3-1-w.amazonaws.com.
s3-1-w.amazonaws.com.   1   IN  A   54.231.72.59

Any ideas about what might be happening?

已采纳解答

原帖链接 · JustinHK · CC BY-SA 3.0

Adding an S3 endpoint in the private subnet resolved the issue.

It turns out that our problem was specific to accessing S3. Our setup at the time was:

  • NAT gateway running in public subnet
  • S3 endpoint in public subnet (with higher routing priority than the internet gateway)
  • A default rule for traffic in the private subnets to go through the NAT.

It appears that traffic was not getting routed through the NAT to S3 either through the public internet or through the S3 endpoint. I still do not know why.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2016-09-09)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 3.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。