Introducing Resource Access Manager (RAM)
Start course
3h 55m

This section of the AWS Certified Solutions Architect - Professional learning path introduces you to the core networking concepts and services relevant to the SAP-C02 exam. We start with an introduction to the AWS Virtual Private Network (VPC) and networking services. We then understand the options available and learn how to select and apply AWS networking, DNS, and content delivery services to meet specific design scenarios relevant to the AWS Certified Solutions Architect - Professional exam. 

Want more? Try a Lab Playground or do a Lab Challenge

Learning Objectives

  • Get a foundational understanding of VPCs, their security, and connectivity
  • Learn about VPC sharing using the AWS Resource Access Manager
  • Discover inter-regional and intra-regional communication patterns in AWS
  • Learn about AWS Direct Connect, along with its implementation, configuration, and connectivity options
  • Understand routing in AWS, including static and dynamic routing
  • Understand the basics of networking, including Elastic IP addresses, Elastic Network Interfaces, networking with EC2, VPC endpoints, and AWS Global Accelerator
  • Learn about the DNS and content delivery services Amazon Route 53 and Amazon CloudFront

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.


About the Author
Learning Paths

Danny has over 20 years of IT experience as a software developer, cloud engineer, and technical trainer. After attending a conference on cloud computing in 2009, he knew he wanted to build his career around what was still a very new, emerging technology at the time — and share this transformational knowledge with others. He has spoken to IT professional audiences at local, regional, and national user groups and conferences. He has delivered in-person classroom and virtual training, interactive webinars, and authored video training courses covering many different technologies, including Amazon Web Services. He currently has six active AWS certifications, including certifications at the Professional and Specialty level.