Example: A VPC with an PIv4 CIDR block of 10.0.0.0/16 has 65,636 total IP addresses. The VPC has four equal-sized subnets. Only 251 IP addresses are available for use by each subnet.
Provide a target in your VPC route tables for internet traffic
Perform network address translations for intances that were assigned public PIv4 addresses
To make a subnet public, you attach an internet gateway to your VPC and add a route entry to the route table.
Network Address Translation (NAT) gateway enables intances in a private subnet to connect to the public internet and prevent it from initation a connection.
Performance can be negatively affected if your data center is located far away from your AWS region
AWS direct connect
dedicated private connection between your network and one of the direct connect locations
uses open standard 802.1q virtual local area networks
VPC endpoints
A VPC endpoit is a virtual device that enable you to privately connect to Amazon regional services
AWS PrivateLink:
Requires VPC interface endpoint
Private connectivity between 2 VPCs, AWS services and on-premises app
Two types of endpoints:
Gateway endpoints (Amazon S3 and Amazon DynamoDB)
Interface endpoints (powered by AWS PrivateLink)
AWS Transit Gateway
A transit gateway is a network transit hub that you use to interconnect your VPCs and on-premises network.
Section 4: VPC security
Security groups
A security group acts as a virtual firewall that controls inboud and outbound traffic from your instance.
Security groups have rules to manage instance traffic
Default security groups are sealed shut to inbound traffic. we need to define rules.
Security groups are stateful. The outbound traffic is always allowed.
Network access control lists (network ACLs)
Act at a subnet level.
One-to-one relationship with subnet
A network ACL has separate inbound and outbound rules, and each rule can either allow or deny traffic.
Default network ACLs allow all inbound and outbound IPv4 traffic
Network ACLs are stateless
Security groups versus network ACLs
Attribute
Security Groups
Network ACLs
Scope
Instance level
Subnet level
Supported Rules
Allow rules only
Allow and deny rules
State
Stateful (return traffic is automatically allowed, regardless of rules)
Stateless (return traffic must be explicitly allowed by rules)
Order of Rules
All rules are evaluated before decision to allow traffic
Rules are evaluated in number order before decision to allow traffic
Section 5: Amazon Route 53
DNS resolution
It is the process of tranlsating an internal name to the corresponding IP address.
Route 53
Is highly available and scalable Domain Name System (DNS) web service
Is used to route end users to internet applications by transalting names into numeric IP addresses
Is fully compliant with IPv4 and IPv6
Connects user requests to infrastructure running in AWS and also outside of AWS
Is used to check the health of your resources
Features traffic flow
enables you to register domain name
Supported routing
Simple routing
Use in single-server environments
Weighted routing
Assign wights to resource record sets to specify the frequency
Latency routing
Help improve your global app
Geolocation routing
Route traffic based on location of your users
Geoproximity routing
Route traffic based on locations of your resources
Failover routing
Fail over to a backup site if your primary site becomes unreachable
Multivalue answer routing
Respond to DNS queries with up to eight healthy records selected at random
Use case: Multi-region deployement
DNS failover
Improve the availablity of your applications that run on AWS by:
Configuring backup and failover scenarios for your own app
Enabling highly available multi-region architectures on AWS
Creating health check
DNS failover for a multi-tiered web app
Section 6 Amazon CloudFront
Content delivery and network latency
Challenge of network communication: network performance.
Latency can happen depending on the geographical location of the user.
Amazon CloudFront
Fast, global and secure CDN service
Global, network of edge locations and Regional edge caches
Self-service model
Pay-as-you-go pricing
Infrastructure
When a customer makes a demand, CloudFront respond with the IP address of the edge location closest to the customer. CloudFront obtains the data and copies it to the edge location.
Edge locations
Network of data centers that Cloudfronts uses to serve popular content quickly to customer
Regional edge cach
CloudFront location that caches content that is not popular enough to stay at an edge location. It is located between the origin server and the global edge location
When data become stale, it is removed from the cache of the edge location
Wrap-up
Which AWS networking service enables a company to create a virtual network within AWS?