6. Architecture Map

< All Topics

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 connections between the different services  

our Network Analyzer feature helps you understand what breach you may have in your network mesh.

Let’s start on top of the page.

You will see the last update time we collect all your meta-data in your accounts to keep your architecture up-to-date on the left upper corner.

If you want, you can press the button on demand, and it will take 5-10 minutes until we collect near real-time architecture.

You can filter by a specific service in your architecture the result will give you all the occurrences 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 accounts that we show in the center by clicking on the “included accounts” button :

each account has its own color that in the mapping will be shown the same color on the border of the object.

The timeline lets you go back in time and load architecture from the past so that you can track the changes and evaluate what has been changed.

There is an icon that when you click on him, a TimeLine will be opened :

Now let’s say I have explored my architecture and got into a situation I want to share/save my view.  

Clicking on the” Save State” option will save the architecture and allow you to load it when clicking on the Load State Button. It will open all the last saved items (it a number 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 I have in my architecture.

All the icons are taken from the provider’s catalog except 2 icons equal to 0.0.0.0/0 and include a list of authorized IPs outside your CloudProvider.

We already have a 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 objects and right-click, list-menu options will have appeared. 

There are 3 main edges we create :

  1. Infrastructure edge – it will show all the infrastructure edges related to the service. At this example, you can see  “EBS Attachment” clicking on that option will show all the related EBS volumes the instance have
  2. 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.

The menu list 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.”

Previous 5. Cost Control
Next 7. Admin Area
Table of Contents

Join our weekly demo

Once a week our CEO, Chen Goldberg is giving a group demo. 

In this demo he’s showing how to gain maximum cloud security and compliance using CloudWize platform. 

We use cookies and tracking technologies to improve your experience on our website and for analytics purposes. By using and accessing this site, you agree to our Terms of Use and Privacy Policy