vpc2
private subnet would not allow internet inbound traffic directly, but database has to connect internet and update the patches, todo so , you need to have NAT gateway(elasticip)
database server --> router--> internet gateway--> route tables says (nat-gateway-id) (for ip 00000/0)--then traffic goes to natgateway--> custom route table says (igw-id) it means allowed to go via internet gateway.
High performance 55000 sessions it is not possible only for ec2 instance directly.. without NAT
users cannot route traffic to a NAT gateway through a vpc peer,site to site vpn, or aws direct connect.
1. interface endpoints.. saas solution direct connect.
2. gateway endpoints
1publci subnet
- 2. private subnte
3. public route table
4.private route table associate vpc, assign subnet.
5.internet gateway
6. natgate name it, then selecct in public subnet., associate elasitc ip, create natgw.
7. open publicroutetable, edit routes, add rount to internet 0.0.0.0/0 target igw
8.select pvt routtable. edit add route --0.0.0.0/ nat gw in the target.
- 1. create vpc -- vpcname2
- 2. 10.101.10.16/ create vpc
- create internet gateway
3.
Comments
Post a Comment