Visualizing AWS with Relationship Graphs
Use relationship graphs to easily navigate your AWS accounts and gain insights to how all your resources are interconnected.
AWS can be a daunting platform for novice cloud users due to its vast array of over 200 different service offerings. With resources spread across 17 commercial regions and multiple accounts, navigating and managing AWS can be even more challenging.
However, with Steampipe relationship graphs, navigating and managing your cloud infrastructure becomes much easier. Not only can you quickly and easily jump from one cloud resource to another without logging in to the AWS console, but you also gain better visibility into your cloud infrastructure, reduce the risk of errors, improve collaboration, and streamline troubleshooting and problem-solving. By providing a clear and intuitive visualization of your cloud resources and how they are connected, Steampipe relationship graphs make it easier for you to make informed decisions and manage your cloud infrastructure with confidence.
Let's take a closer look at some examples of how Steampipe relationship graphs can help you navigate and manage your AWS infrastructure more effectively.
We can start with your VPC. Here we see the four subnets and the availability zones. For example, in the
public_1 subnet, we find an EC2 Instance and its associated network interface. You can also navigate the Security Groups created in this VPC.
We can click on the WordPress Instance to see more details about it. Here we see the WordPress instance has a disk and a network interface. In addition, we can see the instance role and the SSH keys are often a way to see who created a machine.
The IAM Role allows us to see what permissions the WordPress instance has. As you can see, the instance has the
Additionally, we see that both the ec2 and lambda services can assume this role. As this role is for EC2, that is something a DevOps engineer should investigate.
The IAM User Detail dashboard shows the relationship between a user, their access keys, and the attached policies. For example, here is what the Steampipe Cloud IAM user looks like.
Uncover hidden details in your AWS footprint.
These graphs work hand-in-hand with their dashboards' infocards, charts, and tables to help you understand your AWS cloud in a whole new way. Which of these seem most useful to you? What other kinds of relationships will help you understand your cloud environments and manage them more effectively?
We're excited to learn more about your experience using the AWS Insights Mod. Our Slack community is a great place to share your feedback and connect with other AWS users.