When you are managing multiple cloud based networks the chances are there are multiple cloud accounts to look after and these may well be from different vendors.

Following on from our post on the AWS Cloud Practitioner Essentials Compute topic, in this post we’ll look at module 3 which concerns itself with the global infrastructure AWS has in place to deliver cloud services and the reliability built in using the various regions and availability zones to provide both redundancy and lower latency.

When you are building cloud based infrastructure or are handed a new account or existing project to manage, the very first thing you are likely to ask yourself is what does the infrastructure look like? What resources are running? Where are they running? What does the security look like?

Could your team show you with any confidence what systems and resources you have running in the cloud. Could they do that today, or right now.

If you are building or supporting cloud infrastructure built on AWS, GCP or Azure it is now extremely simple to get a live graphical snapshot of your cloud network topology.

A VPC peering connection is a networking connection between two VPCs that enables you to route traffic between the two VPCs using private IPv4 or IPv6 addresses. Instances in either VPC can communicate with each other as if they are within the same network. You can create a VPC peering connection between your own VPCs, or with a VPC in another AWS account. The VPCs can be in different AWS regions which is also known as an inter-region VPC peering connection.

One of the more advanced features of the Hava business plan is the ability to create teams.

Amazon Route 53 is a scalable and highly available DNS service that translates human readable website names like www.hava.io into the numeric IP address location of the target website host (13.35.145.107) or a private VPC or application endpoint.

The AWS Command Line Interface (CLI) is a downloadable tool that you can use to manage your AWS services.