Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • Note that curl default is https (if you want to avoid it you should use -k for insecure mode) Commented Oct 13, 2023 at 14:40
  • There's a difference between the AWS metadata service's IP address and the default DNS domain. There is an AWS service waiting to accept connections/requests at the IP address. There is no AWS service waiting for connections to the DNS domain name. aws ec2 describe-tags uses the AWS API and not the IP address or the DNS domain name. Three different things with different documented behaviors. Commented Oct 14, 2023 at 1:40
  • @SottoVoce Thanks. If you've set your region as eu-west-2, aws ec2 describe-tags connects to ec2.eu-west-2.amazonaws.com but in --debug mode this connection stage hangs. Any ideas why? Thanks. Commented Oct 17, 2023 at 8:53
  • Your descriptions of subnet and VPC configuration, descriptions of the aws ec2 describe-tags commands, and which EC2 instances work and don't work are too vague to troubleshoot definitively. My best guess is that you've launched new EC2 instances in private subnets that don't have NAT gateways, or you've launched new EC2 instances in public subnets but haven't given them public IP addresses. Commented Oct 17, 2023 at 13:47