Cloud Quest: Resolve VPC Routing Conflicts
I'm trying to understand the issue I am facing in the exercise in the Networking Island: I have updating the routing tables (at least I think I have done it correctly). The environment doesn't seem to give me enough information to properly troubleshoot this. I have tried a number of different attempts at solving this but can't seem to get it right in the DIY section. Can anyone give me a hint beside the one in the exercise - it is not helpful at all.
The activity states: Update the routing table to route traffic between the APP VPC and Database VPC connected by VPC peering. No matter what I do, no matter how I update the table, nothing works. I have to be missing something.
- 最新
- 投票最多
- 评论最多
:
I have not seen this exercise but could you share the screen shots of what it’s asking?
Any examples of the VPC cidr ranges, subnets and peering information would be good.
These are the ranges it has for my environment: Load Balancer: 192.168.0.0/16
Application Server: 10.0.0.0/16
VPC Database: 172.16.0.0/16
App Instance 1: 10.0.0.19 curl -Iv http://10.0.0.19
App Instance 2: 10.0.1.248 curl -Iv http://10.0.1.248
Application Load Balancer: ApplicationLoadBalancer-900711537.us-east-1.elb.amazonaws.com
curl -Iv http://ApplicationLoadBalancer-900711537.us-east-1.elb.amazonaws.com
VPC APP <—> VPC DB
Route Table ID: rtb-0a6ade0a9907d77b3 / vpc-app-private-1 VPC ID: vpc-07db66725066c561c / VPC Application Servers
I've tried just about everything I know to get this and have even solicited the help of others without success. The Hint from the DIY is not very helpful.
相关内容
AWS 官方已更新 1 年前- AWS 官方已更新 8 个月前
If anyone else is fighting with the same assignment in Networking, I can say that the above screenshots helped me see where I was going wrong. I put in too many specific routes and not enough #.0.0.0/16 routes. Once I cleaned up my routes, I got the assignment correct. @KARTHIK did a great job. Thank you,