1. Home
  2. Training Library
  3. Amazon Web Services
  4. Amazon Web Services Courses
  5. Inter-Regional and Intra-Regional Communication Patterns

Summary

Contents

keyboard_tab
Summary
Overview
Difficulty
Intermediate
Duration
19m
Students
15
Ratings
5/5
starstarstarstarstar
Description

In this course, we discuss how our services deployed to AWS communicate with each other. We cover what communication looks like when our services are in the same region and what communication looks like when our services are in different regions.

Learning Objectives

  • Inter-regional communication patterns
  • Intra-regional communication patterns

Intended Audience

  • Anyone working with AWS Networking 
  • Those studying for the AWS Networking Specialty certification
  • Anyone studying for the AWS Solutions Architect certifications
  • Anyone just looking to increase their AWS knowledge

Prerequisites 

  • Before attending this course, you should already be familiar with AWS networking services such as VPCs and VPC peering

 

Transcript

In this course, we've discussed different communication patterns for inter-region and intra-region communication in AWS. We began by discussing communication then was also deployed to a single VPC. We then discussed different options for inter and intra-region communication. For intra-region communication, we can deploy every resource to the same VPC, we can deploy to multiple VPCs and isolate resources or we can deploy to multiple VPCs and use VPC peering to connect the VPCs or deploy multiple VPCs and use transit gateway to connect the VPCs. For inter-region communication, we can deploy multiple VPCs and isolate resources, deploy to multiple VPCs and use VPC peering or deploy to multiple VPCs and use transit gateway. 

When connecting to AWS services or services provision by third parties, we can use public endpoints and access the service through public networks or use VPC endpoints and endpoint services so that we can access services using AWS's private network. VPC peering offers simplicity but does not scale as well as transit gateway. VPC peering is a partial or full mesh and we can use knuckles and security groups to help control the flow of traffic. 

Transit gateway uses a hub and spoke design and we use multiple route tables as well as knuckles and security groups to control the flow of traffic. Although transit gateway is more expensive than VPC peering, the fact that VPCs that use transit gateway can share Internet gateways and share site-to-site VPNs might mean that transit gateway is more cost-effective compared to having multiple VPCs with their own Internet and virtual private gateways. Thank you for your time. Good luck with your continued learning, and I hope to see you on other courses soon. Thank you.

 

About the Author

Mike has worked in IT since 1997, specializing in networking, storage, and architecture. He's been in cloud computing for the last 8 years, working across several cloud platforms but specializing in AWS. He's been involved in many cloud projects over the years covering migrations, hybrid connectivity, security optimization, networking, and storage architecture.

He gained his first training qualification in 1998 and, about 3 years ago, became an AWS Authorized Champion Instructor. He's delivered AWS cloud courses across Europe for a range of clients, with a focus on Architecture, Security, and Networking. He currently holds certifications for the four biggest cloud vendors, including the AWS Solutions Architect Professional, AWS DevOps Engineer, and AWS Advanced Networking specialty certifications.

He lives in the North of England with his wife Frances and their dog Inca.