Closed tejarajaboina closed 4 years ago
Please check if Ec2 mechine is in Private VPC . Please make sure to use Public in VPC to access it from internet
No machine is in Public VPC only
On Tue 17 Dec, 2019, 1:44 AM vinodh2020, notifications@github.com wrote:
Please check if Ec2 mechine is in Private VPC . Please make sure to use Public in VPC to access it from internet
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/QT-DevOps/AWSIssues/issues/58?email_source=notifications&email_token=AF4JZI3CSBZLMFO6EJJMRGTQY7OQRA5CNFSM4J3KC6F2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEG76IUI#issuecomment-566223953, or unsubscribe https://github.com/notifications/unsubscribe-auth/AF4JZI5QJ25JNSTHW6E2LB3QY7OQRANCNFSM4J3KC6FQ .
Please check Route table for VPC subnets, there you can get some clue to allow all Ip's
Hello Teja, To isolate the issue, could you try creating a new EC2 instance in another region, say US-West-2a. Please ensure that you setup a rule in your security group to allow all inbound traffic(for testing purpose).
Secondly, for the new instance, please create and download a new .pem file for connecting to the instance from your terminal.
Please let us know how it works.
Thanks.
Hi Anupam/Vinod,
We have given All Traffic in Security Groups, Network ACL. We gave opte 10.0.0.0/16 in Route tables and 10.0.1.0/24 in subnets. We Associated subnets to route tables. And also associated VPC to respective subnets, NACL, Route Tables. And we made public enabled while creating LINUX EC2 machine, associated respective security groups and created new key pair. We did all this in new AZ. Still it doesn't work.
Hi, Can you attach the screenshots of the EC2 creation and login steps? In EC2 creation, apart from setting up the security group to allow all traffic, please leave other settings such as route tables, etc as is, in default mode.
I’m basically asking you to use the steps mimicking the classroom scenario.
Thanks.
Hi
I have attached whole EC2 Session creation. And Timeout Session error. EC2 Timeout Error.docx
Hello Sai, Thank you for the screenshots.
It seems you are doing it in the Ohio AZ. Can you try it in the US-West-2a ? I had similar problems setting things up in Ohio AZ. Changing it to a different zone helped me.
Please try it and see how it works.
Thanks.
Hi Anupam,
It worked in Oregon, Thanks. But may I know why it didn't work on other regions.
Regards, Sai.
Hello Sai, It probably has something to do with new accounts but not completely sure. Can you try again creating an instance in the Ohio region? If it doesn't work, then you can contact AWS support for assistance. https://support.aws.amazon.com/#/contacts/aws-account-support
Thanks.
please close issue teja
Thanks for your help
please find attached screenshots timeout Error.pdf