Identifying the resources and VPCs in your AWS account and which AWS regions they are deployed in can be a time consuming process that is often put off when there are more important jobs to be done. 

If you have been working with AWS infrastructure for any length of time, you understand the importance of documenting your AWS VPCs using network topology diagrams. They visually represent the construction of your AWS network, and can also speed up the on-boarding of new team members and external consultants. 

Knowing what regions your infrastructure is deployed in is essential when trying to establish what would happen if there is an outage in one particular AWS region. If us-east-1 drops out, can your application continue to function.

So having a diagram that clearly shows what regions host your VPCs and AWS resources is not a bad idea.

As a cloud professional working with Microsoft Azure, you no doubt appreciate the value of great network topology diagrams. Azure diagrams provide a visual cue for better communication and understanding of your cloud infrastructure at all levels of your organisation, from management down to freshly onboarded engineers and consultants.

If you are building solutions on Microsoft Azure, you'll almost certainly want to know your architecture has been built in line with your design which often leads to the need to create Azure diagrams.

When you have accurate and up to date network topology diagrams on hand it enables you to visually explain your network infrastructure to both your engineering and operations team and also provide management with an easy to understand representation of what you are building and managing. If you are onboarding new engineers, or engaging external consultants, you can bring them up to speed very quickly with a well laid out Azure network topology diagram.

The problem with traditional diagrams has always been the time it takes to create them. If you use manual drag and drop diagram software or drawing packages like Microsoft Visio the process can take forever which is why up to date Azure network topology diagrams are rarely on hand. Engineers rarely have the time or motivation to sit down and create Azure diagrams. They generally have far more important or pressing issues to work on.

This is where you can leverage Hava to help you create Azure diagrams.

If you are taking on a new client or development project, having access to infrastructure documentation is a massive advantage when trying to understand exactly what is running on your network. Come to think of it, with the complex nature of cloud consoles and network configurations you may be surprised at what you have running in your existing infrastructure.

Back in the day our team provided expert cloud consulting services. When we took on a new client, diagramming the new client's infrastructure was always the first job in the process. It was always, without exception, time consuming, laborious but necessary in establishing exactly what was going on in the client's cloud accounts prior to starting work on improving or redesigning the network infrastructure.

If you have been working with AWS VPCs for any length of time, you understand the importance of documenting your AWS VPCs using cloud architecture diagrams. Not only do they visually represent the construction of your AWS network, they also speed up the on-boarding of new team members and external consultants the also help you to quickly identify what the network should look like in the middle of an outage.

When you are working with Azure cloud computing infrastructure in your role as a DevOps engineer, there are many benefits to creating and maintaining accurate Microsoft Azure diagrams.

You can effectively communicate your Azure network design to both technical DevOps staff, developers and also management where necessary.  If you are onboarding new DevOps engineers, or engaging external consultants, you can bring them up to speed very quickly with a well laid out accurate infrastructure diagram.

If you are taking on a new client, application or project, having access to detailed infrastructure documentation is a massive advantage when trying to understand exactly what is running where. Back in our cloud consulting days, diagramming a new client's infrastructure was always the first job in the on-boarding process. It was often time consuming, laborious but necessary in establishing exactly what was going on prior to starting work on improving or redesigning infrastructure.

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

Professional cloud engineers understand the importance of documenting networks using network topology diagrams. Not only do they assist with communicating the construction of your cloud network, they also speed up on boarding new team members, external consultants and quickly identifying what the network should look like in the middle of an outage.

Accurate AWS network diagrams play a vital role in monitoring and internally communicating the operational status and design of well engineered AWS infrastructure, which is why serious AWS development teams use an AWS Diagram Builder.