Virtual Private Cloud Peering for

High Integrated and Secure Data

Project submitted by:-

Adnaan Arbaaz Ahmed (16WJ1A1202)

B. Sri Vatsav (16WJ1A1205)
Vanam RajKumar (16WJ1A1253)
Rajesh Durganath (17WJ5A1202)
Introduction:
●
A Virtual Private Cloud is an on-demand
configurable pool of shared computing
resources allocated within a public cloud
evironment, providing a certain level of isolation
between the different organizations (denoted as
users hereafter) using the resources.
●
A VPC peering connection is a networking
connection between two VPC’s that enables
you to route traffic between them using private
Ipv4/Ipv6 addresses.
Contd...
●
Instances in either VPC can communicate with
each other as if they are in the same network.
●
You can create a VPC peering connection
between your own VPC’s, or with a VPC in
another AWS account.
●
The VPC’s can be in different regions called as
inter-region VPC peering connection.
Abstract:
●
Confidential and high integrated data is secured
by instanciating another private intermediate for
filter IP’s from unknown sources, the security
over data is achieved.
●
A VPC peering connection helps you to
facilitate the transfer of data with more secure
environment by different or same Availability
Zone regions to communicate with each other
using private IP addresses, without requiring
gateways, VPN connections, or separate
network appliances.
Existing Approach:-
●
The network is everything in this world. For any
data communication, there should be a network
which contains Router, Servers, Switch,
Computers, Racks, Cable etc.. For setting up
these kinds of network infrastructure on on-
premises datacenter it takes a lot of effort and
investment. And again there is a need to handle
the cost of maintenance and services,
protection from fire surges, solutions for
disaster recovery, and having security patches
etc... Overall it may take a few months to have
this type of setup.
Proposed Approach:-
●
Amazon provides services in the form of Amazon Web
Services (AWS) to make it easy for all these setups.
You can set-up all the IT infrastructure as per your
requirements within a few minutes.
●
AWS provides Amazon VPC service for creating a
private cloud network. Using Amazon VPC you can
create multiple virtual networks as needed.
●
In AWS, Instances within the VPC can communicate
with each other but it can’t communicate with another
instance in a different VPC. By default, Amazon has
disabled the communication between the private
VPCs. To enable the VPC sharing on the private
network in AWS, we need to have Amazon VPC
System Requirements:-
●
Constant Internet Connection
●
Internet Browser
●
An AWS account
Modules:-
●
Creating a VPC
●
Configuring Internet Gateways
●
Configuring Subnets
●
Configuring Route Tables
●
Configuring Security Groups
●
Creating an instance
Module 1: Creating a VPC
●
Open the console https://console.aws.amazon.com/vpc/.
●
Click on launch a new VPC
●
Provide the credentials
1) IP CIDR block (10.0.0.0/16)
2) VPC name (Mini-Project-A)
3) Public Subnet (10.0.0.0/24)
4) Availability Zone (No Preference)
5) Subnet Name (Mini Subnet1)
6) Enable DNS host names (Leave Default Selection)
7) Hardware Tenancy (default)
Module 2:- Configuring Internet Gateway

●
Open the console
https://console.aws.amazon.com/vpc/.
●
Navigate to Internet Gateways
●
Provide the name for the gateway
Name (Mini-IG) Create
●
Attach it to VPC (Mini-Project-A)
 Module 3:- Configuring Subnets
●
Open the console
https://console.aws.amazon.com/vpc/.
●
Select Subnets
●
Enter the following cradentials:
1)Name (Mini-PubSN)
2)Attach it to VPC (Mini-Project-A)
3)Provide Ipv4 CIDR (10.0.0.0/24)
Module 4:- Configuring Route Tables
●
Open the console https://console.aws.amazon.com/vpc/.
●
Select Route Table
●
Click on create
●
Provide the following credentials:
1) Name (Mini-PubRT)
2) Attach it to public Subnet (Mini-PubSN)
3) Under routes... edit
4) designation (0.0.0.0/0)
5) target (Mini-IG)
6) associate it with Mini-PubSN
●
Save
Module 5: Configuring Security Groups
●
Open the console http://console.aws.amazon.com/vpc/
.
●
Select Security Groups
●
Provide the following credentials:
1)Name (Mini-SG)
2)Allow traffic from:
3)SSH---> source (My IP)
4)SSH---> source:custom (10.0.0.0/24)
5)All ICMP ---> rpivate instance of VPC (Mini-Project-B)
●
Save
Module 6:- Creating an Instance
●
Open the console https://console.aws.amazon.com/ec2/.
●
Click on launch instance
●
Choose AMI (Amazon Machine Image) and Instance type.
●
Configure instance details:

1) Network

2) Subnet

3) File Systems
●
Select Storage and add Tags
●
Configure Security Groups

1) Type: SSH

2) Protocol: Tcp

3) Port Range: 22

4) Source: Anywhere (0.0.0.0/0)

●
Choose Review and Launch
●
Click on Launch
Conclusion:
●
After the VPC peering connection is made, the local
and the peer tenants must add rules in the local and
peer VPC’s to enable the communication between the
two connected VPC’s
●
VPC A is peered with both VPC B and VPC C. If VPC
B and VPC C have overlapping CIDR blocks, routes
with the same destinations cannot be added in VPC A.
●
To ensure Security, user must not accept connection
requests from unkonwn tenants.
●
We cannot delete a VPC for which VPC peering
connection routes have been configured.
References:-
●
https://docs.aws.amazon.com
●
https://docs.aws.amazon.com/vpc/latest/userguide/what-is-amazon-vpc.html
●
www.wikipedia.org
●
Adnaan Arbaaz Ahmed, Dr. M.I. Thariq Hussan, “Cloud Computing: Study of
Security Issues and Research Challenges”, International Journal for
Advanced Research in Computer Engineering and Technology Volume 7,
Issue 4, 362-369, April 2018.
●
Adnaan Arbaaz Ahmed, Dr. M.I. Thariq Hussan, Venkateswarlu Bollapalli,
“Upgrade- Data Security in Cloud by Machine Learning and Cryptography
Techniques”, International Journal of Engineering and Advanced Technology
Volume 8, Issue 6, 2728-2732, August 2019.