Conversation

Notices

1. Embed this notice
   Ellopunk (ellopunk@infosec.exchange)'s status on Wednesday, 15-Feb-2023 00:36:32 JST Ellopunk

   Reporting as I forgot tags

   need help. 
Created a full VPC, DNS resolution has bee. Enabled, internet gateway is attached. Ports open 22, 80, and 443. I can not connect to the instance. (Console or ssh)
Where would you start trouble shooting?

   #aws #cloud

   • Embed this notice
     Blair Gillam (blairgillam@mastodon.social)'s status on Wednesday, 15-Feb-2023 00:36:31 JST Blair Gillam

     in reply to

     @Ellopunk Confirm the route table for your new VPC has routes to the subnet your EC2 instance is in.

     I've deployed EC2 instances to a private subnet that could not use the internet gateway way too many times.

     silverwizard likes this.
   • Embed this notice
     silverwizard (silverwizard@convenient.email)'s status on Wednesday, 15-Feb-2023 00:39:22 JST silverwizard

     in reply to

     • eternalyperplxed
     @eternalyperplxed @Ellopunk Also the outbound security group allows outbound traffic - that being weird has hit me several times
   • Embed this notice
     eternalyperplxed (eternalyperplxed@infosec.exchange)'s status on Wednesday, 15-Feb-2023 00:39:23 JST eternalyperplxed

     in reply to

     @Ellopunk A few things, route table with a default route to the IGW, the EC2 will need a public IP associated with it, double check the network ACL's although the defaults are usually wide open.