Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AWS Three Tier Web Architecture > Part 3: App Tier Instance Deployment > Connect to Instance #103

Closed
Tracked by #13
tungbq opened this issue Jun 14, 2023 · 5 comments · Fixed by #111
Closed
Tracked by #13

Comments

@tungbq
Copy link
Owner

tungbq commented Jun 14, 2023

Automate: https://catalog.us-east-1.prod.workshops.aws/workshops/85cd2bb2-7f79-4e96-bdee-8078e469752a/en-US/part3/connecttoinstance

@tungbq
Copy link
Owner Author

tungbq commented Jun 17, 2023

Cannot connect to EC2 via Session Manager:

  • Checked the IAM -> OK
  • Need check SG
  • Need check AMI? ami-090e0fc566929d98b

@tungbq
Copy link
Owner Author

tungbq commented Jun 17, 2023

Hanging:
image

@tungbq
Copy link
Owner Author

tungbq commented Jun 17, 2023

Done:

sh-4.2$ sudo -su ec2-user
[ec2-user@ip-10-0-3-9 bin]$ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=106 time=1.79 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=106 time=1.20 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=106 time=1.50 ms
^C
--- 8.8.8.8 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 1.206/1.501/1.796/0.244 ms
[ec2-user@ip-10-0-3-9 bin]$

@tungbq
Copy link
Owner Author

tungbq commented Jun 17, 2023

SUMMARY:

  • Learn from the SSM doc
  • After the instance is spined up, wait a little time

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant