The official documentation has the most detail, but the short answer is: You can either use the AWS Console for web access, or the AWS CLI for a native "terminal" experience. All access is based on IAM permissions, and sessions are proxied by AWS Systems Manager. Session Manager gives you remote access to your servers without opening any ports in security groups, building any VPN tunnels, or using bastion hosts. While not a very magical name, it does provide a magical experience. And with the rise in "Zero Trust" networking, how do you securely provide access without blindly trusting network CIDR's?Įnter AWS Systems Manager Session Manager. ![]() This can increase in complexity very quickly with multiple VPC's across multiple regions, multipied by each AWS account. ![]() As you get more advanced, you setup VPN tunnels or bastion hosts to secure your remote access. Worst case, your server has a public IP with port 22 (SSH) open to the world, which means theoretically anyone, anywhere in the world could break in. When working with AWS, there are plenty of features that make your life easier, but it's rare to find a feature that feels like magic.īefore we dive into the magic, what's the problem we're trying to solve? When working with servers anywhere, usually there needs to be some sort of remote access to SSH or RDP and install/troubleshoot things as needed.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |