VPC Endpoint

VPC Endpoint issue in place of NAT gateway because when we use NAT gateway services, charges are higher as AWS charge for NAT gateway, Download and Upload data charge.

VPC Endpoint is free and AWS charges nominal for services access.

1.       Create VPC

2.       Create Two subnets: one for public IP and one for private IP.

3.       Create an IGW gateway

4.       Attach IGW gateway with VPC.

5.       Create a Route Table

6.       Define the IGW gateway path in the route table.

7.        Define the path for the public subnet to go to the internet i.e. Subnet association select subnet which have public access.

8.       Create two EC2 instances: one with Public IP in one subnet and one with private IP in one subnet.

9.       Create Endpoints in VPC. Select AWS services for S3 gateway service and VPC and private Subnet.

10.    Access Public IP EC2 Machine.

11.   Create one File for keypair in an EC2 machine like vi keypair.pem

12.    Put the keypair secret code in the file keypair.pem and exit from file

13.   Give Permission to file like chmod 700 keypair.pem

14.   Access private EC2 server machine like SSH -I keypair.pem  ec2-user@172.168.2.2

15.   Go to in root account of the private server like sudo su –

16.   Configure Aws in a private server like aws configure and put the access key and secret key

17.   Check bucket availability like aws s3 ls

18.   If the bucket does not exist then create a bucket like aws s3 mb s3://bucketname

19.   Put some objects in a bucket and check objects like aws s3 ls s3://bucketname

20.   Check bucket can delete like aws s3 rb s3://bucketname (object delete manually from bucket first after that it will remove only)

Note: This all is done through Endpoint. if we delete the endpoint then we can’t access the aws services S3.

 *******************Happy Learning*****************

Comments

Popular posts from this blog