In this post we are going to share a few tips on how to improve the layout of the AWS Diagrams that you generate with Cloudockit:
Specify a Name tag (used in the output Diagrams)
When you navigate in the AWS Management console, most of the time you see that resources are identified by long unique identifier that are quite difficult to read.
That’s the reason why a very common practice in AWS is to create a Tag that contains a short name that you understand and that is readable.
Cloudockit allows you to specify what this tag is so that Cloudockit retrieves readable names and use them bellow shapes in the Diagram.
To specify the tag, you need to go in the Content Tab and scroll at the bottom of the screen:
Please note that if you are not sure about the tag, you can click on retrieve the list of all tags.
Specify an Application tag (used in the output Diagrams)
The same way AWS people create a tag that contains the name, they also typically create a tag that contains the name of the business application that uses the resource tagged.
From the content tab, you can specify this tag:
When this tag is specified, you will get a list of applications in the word document and also, you will get a Visio Diagrams named ByApplications that will contain a tab per Application with all the components of this application.
Please ensure that you have selected the Visio Diagram by applications also:
Re-Layout the generated Visio Diagram
Once you have opened the generated Visio Diagram, you can use the Auto-Layout feature of Visio. This will help if you have many overlapping arrows that make the diagram difficult to read:
Choose the output of the Diagrams that gets generated.
From the beginning of Cloudockit until now, the only output format supported was Visio. From now on, we are committed to support multiple output formats like Draw.io and Lucidchart.
Note : At the time of writing of this blog post, Draw.io is only accessible in our beta environment