This allows you to use Session Manager without any inbound connections. Increased Security: This configuration works with only one Amazon Elastic Compute Cloud (Amazon EC2) instance (the bastion host) with outbound port 443 connecting to Systems Manager infrastructure. So, what are the benefits of having this configuration: A managed instance that you create acts as a bastion host, or gateway, to your AWS resources. This capability means that Session Manager tunnels real SSH connections, allowing you to tunnel to another resource within your VPC directly from your local machine. Session Manager is a fully managed AWS Systems Manager capability that lets you manage your Amazon Elastic Compute Cloud (Amazon EC2) instances, on-premises instances, and virtual machines (VMs) through an interactive one-click browser-based shell or through the AWS Command Line Interface (AWS CLI). What is AWS Systems Manager Session Manager? Thanks to AWS for the wonderful documentation. Mentioned below is the diagram for a better understanding of the scenario.īefore talking about the solution let’s have a look at the AWS Systems Manager Session Manager in a nutshell. It is a tiring job for the developers to connect through the Bastion Host or Jumpbox to query something from the Database. We are using VPC peering to establish connection between the lambda functions and MongoDB. I am working on an interesting project which involves lots of integrations where AWS Lambda functions and a document database (MongoDB) are deployed in two separate VPC networks. Log story short, Yes its possible with the help of AWS Systems Manager Session Manager. How awesome is to access either a MongoDB or MySQL deployed in a VPC network locally using MongoDB Compass or MySQL Workbench ?Īt this point you might think that, how is it possible to tunnel to another resource within VPC directly from your local machine?

Bastion ssh tunnel