- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
There many nuanced differences between these services but the basic idea is that EC2 Instance Connect allows for a convenient and secure native SSH connection using short-lived keys while Session Manager permits an SSH connection tunneled over a proxy connection.
The session manager agent establishes a reverse connection to the service so it is not necessary to, for example, open port 22 on the host. EC2 Instance Connect requires the host security group to permit ssh traffic inbound.
A few other things of note: EC2 Instance Connect supports only Linux EC2 hosts while Session Manager supports Windows and Linux hosts both EC2 Instances and On-prem.
Hope that helps.
The simple answer to this is that after deploying your EC2 instance you want to connect to it ans use it the same way you would use a computer in front of you. Now coming down to the question. 1.)SSH connect -It basically allows you to control a remote machine , all using the command line
- you can configure all the required parameters necessary for doing SSH using the free tool putty 2.) EC2 Instance connect
- Connect to EC2 instance within your browser
- No need to use the key file that you have downloaded
- The best part is that the temporary key is uploaded onto EC2 instance by AWS Hope that helps!
Contenuto pertinente
- In che modo posso risolvere i problemi di connessione alla mia istanza Linux Amazon EC2 tramite SSH?AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata un anno fa
If I understand well, using EC2 instance connect is better than traditional SSH, integrate with legacy access method but it's worse than Session Manager. With Session Manager, we don't need to open port 22 and much simpler configuration. Why don't we just use Session Manager?