VPC Security and Control
VPC Sharing using the AWS Resource Access Manager
AWS Networking Basics
Introduction to AWS PrivateLink
Using AWS Network Firewalls to Secure Your VPCs
Inter-Regional and Intra-Regional Communication Patterns
The course is part of this learning path
In this section of the AWS Certified Advanced Networking - Specialty learning path, we introduce you to the various networking and VPC services currently available in AWS that are relevant to the ANS-C01 exam.
- Identify and describe the various networking services available in AWS
- Describe how to configure an Amazon Virtual Private Cloud (VPC)
- Understand how to control network traffic via Security Groups and Network Access Control Lists (NACLs)
- Describe options for VPC connectivity, subnets, and routing
- Understand how to share VPC resources using the AWS Resource Access Manager (RAM)
- Identify how to evaluate the configuration of VPC resources using the VPC Reachability Analyzer
The AWS Certified Advanced Networking - Specialty certification has been designed for anyone with experience designing, implementing, and operating complex AWS and hybrid networking architectures. Ideally, you’ll also have some exposure to the nuances of AWS networking, particularly regarding the integration of AWS services and AWS security best practices. Many exam questions will require advanced level knowledge of many AWS services, including AWS networking services. The AWS Cloud concepts introduced in this course will be explained and reinforced from the ground up.
The high-level architecture for a typical AWS PrivateLink environment is shown here. On the service providers side, the following steps are taken to create a PrivateLink endpoint service. One, deploy the AWS resources required to support the workload or service that the organization will provide to its customers. Two, PrivateLink services are made available through either a network or a gateway load balancer, thus the provider must create an NLB or GWLB to front-end those services. Three, with the load balancer validated and tested, a PrivateLink service endpoint is created and access is provided to one or many AWS principles. On the service consumer side, a VPC endpoint is created to connect to the service provider. When creating a PrivateLink service endpoint, a service provider has the option to enable or disable the required acceptance for endpoint and enable private DNS name settings.
Let's take a moment to consider the functionality they provide. To control which AWS principles have access to their PrivateLink service endpoints, service providers have the ability to use a combination of permissions and acceptance settings. The service provider assigns permissions to access a PrivateLink service endpoint to an AWS account, ad IAM user, or IAM roles. Beyond permissions, a service provider must also accept or reject the connection request. If the acceptance required option is enabled as shown on the image, the endpoint service is not accessible to a given service consumer until the service provider manually accepts the consumer's endpoint connection request, even if the consumer has the appropriate access permissions. If acceptance required is unchecked, consumer endpoint connection requests are automatically accepted and access to the PrivateLink endpoint service is given to those AWS principles with the appropriate access permissions.
Enabling a private DNS name allows service consumers to connect to the PrivateLink service using a custom and typically friendlier FQDN, such as SaaS service.domain.com. A route 53 private hosted zone is not required to support this functionality. To support a private DNS name, the service provider simply specifies its preferred FQDN when creating the PrivateLink service endpoint. To use the private DNS names specified by the provider, the service consumer enables the private DNS name option when building their service connection.
Stuart has been working within the IT industry for two decades covering a huge range of topic areas and technologies, from data center and network infrastructure design, to cloud architecture and implementation.
To date, Stuart has created 150+ courses relating to Cloud reaching over 180,000 students, mostly within the AWS category and with a heavy focus on security and compliance.
Stuart is a member of the AWS Community Builders Program for his contributions towards AWS.
He is AWS certified and accredited in addition to being a published author covering topics across the AWS landscape.
In January 2016 Stuart was awarded ‘Expert of the Year Award 2015’ from Experts Exchange for his knowledge share within cloud services to the community.
Stuart enjoys writing about cloud technologies and you will find many of his articles within our blog pages.