For this workshop, you will use AWS Session Manager to access several EC2 instances. Session Manager is a fully managed AWS Systems Manager capability that allows you to manage your Amazon EC2 instances and on-premises virtual machines (VMs) through an interactive one-click browser-based shell. Session Manager provides secure and auditable instance management without the need to open inbound ports, maintain bastion hosts, or manage SSH keys.
First cloud journey Lab for indepth understanding of Session manager.
Systems Manager
in the quick search box and press Enter:This EC2 instance is already running in “VPC Cloud” and will be used to test connectivity to Amazon S3 through the Gateway endpoint you just created (s3-gwe).
Session Manager will open a new browser tab with a shell prompt: sh-4.2 $
You have successfully start a session - connect to the EC2 instance in VPC cloud. In the next step, we will create a S3 bucket and a file in it.
cd ~
in the CLIfallocate -l 1G testfile.xyz
, which will create a file of 1GB size named “testfile.xyz”.aws s3 cp testfile.xyz s3://your-bucket-name
. Replace your-bucket-name with the name of S3 bucket that you created earlier.You have successfully uploaded the file to your S3 bucket. You can now terminate the session.
Congratulation on completing access to S3 from VPC. In this section, you created a Gateway endpoint for Amazon S3, and used the AWS CLI to upload an object. The upload worked because the Gateway endpoint allowed communication to S3, without needing an Internet Gateway attached to “VPC Cloud”. This demonstrates the functionality of the Gateway endpoint as a secure path to S3 without traversing the Public Internet.