VPC Security and Control
VPC Sharing using the AWS Resource Access Manager
AWS Networking Basics
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.
In this section, we will discuss the role Resource Access Manager plays in sharing of centralized resources. In order to use VPC sharing, you must work with AWS Resource Access Manager, RAM. RAM allows you to share a whole host of AWS resources from centralized AWS accounts. Using RAM, you can share resources such as Aurora DB Clusters, Dedicated Hosts, Resource Groups, and of course VPC Subnets. The first thing you should do if you want to easily use RAM is to enable sharing. This can be done through the Resource Access Manager console or through the AWS CLI. Next, using the console or CLI you create a resource share.
When you create a resource share, you provide a name for the share and the list of resources you wish to share. Here, we can see that we are creating a share called DevTeam1 and we're sharing three subnets from the same VPC. Next, we can assign permissions to the share. The permissions allow us to restrict the actions that principles are allowed to perform on the share. If you're happy with the permissions, you can click 'Next' and identify the principles you wish to share the resources with. If you select OU, then the resources you are sharing will be shared with all AWS accounts in the organizational units and any new AWS accounts that are added to the OU in the future. We would then complete the wizard and very quickly the shared resources, in this case three shared subnets, would appear in the VPC console of the chosen AWS accounts.
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.