- Más nuevo
- Más votos
- Más comentarios
Problem solved; I NATed to the same private subnet... :D. Don't ask me why... Sorry for troubling you @Tom-B and @kentrad. I was not thorough enough when I inspected the NAT first time. Have a nice weekend!
The "Connection timeout ...." message leads me to believe that the routing for subnet B is not quite right. That is assuming you are running the aws ec2 attach-volume...
command from the instance in subnet B. The CLI can't communicate with the EC2 service.
If you're getting a connection timeout error, I would start by checking that you can reach the ec2 API endpoint from your host by running:
ping ec2.eu-west-1.amazonaws.com
If the ping times out. I'd suggest reviewing your routing tables, security groups and Network ACL's.
Thank you for good suggestions about routing etc @Tom-B and @kentrad. I have looked thoroughly at the routing tables, and to me, they look the same, but I may have missed something. I will have another look tonight and report back. Time for cooking dinner now :)
Contenido relevante
- OFICIAL DE AWSActualizada hace un año
- OFICIAL DE AWSActualizada hace 4 meses
are you 100 Sure the 2nd EC2 is in the same AZ as the volume?