简体   繁体   English

尝试通过AWS中的nat实例从私有子网实例访问Internet时遇到问题?

[英]Getting issue while trying to access internet from private-subnet instance via nat intance in aws?

I create a vpc with two subnets public and private. 我创建具有两个子网public和private的vpc。

In public subnet I used NAT instance for internet access. 在公共子网中,我使用NAT实例进行Internet访问。 I trie to access internet which is in private subnet, but failed. 我试图访问位于专用子网中的Internet,但失败了。 I configured well for security groups and route tables. 我为安全组和路由表进行了很好的配置。 Is it necessary that NAT instance should be of m1.small type? NAT实例是否必须为m1.small类型?

No nat box can have any instance type. nat框不能有任何实例类型。 However, in your private subnet's Route table, there should be an entry like this 但是,在您的私有子网的“路由”表中,应该有一个像这样的条目

Destination cidr: 0.0.0.0/0 Target: 目标cidr:0.0.0.0/0目标:

If this is already in place, then check the security group. 如果已经存在,请检查安全组。 For testing try to open all traffic in all security groups that you have. 为了进行测试,请尝试打开您拥有的所有安全组中的所有流量。

there might be chance you have not selected correct NAT instance while creating NAT instance in Step 1: Choose an Amazon Machine Image (AMI) 步骤1:选择Amazon Machine Image(AMI)中创建NAT实例时,您可能没有选择正确的NAT实例。
make sure you instance name contain "nat" , 确保您的实例名称包含“ nat”

after clicking on Community AMIs and add filter for nat , it is not filtering correct name , make sure your instance name should contain "nat" 单击社区AMI并为nat添加过滤器后,它没有过滤正确的名称,请确保您的实例名称应包含“ nat”

below are only nat Amazon Machine Image (AMI) available in community 以下是社区中仅提供的nat Amazon Machine Image(AMI)

  • amzn-ami-vpc- nat -hvm-2018.03.0.20180811-x86_64-ebs amzn-ami-vpc- nat -hvm-2018.03.0.20180811-x86_64-ebs
  • amzn-ami-vpc- nat -hvm-2017.09.1-testlongids.20180307-x86_64-ebs amzn-ami-vpc- nat -hvm-2017.09.1-testlongids.20180307-x86_64-ebs
  • amzn-ami-vpc- nat -hvm-2017.09.1.20180103-x86_64-ebs amzn-ami-vpc- nat -hvm-2017.09.1.20180103-x86_64-ebs

暂无
暂无

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 从NAT实例后面的AWS VPC私有子网访问ftp - ftp access from AWS VPC private subnet behind a NAT instance 私有子网中的 AWS EC2 实例无法通过 NAT 网关连接到互联网 - AWS EC2 instance in private subnet unable to connect to internet via NAT gateway 通过AWS中的NAT实例从专用子网访问Internet - Internet access from Private Subnets through NAT instance in AWS AWS:SSH 通过 NAT 网关从公共 su.net EC2 实例到私有 su.net EC2 实例没有发生 - AWS : SSH to private subnet EC2 instance from public subnet EC2 instance via NAT GATEWAY is not happening 带有NAT设置的Internet无法访问AWS Public / Private子网 - AWS Public/Private subnet not accessible to internet with NAT setup AWS - 使用 NAT 网关(由 Lambda 访问)的私有子网中的 EC2 代理到无服务器 Aurora 的 Internet 访问 - AWS - Internet Access for an EC2 Proxy to Serverless Aurora in a Private Subnet with NAT Gateway (Accessed by Lambda) 在AWS上将端口从互联网转发到私有子网实例 - Port forwarding on AWS from the internet to private subnet instance 如何在 AWS 中将私有子网连接到 Internet,而无需 NAT 或 EIP? - How to connect a private subnet to internet without NAT nor EIP in AWS? 如何通过NAT实例连接到专用子网中的RDS实例 - How to connect to RDS Instance in private subnet via NAT instance 如何在通过 nat 网关连接到 Internet 的私有子网中配置 NACL? - How to configure a NACL in a private subnet connected to internet via nat gateway?
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM