#SSH

Instance interactive access

Generally, we create Linux instances allowing port 22 to access via SSH. Using AWS Systems Manager Session Manager instead of directly accessing via SSH we don't need inbound rules to open ports in Security Groups. There are no inbound rules. Normally we’d require tcp 22 to ssh into this instance. If we go back to Systems Manager, we can go to instance actions, start a session, and..what’s gonna happen? We are connected to our instance! We strongly recommend using AWS Systems

Did you know there is a better way to connect to your AWS Linux Instances than SSH?

For years, you used SSH as the only way to access your ec2 instances, surely you've exposed port 22 to anywhere (0.0.0.0/0) making your instances or bastion instances reachable from anyone on the internet. Some people prevent this by implementing VPN solutions, which increases the complexity and potential points of failure and tons of maintenance tasks. Your search ended right here, there is a great tool that allows you to connect to the Linux terminal, SSM Session Manager. T

Say no more to SSH keys, SSM is THE tool

The remote access login is the barrier that intruders must break in order to steal information. Several options have tried to help us in the prevention of intrusions. However, there is a reality: our physical device, while providing availability, is vulnerable to possible attacks due to its permanent connection to the net. Even the preservation and administration of private keys bring inconveniences related to physical devices or human errors. AWS brings the evolution, with S