Book Image

Practical AWS Networking

By : Mitesh Soni
Book Image

Practical AWS Networking

By: Mitesh Soni

Overview of this book

Amazon Web Services (AWS) dominates the public cloud market by a huge margin and continues to be the first choice for many organizations. Networking has been an area of focus for all the leading cloud service providers. AWS has a suite of network-related products which help in performing network related task on AWS. This book initially covers the basics of networking in AWS. Then we use AWS VPC to create an isolated virtual cloud for performing network-related tasks. We then provide an overview of AWS Direct Connect after taking a deep dive into scalability and load balancing using the auto scaling feature, Elastic Load Balancing, and Amazon Route S3. Toward the end of the book, we cover troubleshooting tips and security best practices for your network. By the end of this book, you will have hands-on experience of working with network tasks on AWS.
Table of Contents (15 chapters)
Title Page

An overview of networking services

In this section, we will look at an overview of networking services. We will cover them in more detail in the upcoming chapters:

Let's start with Amazon Virtual Private Cloud.

Amazon Virtual Private Cloud

Amazon Virtual Private Cloud (Amazon VPC) is more secure because it allows you to create instances in a logically isolated virtual network.

The following screenshot shows a few of the components that are important in the Amazon VPC:

AWS Accounts only support EC2 instances in VPC. Now, do you need to create a VPC the moment you create your account?

The answer is no. A default VPC is available in the Amazon VPC. If you delete the default VPC, then you cannot restore it—you would need to contact AWS Support to do so:


The default VPC contains the following:

  • A VPC with a size /16 IPv4 CIDR block ( This means that you have 65,536 private IPv4 addresses. For more details on CIDR, check out the following link:
  • Default subnet /20 in each Availability Zone. Here, you have 4,096 addresses per subnet.
  • One internet gateway.
  • A main route table for the default VPC.
  • A default security group that must be associated with your default VPC.
  • A default network Access Control List (ACL):

Perform the following steps to display the subnets available in your VPC dashboard:

  1. Click on Your VPCs in the VPC Dashboard.
  2. Verify the VPC ID, State, IPv4 CIDR, Route table, Network ACL, and so on:

The subnet can be defined as a section of a VPC's IP address range, and is where you can place groups of isolated compute resources.

Each subnet in a default VPC has 4,091 addresses available, and each subnet is created in the different Availability Zones.
  1. Click on Subnet on the left sidebar in the VPC Dashboard. Below Subnets, we have Route Tables, Internet Gateways, NAT Gateways, and Elastic IP addresses:
    • Route Tables help us define subnets that need to be routed to the Internet Gateway, the virtual private gateway, or other instances.
    • Internet Gateway allows you to connect to the public internet from an Amazon VPC.
    • NAT Gateway represents a highly available and managed Network Address Translation (NAT) service for resources in a private subnet so that they can access the internet. A NAT gateway is created in a public subnet.
    • An Elastic IP address is a public static IPv4 address, and is used so that you can access the resource. If an Elastic IP address is not allocated with a running instance, then an hourly charge has to be paid by the user.

In the next section, we will discuss Amazon CloudFront.

Amazon CloudFront

Amazon CloudFront is a Content Delivery Network (CDN) service. It helps ensure speedy content delivery to the user, along with the use of edge locations that have been established by AWS.

Go to AWS Management Console | Services | Networking & Content Delivery | CloudFront:

The following sequence takes place when the user requests static or dynamic content:

  • If the content is available in the edge location near the user, CloudFront delivers the content immediately
  • If the content is not available in the edge location near the user, CloudFront requests content from the source, such as an Amazon S3 bucket or an HTTP server, and delivers it to the user

In the next section, we will discuss Amazon Route 53.

Amazon Route 53

Amazon Route 53 is a domain name or DNS service. It is a reliable and scalable service that has DNS servers distributed globally. It scales automatically to manage the spike in DNS queries so that services are robust.

Let's talk about what services it provides to a user. The following services are available when using Amazon Route 53:

  • A highly available domain name system
  • Domain name registration
  • Health checks
  • A scalable domain name system

Go to AWS Management Console | Services | Networking & Content Delivery | Route 53:

In the next section, we will cover AWS Direct Connect in brief.

AWS Direct Connect

Can we connect to AWS from the internal network of an organization without accessing the internet? The answer is yes!

It's quite simple! Connect the internal network to the AWS Direct Connect location using a standard 1 Gigabit or 10 Gigabit Ethernet fiber-optic cable. Once you have done this, you can create virtual interfaces that connect to AWS services.

Go to AWS Management Console | Services | Networking & Content Delivery | Direct Connect:

In the next section, we will cover Elastic Load Balancing in brief.

Elastic Load Balancing

Elastic Load Balancing/Elastic Load Balancers (ELB/ELBs) can be used to distribute traffic to multiple targets. ELB can be configured on Amazon VPC and Amazon Elastic Beanstalk. It only distributes traffic to healthy targets.

There are two types of load balancers that are supported by Elastic Load Balancing:

  • Application Load Balancers
  • Classic Load Balancers:

Go to AWS Management Console | Services | EC2 | EC2 Dashboard | Load Balancing | Load Balancers:

In the next section, we will cover Auto Scaling in brief.

Auto Scaling

Auto scaling creates a scenario where you have an appropriate number of instances or targets to serve the traffic load based on certain conditions. Based on configured Auto Scaling policies, instances are increased and decreased on demand.

Go to AWS Management Console | Services | EC2 | EC2 Dashboard | Auto Scaling | Launch Configurations or Auto Scaling Groups:

In the next section, we will cover the AWS Billing Dashboard.