6. Architecture Map
The architecture view is a resource mapping group that builds a physical topology of your resources in the multi-account, we enable the user to explorer his architecture from top to bottom,
Including the ability to understand the different connection between the different services
Lets start on top of the page
On the left upper corner you will see the last update time we collect all your meta-data in your accounts in order to keep your architecture up-to-date.
If you want you can press the button on demand and it will take 5-30minutes until we will collect near real time architecture.
You can filter by a specific service in your architecture the result will give you all the occurrence of the specific service you asked for
and if you want to filter by free text things like tags or other things you can search it also in the related filter search box :
You can see all the account that we show in the center by clicking on “included accounts” button :
you can specify your own name for the account by clicking the wheel on the right panel near to the down arrow .
each account have its on color that in the mapping will be show the same color on the border of the object :
Lets take a look on the right corner at the toolbox again :
There is an icon 
The timeline lets you the ability to go back in time and load architecture from the past so that you can track the changes and evaluate what has been changed .
Next to the icon 
I explorer my architecture and got into a situation i want to share/save like the example below:
Clicking on ”Save State” option will save the architecture and will give you the ability to load it when clicking on the Load State Button it will open all the last saved items(it a numbers so the last architecture i have saved will be the biggest number in the list) when i choose one it will open the architecture i have saved , later i can share it with my teammate to go over the specific architecture design :
As you can already see the main page includes all the objects that I have in my architecture.
All the icons are taking from the providers catalog except 2 icons that is
equal to 0.0.0.0/0 and that includes a list of authorized ips outside your CloudProvider.
We already have a the physical hierarchy in your stack as you can see in the picture below:
Let’s look at the ec2 instances that are marked. You can see on the right panel all the details of the specific instance including the cost, tags, and all the meta-data when i will press the “JSON” blue button.
When standing on one of the object and right-click a list-menu options will
appeared:
There is a 3 main edges we create :
- Infrastructure edge – it will show all the infrastructure edge related to the service, at this example you can see “EBS Attachment” clicking on that option will show all the relates ebs volumes the instance have
- Network Edge – here we have an algorithm that calculates all the network policies an object has and the result is the actual network connection you really have.
On the menu-list it will be the “Network Access” and “Public Network Access”
The result will be in the picture below: “red” for ingress Network from the “Public
Network Access”,
“green” for outbound and ingress in the “Network Access”.
