Help us improve the AWS re:Post Knowledge Center by sharing your feedback in a brief survey. Your input can influence how we create and update our content to better support your AWS journey.
My instances can not access AWS public endpoints
I have this error
- connect to 172.31.69.200 port 443 failed: Connection timed out
- Failed to connect to ec2.ca-central-1.amazonaws.com port 443 after 130673 ms: Couldn't connect to server
- Closing connection curl: (28) Failed to connect to ec2.ca-central-1.amazonaws.com port 443 after 130673 ms: Couldn't connect to server
- Newest
- Most votes
- Most comments
Hello.
connect to 172.31.69.200 port 443 failed: Connection timed out
"172.31.69.200" is a private IP address.
Just a guess, are you creating an EC2 VPC endpoint in the VPC where ElasticBeanstalk's EC2 is running?
Enabling private DNS name resolution on a VPC endpoint resolves AWS service endpoints to private IP addresses.
In that case, since you will be accessing "ec2.ca-central-1.amazonaws.com" via the VPC endpoint, you will need to configure the security group for the VPC endpoint to allow HTTPS.
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/interface-vpc-endpoints.html
Relevant content
- asked 9 months ago
- asked 2 years ago
Agreed with Riku, a public AWS service endpoint necessarily has an IP address publicly routable on the internet. The one that you mention is an address coming from RFC1918 which is dedicated to private address. Then it's probably a private service endpoint for which you must configure sec groups appropriately.