Skip to main content

AWS Networking: How It Differs From Your Data Center

AWS networking shares a lot in common with the way you run things locally; we’ll discuss some differences.

In this article, I’m going to break AWS networking down to its basic building blocks to offer some big-picture insight. By the way, you might enjoy Cloud Academy’s course on VPCs and AWS networking.

The following are what I believe the main network-oriented services on AWS:

  • Amazon Virtual Private Clouds (VPCs) let you launch AWS resources into virtual, isolated networks defined to perfectly fit your needs.
  • AWS Direct Connect links your local network to your AWS resources through an AWS Direct Connect location over a standard 1 gigabit or 10 gigabit Ethernet fiber-optic cable.
  • Amazon Route 53 provides a highly available and scalable Domain Name System (DNS) web service.

AWS Networking: Virtual Private Cloud (VPC)

Properly understanding VPCs is critically important not only for AWS Networking but for successfully working with AWS itself. As always, AWS’s documentation is a great place to start.

Here’s their definition:

Amazon Virtual Private Cloud (Amazon VPC) enables you to launch Amazon Web Services (AWS) resources into a virtual network that you’ve defined. This virtual network closely resembles a traditional network that you’d operate in your own data center, with the benefits of using the scalable infrastructure of AWS.

So if you’re already familiar with networking, you are in luck: AWS networking’s use of virtual networks closely resembles a traditional network that you’d operate in your own data center. but even if you’re still a bit new to the scene, you can hopefully still pick up some important basics.

How is AWS VPC Networking different?

1.  AWS Networking Configurations

Assuming you have an AWS account you should already have a configured VPC waiting for you. If you’d like to roll your own, open your VPC dashboard an select “Start VPC Wizard” you will see these four choices:

  1. VPC with a Single Public Subnet.
  2. VPC with Public and Private Subnets.
  3. VPC with Public and Private Subnets and Hardware VPN Access.
  4. VPC with a Private Subnet Only and Hardware VPN Access.

For the time being forget about the last two – which involve connecting to an external VPN – and concentrate on numbers one and two.

In a VPC with a Single Public Subnet, your instances run in a private, isolated section of the AWS cloud with direct access to the Internet. Network Access Control Lists and Security Groups can be used to provide close control over inbound and outbound network traffic to your instances.

In a VPC with Public and Private Subnets, besides a public subnet, this configuration adds a private subnet whose instances are not addressable from the Internet. Instances in the private subnet can establish outbound connections to the Internet via the public subnet using Network Address Translation (NAT).

2.  Subnets

So subnets come in two flavors, public and private. Here’s how they work:

  • If a subnet’s traffic is routed to an Internet gateway, the subnet is known as a public subnet.
  • If a subnet doesn’t have a route to the Internet gateway, the subnet is known as a private subnet.

Some other things to know about subnets:

  • A Subnet lives within a VPC and within a single Availability Zone
  • You can have multiple Subnets within a VPC that live in different Availability Zones

3.  Regions and Availability Zones

AWS regions are completely isolated from each other. To reduce network traffic latency, it is usually best to choose a region that’s geographically close to you or your resources. While each AWS region is isolated, there are multiple Availability Zones within a region that are connected to each other via low-latency links.

4.  Security Groups and NACLs

While Network Access Control Lists and Security groups both exist to control network traffic, their main difference is that ACLs act as a firewall for controlling traffic into and out of subnets, while security groups provide security at the instance level.

5. Internet Gateways

When you launch a VPC, by default, an Internet Gateway (IGW) will be created and attached. As you can probably guess, this serves to connect resources within a VPC to the Internet. Now, since the Internet is where all the bad guys live, make sure you’ve locked all the doors that need locking.

Hint: If you are setting up an instance, configure your security group to allow only the minimum possible amount of incoming traffic – which is probably SSH (port 22) set to allow access only from your own IP. You can open other ports as needed later on.

6. Route Tables

Route tables direct network traffic between instances inside a subnet. If you need resources within different subnets to be able to talk to each other, then you will definitely need to understand route tables.

AWS Direct Connect

You are probably not going to need AWS Direct Connect unless you are planning on building significant infrastructure on AWS. Nevertheless, it is an important AWS networking concept. In a nutshell, AWS Direct Connect links a local network to your AWS resources through a dedicated connection to an AWS Direct Connect physical location (generally, a third party provider) over a standard 1 gigabit or 10 gigabit Ethernet fiber-optic cable.

Amazon Route 53

If you want your users to find you, you’ll need DNS routing. The AWS networking solution to that problem is Route 53, which offers highly available and scalable Domain Name System, domain name registration, and health-checking web services. It provides services, unlike other DNS providers, but with some nice extras like:

  • Health checks and DNS failover. There’s nothing like users successfully finding their way to your web app…only to discover that the server is down. Route53 can make your applications highly available and resilient to failure by keeping a careful watch on their status. If your applications are deployed in multiple availability zones within multiple AWS regions, Route 53 can perform health checks against each endpoint, allowing your clients to invisibly switch between servers without even noticing that there was a problem.
  • Routing Decisions are based on…
    – Health check status
    – WRR (weighted round robin),
    – LBR (latency-based routing)
    – Geolocation routing.
  • Aliasing is another special feature Route 53 that is unique to AWS.

In Conclusion

AWS Networking is not quite the same as “old world” networking, but where it’s different, it’s usually a good thing. Here’s a summary of what we discussed:

VPC (Virtual Private Cloud)

– Different Configurations for your Network
– Subnets

– Regions and Availability Zones
– Security Groups and NACLs
– Internet Gateways 
– Route Tables

AWS Direct Connect
Amazon Route 53

– Health checks and DNS failover
Routing Decision Making
– 
Aliasing

Avatar

Written by

Michael Sheehy

I have been UNIX/Linux System Administrator for the past 15 years and am slowly moving those skills into the AWS Cloud arena. I am passionate about AWS and Cloud Technologies and the exciting future that it promises to bring.

Related Posts

Sam Ghardashem
Sam Ghardashem
— May 15, 2019

Aviatrix Integration of a NextGen Firewall in AWS Transit Gateway

Learn how Aviatrix’s intelligent orchestration and control eliminates unwanted tradeoffs encountered when deploying Palo Alto Networks VM-Series Firewalls with AWS Transit Gateway.Deploying any next generation firewall in a public cloud environment is challenging, not because of the f...

Read more
  • AWS
Joe Nemer
Joe Nemer
— May 3, 2019

AWS Config Best Practices for Compliance

Use AWS Config the Right Way for Successful ComplianceIt’s well-known that AWS Config is a powerful service for monitoring all changes across your resources. As AWS Config has constantly evolved and improved over the years, it has transformed into a true powerhouse for monitoring your...

Read more
  • AWS
  • Compliance
Avatar
Francesca Vigliani
— April 30, 2019

Cloud Academy is Coming to the AWS Summits in Atlanta, London, and Chicago

Cloud Academy is a proud sponsor of the 2019 AWS Summits in Atlanta, London, and Chicago. We hope you plan to attend these free events that bring the cloud computing community together to connect, collaborate, and learn about AWS. These events are all about learning. You can learn how t...

Read more
  • AWS
  • AWS Summits
Paul Hortop
Paul Hortop
— April 2, 2019

How to Monitor Your AWS Infrastructure

The AWS cloud platform has made it easier than ever to be flexible, efficient, and cost-effective. However, monitoring your AWS infrastructure is the key to getting all of these benefits. Realizing these benefits requires that you follow AWS best practices which constantly change as AWS...

Read more
  • AWS
  • Monitoring
Joe Nemer
Joe Nemer
— April 1, 2019

AWS EC2 Instance Types Explained

Amazon Web Services’ resource offerings are constantly changing, and staying on top of their evolution can be a challenge. Elastic Cloud Compute (EC2) instances are one of their core resource offerings, and they form the backbone of most cloud deployments. EC2 instances provide you with...

Read more
  • AWS
  • EC2
Avatar
Nitheesh Poojary
— March 26, 2019

How DNS Works – the Domain Name System (Part One)

Before migrating domains to Amazon's Route53, we should first make sure we properly understand how DNS worksWhile we'll get to AWS's Route53 Domain Name System (DNS) service in the second part of this series, I thought it would be helpful to first make sure that we properly understand...

Read more
  • AWS
Avatar
Stuart Scott
— March 14, 2019

Multiple AWS Account Management using AWS Organizations

As businesses expand their footprint on AWS and utilize more services to build and deploy their applications, it becomes apparent that multiple AWS accounts are required to manage the environment and infrastructure.  A multi-account strategy is beneficial for a number of reasons as ...

Read more
  • AWS
  • Identity Access Management
Avatar
Sanket Dangi
— February 11, 2019

WaitCondition Controls the Pace of AWS CloudFormation Templates

AWS's WaitCondition can be used with CloudFormation templates to ensure required resources are running.As you may already be aware, AWS CloudFormation is used for infrastructure automation by allowing you to write JSON templates to automatically install, configure, and bootstrap your ...

Read more
  • AWS
  • CloudFormation
Badrinath Venkatachari
Badrinath Venkatachari
— February 1, 2019

10 Common AWS Mistakes & How to Avoid Them

Massive migration to the public cloud is changing architecture patterns, operating principles, and governance models. That means new approaches are vital to get a handle on soaring cloud spend. Because the cloud’s short-term billing cycles call for financial discipline, you must empower...

Read more
  • AWS
  • Operations
Avatar
Andrew Larkin
— January 24, 2019

The 9 AWS Certifications: Which is Right for You and Your Team?

As companies increasingly shift workloads to the public cloud, cloud computing has moved from a nice-to-have to a core competency in the enterprise. This shift requires a new set of skills to design, deploy, and manage applications in cloud computing.As the market leader and most ma...

Read more
  • AWS
  • AWS Certifications
Avatar
Andrew Larkin
— January 15, 2019

2018 Was a Big Year for Content at Cloud Academy

As Head of Content at Cloud Academy I work closely with our customers and my domain leads to prioritize quarterly content plans that will achieve the best outcomes for our customers.We started 2018 with two content objectives: To show customer teams how to use Cloud Services to solv...

Read more
  • AWS
  • Azure
  • Cloud Computing
  • Google Cloud Platform
Avatar
Jeremy Cook
— November 29, 2018

Amazon Elastic Inference – GPU Acceleration for Faster Inferencing

“Add GPU acceleration to any Amazon EC2 instance for faster inference at much lower cost (up to 75% savings)”So you’ve just kicked off the training phase of your multilayered deep neural network. The training phase is leveraging Amazon EC2 P3 instances to keep the training time to a...

Read more
  • AWS
  • Elastic Inference
  • re:Invent 2018