Sie sind auf Seite 1von 18

AWS Document Guide

Lab 26
Configuring Endpoint and access the s3 bucket

Scenario: We have required to access s3 service without internet access from private subnet.

Create one windows instance with Public subnet. We need to install command line interface tool in that
instance.

Download the package in public instance.

Page 1 of 18
AWS Document Guide
Go to services and click “VPC”.

Page 2 of 18
AWS Document Guide

Click Endpoints and click “Crete Endpoint”.

Page 3 of 18
AWS Document Guide

Select S3.

Page 4 of 18
AWS Document Guide

Select VPC and select sanbound VPC’s subnet.

Page 5 of 18
AWS Document Guide

Create “Create Endpoint”

Endpoint has been successfully created.

Page 6 of 18
AWS Document Guide

Page 7 of 18
AWS Document Guide
Endpoint is now available.

Page 8 of 18
AWS Document Guide

Create a new subnet in North Virginia.

Page 9 of 18
AWS Document Guide

While creating subnet,

Name tag as “Sansbound_Private_Subnet_NVG”

VPC as “Sansbound_NVG_VPC”.

IPV4 CIDR Block: 192.168.1.0/24

Click “Yes create”.

Page 10 of 18
AWS Document Guide

We can able to see s3 routing information in private routing table.

Page 11 of 18
AWS Document Guide

Create an windows 2016 instance by using regular steps.

Login to private instance.

Copy and paste the command line interface setup in private server. Then run the setup in private subnet
server.

Page 12 of 18
AWS Document Guide

Try to ping google.com from private subnet, you would not able to connect.

Page 13 of 18
AWS Document Guide

Type aws

Page 14 of 18
AWS Document Guide

Type aws s3 ls in command prompt.

S3 can be able to access without internet.

Page 15 of 18
AWS Document Guide

Type aws s3 mb s3://sansbound3

Sansbound3 bucket has been created.

Page 16 of 18
AWS Document Guide

Type

Aws s3 ls

Page 17 of 18
AWS Document Guide

Type

Aws s3 rb s3://sansbound3

Sanbound3 bucket has been removed successfully.

Page 18 of 18