When you are building applications and networks on AWS, there are many compelling reasons why you would want to accurately diagram and document your AWS infrastructure. Knowing exactly what is running based on the actual resources configured in your AWS environments is probably the number one reason to use an automated AWS infrastructure diagram generator over manually drawing diagrams yourself using a drag and drop process.

How does standardised documentation assist with infrastructure visibility and understanding?

AWS cloud architecture can get complex fast. Once you rotate through a few engineers or external consultants how confident are you that someone within your organisation knows exactly what you have running in your cloud accounts and are those resources actually being used.

Having up to date diagrams can be invaluable when you want to know how your networks hang together or need to explain to stakeholders what you have running and why.

The problem with creating and maintaining network diagrams manually is finding the time to do it in the first place, which is never anyone's priority and then finding the time to update the diagrams when things change (which they invariably do) 

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?

When you are building cloud based applications and networks on AWS, there are many compelling reasons why you would want to accurately diagram and document your AWS infrastructure. Knowing exactly what is running based on the actual resources configured in your AWS environments is probably the number one reason to use an automated AWS infrastructure diagram generator over manually drawing diagrams yourself using a drag and drop process.