Create two instances in two different vpc in same region and make them to ping to each other over internal ip(local ip)

 step1: Create Two VPC, one is Privpc and another is Pubvpc.

  


step2: Now create two subnet, one is Pubsub and another is Prisub.


step3: Now create two route tables, one is pubRT and another is PriRT. And attach pubRT to                         pubvpc. Then, PriRT attach with privpc.


step4: Now select pubRT and then below select subnet associate. Then, Edit subnet associate and                 select pubsub (subnet) and Save it.

          Now repeate same like this but this time for PriRT.

          Now sleect PriRT and then below select subnet associcate. Then, Edit subnet associate and                select prisub (subnet) and Save it.
  

step5: Now, create two Internet Gateway, one is pubigw and another is priigw. Then, Attach pubigw with pubvpc and priigw with priVPC.


step6: Now, create two security group, one is prisecgrp and another is pubsecgrp. 
           


      Now, select prisecgrp and go in inbound rules and Edit it. In inbound rules click on add rules            button then select type SSH and source ip 0.0.0.0/0. 
      Then add rules type All ICMP - IPv4 two time and add one time pubsub (subnet) CIDR IP                which you provided and second prisub (subnet) CIDR IP which you provided.

   

step7: Now create two instance one public and another is private. 
  
           In public instance configure : vpc -- pubvpc, subnet -- pubsub, security group -- pubsecgrp.
           Then Lauche instance.
 
           In private instance configure : vpc -- privpc, subnet -- prisub, security group -- prisecgrp.
           Then Lauche instance.

    

step8: Now, Go back to VPC dashboard and click on peering connection from the left hand side                   panel.

          Here, give name pubpeer. Then slecte local VPC to peer with in first VPC ID select pubvpc and            select another VPC to peer with in second VPC ID select priVPC and then click on create                      peering connection.

     


step9: Now, go back to route tables, and select one route pubRT and then select below route and                     click on button edit routes in right hand side below corner.

  


step10: Now, in Edit routes section click on Add route button and then click on target search box and               select internet gateway and choose pubigw and enter destination 0.0.0.0/0 which i hilighted                   in yellow color. 

             Then, click on Add route button again and click on target serach box and select peering                       connection  pubpeer and HERE make sure give correct destination if you doing this edit                 route for pubRT then enter destination of prisub (subnet) CIDR IP which you gave when                 created subnet.

             Same repeat these steps for priRT but just select internet gateway as priigw and in peer                     connection enter destinantion pubsub (subnet) CIDR IP which you gave when ctreated                     subnet.

   


step11: Now all steps done go back to EC2 instance page and connect first public instance and once it              should be connect copy private ip of Private instance. Then enter the command ping and                      paste the private ip of private insatnce like this command:  ping 172.0.0.38.

Now same like connect private instance this time and once it should be connect ping ip of public instance private ip.

   


     You will see same type of output in both instance when you connect and ping each other                     private IPs.   

 

      Thank you.

Comments

Post a Comment

Popular posts from this blog

Error Solving : -bash: /usr/local/bin/kubectl: cannot execute binary file : after Kubernetes installation: you're trying to run the kubectl command on an EC2 instance in AWS

Image
you're trying to run the kubectl command on an EC2 instance in AWS, the first thing to check is whether you've downloaded the correct version of kubectl for your instance's operating system and architecture. follow these steps to resolve it: You can download the correct version of kubectl using the following commands: For Linux x86_64: curl -LO "https://dl.k8s.io/release/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl" copy this link and paste it into your terminal and press Enter. if your system requires arm64 then copy the below link and paste it into the terminal and Enter. For Linux arm64: curl -LO "https://dl.k8s.io/release/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/arm64/kubectl" you will get the following screen. now, Make sure you have the correct version of kubectl for your system architecture. Once you have the correct version of kubectl , Enter the following command: ==> chmod +x kubec...
Read more

Nodejs Application project : using Aws, Jenkins, Docker, Kubernetes

Image
  Step-1: Login to your Aws account and create an instance for Node.js Project. Step-2: Install  Jenkins in your nodejs server (if you don't know how to install Jenkins, follow my DevOps sample project Part -1). Step-3: Once the installation is finished of Jenkins, go to plugin installation and click on Manage Plugins. Then Search for the " Nodejs " plugin and install it. Step-4: Now, Click on New Item and enter the Project Name and select FreeStyle Project . Then click OK . Step-5: write your description and then select the Git option for the git repository clone(if you did not install git plugin , please install it first). Now go back to the dashboard and click on configuration and select Global Tool Configuration, now go down and select node js and enter the name nodejs, and the rest leave it as it is.  Now save it this page and go back to our project Configuration page. Step-6: Enter the Nodejs Project Repository Link. Step-7: Scroll down and select Provide Node...
Read more

Create two public subnets and two private subnets in two different availability zones(AZ) ( one public and one private subnet in each AZ).Create an instance of webserver (like apache ) in each AZ and an instance of db server in any AZ. Attach web servers to ELB and make sure to support cross zone availability.

  Step 1: Create a VPC (if not already created) Go to the Amazon VPC console. Click on "Create VPC." Enter the details such as CIDR block and VPC name. Click on "Create VPC." Step 2: Create the subnets In the VPC console, select "Subnets." Click on "Create subnet." Enter the subnet details such as the VPC ID, availability zone, CIDR block, and subnet name. Repeat the above steps to create the remaining subnets. Step 3: Create the security groups In the VPC console, select "Security Groups." Click on "Create security group." Enter the details such as the security group name, description, and VPC ID. Add inbound and outbound rules as required. Step 4: Launch the instances In the EC2 console, click on "Launch instance." Select the AMI and instance type. In the "Configure Instance Details" section, select the appropriate VPC, subnet, and security group. Configure the rest of the instance settings as required. R...
Read more