E04 - Demonstration of AWS VPC and Launch A Web Server
E04 - Demonstration of AWS VPC and Launch A Web Server
Experiment No.:04
Objectives: After completing this lab, you should be able to do the following:
Create a VPC.
Create subnets.
Configure a security group.
Launch an EC2 instance into a VPC
In this lab, you will use Amazon Virtual Private Cloud (VPC) to create your own VPC and
add additional components to produce a customized network. You will also create a security
group. You will then configure and customize an EC2 instance to run a web server and you
will launch the EC2 instance to run in a subnet in the VPC.
Amazon Virtual Private Cloud (Amazon VPC) enables you to launch Amazon Web Services
(AWS) resources into a virtual network that you defined. This virtual network closely
resembles a traditional network that you would operate in your own data center, with the
benefits of using the scalable infrastructure of AWS. You can create a VPC that spans
multiple Availability Zones.
Architecture
Looking at this LAB, in summery of VPC component that need to make web servers
accessible publicly while keeping application and database servers are private are,
1) One VPC with public subnet for web servers and private subnet for database or app
servers.
2) In order to communicate with these two subnets you need a router. router in AWS direct
communicate within subnets. Implied router term in AWS means routing table. it is a
gatekeeper in vpc networking denote how traffic flows in and out subnet in the VPC. implied
router does not make intelligent routing decision hence we need to configure routing decision
manually.
3) In order get internet access for these subnets we need a internet gateway. Internet gateways
is highly available component in the VPC that connects vpc to the internet.
4) If private subnet need to access internet (such as host update patches etc…) we need to
configure NAT gateway which is a VPC service reside in public subnet. however, in order
make this work, it is recommended to configure route tables for each and every subnet that
point interested traffic whether to internet gateway or NAT gateway.
5) If private subnet need to access vpc services such as S3 bucket, we need to set up a vpc
endpoint that makes private subnet to connect S3 services in AWS backbone directly rather
than using internet gateway (saves cost for egress traffic)
6) Security within the VPC provided by Network access control list and security groups.
NACL secure inbound and out bound traffic for subnets and Security groups provide secure
access to the EC2 instance
if you really need to enable transit traffic (typically hub and spoke design) then you need to
define a new VPC dedicated for transit traffic which also has a router software as a instance
that can peer with other instance (eventually connect to their implied routing tables) and
install static or dynamic routing protocol to route traffic. this type of scenario will be used
hybrid cloud environment when multiple AWS VPCs in a single or multi region need to
connect to On premises network. Site-to site VPN connectivity would be involved in this type
of VPC design.
Conclusion Note: (Student write their understanding and findings in this lab demonstration)