Configure custom VPC create 2 subnet one is private, and one is public.

1.11. Create VPC

2.  2. Create Subnet and attach with VPC (Ex: Web-Subnet, DB-Subnet)

3.  3. Create an Internet Gateway (Ex: igw-pTools)

4.  4. Create a Route Table and subnet associations.

5.       Route Table-- Define the Destination point (Word Wide Access ip 0.0.0.0/0)

6.  5. Create EC2 Server (Ex: Web-Server, DB-Server)- During creation attach VPC and Enable or Disable public access.

7.   6. Access EC2 -Web-Server with public key

8.       For Access Web server to DB Server internally (local)

9.   7. Create a pair key in Web-Server

             [root@ip-10-0-0-160 ec2-user]# vi pTools_Mumbai_Key.pem

                                                                      Put the Key Data in this file.

108. Provide permission Chmod 600

             [root@ip-10-0-0-160 ec2-user]# chmod 600 pTools_Mumbai_Key.pem

199.Access DB-Server from Web-Server

            [root@ip-10-0-0-160 ec2-user]# ssh ec2-user@10.0.1.151 -i pTools_Mumbai_Key.pem

      Check Internet Accessibility

              [root@ip-10-0-1-151 ec2-user]# ping 8.8.8.8

             We can’t Access from DB Server to Internet. Exit from DB-Server.

              [ec2-user@ip-10-0-1-151 ~]$ exit

1110.Access (ping) the internet from Web-Server

[root@ip-10-0-0-160 ec2-user]# ping 8.8.8.8

PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.

64 bytes from 8.8.8.8: icmp_seq=1 ttl=51 time=1.75 ms

64 bytes from 8.8.8.8: icmp_seq=2 ttl=51 time=1.73 ms

^C

1311. If we want to ping the internet from our DB-Server then it will not connect directly to the internet due to security reasons. So we will create NAT GateWay inside the Subnet (which is connected to the internet Ex: Web-Subnet).

1412. Create NAT GateWay inside Web-Subnet and assign Public Elastic IP.

1513.Create a route table for DB-Server under VPC. Ex-DB-RT

1614.Route table associate's subnet associations and then defines Destination path in route table i.e., internet path. Here use NAT Gateway as Target.

1715. Now internet ping from DB-Server

[ec2-user@ip-10-0-1-151 ~]$ ping 8.8.8.8

PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.

64 bytes from 8.8.8.8: icmp_seq=1 ttl=50 time=1.67 ms


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

Comments

Post a Comment

Popular posts from this blog

                                                                 Cross Account Access of S3 1. Login into the  Root Account   URL: https://signin.aws.amazon.com/signin?redirect_uri=https%3A%2F%2Fap-northeast-1.console.aws.amazon.com%2Fconsole%2Fhome%3FhashArgs%3D%2523%26isauthcode%3Dtrue%26region%3Dap-northeast-1%26state%3DhashArgsFromTB_ap-northeast-1_bd682a7e73e1b5fc&client_id=arn%3Aaws%3Asignin%3A%3A%3Aconsole%2Fcanvas&forceMobileApp=0&code_challenge=lDm7WaCJ6pO8nxyAVOEZy424BsqTJSnoP8RoqTySBBU&code_challenge_method=SHA-256 Username: Email id Password: *********** 2. Create a Bucket and upload an object . EX: Bucket: ec2tos3bucket       Object: Hello1.jpg             Hello2.doc 3. Create User IAM Username:...
Read more
Image
  NACL (Network Access Control List) NACL and the security group both act as a firewall . NACL is used on the Subnet level and Security Group on the instance level. Ø   NACL allows or denies ( Stateless ) specific inbound or outbound traffic at the subnet level. You can use the default network ACL for your VPC, or you can create a custom network ACL for your VPC with rules similar to the rules for your security groups to add an additional layer of security to your VPC.   Ø   Each subnet in your VPC must be associated with a network ACL. You can associate a network ACL with multiple subnets . However, a subnet can be associated with only one network ACL at a time . The previous association is removed when you associate a network ACL with a subnet.   Ø   A network ACL has inbound rules and outbound rules . Each rule can either allow or deny traffic. Each rule has a number from 1 to 32766 . evaluate the network ACL rules when traffic ente...
Read more
  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 ...
Read more