# Stack graph

See a CloudFormation stack as a graph of its resources, open any of them, and jump from a resource to its place in the graph.

Open a stack (Services → CloudFormation, or the stack link on any resource that belongs to one) and pick the **Graph** tab. Each box is a resource from the stack’s template, with its type and its status in the stack; a line means one resource refers to the other.

Screenshot: Graph tab of the checkout-service stack with CheckoutApiService in the centre

## Moving around

- Pinch to zoom, drag to move. On a big stack, zoom out for the shape and in for the names.
- **Find a resource** searches by logical ID; **Fit** shows the whole stack again.
- Tap a resource to open it: its screen in the app, its read-only catalogue page, or a link to the AWS console.

## From a resource to the graph

EC2 instances, Lambda functions, ECS services, RDS databases, DynamoDB tables, SQS queues, alarms and log groups that belong to a stack show **CloudFormation stack** with its name on their screen. Tap it to open the graph centred on that resource. On the stack’s **Resources** tab, every row has **Show in graph**.

## What the lines mean

A line joins two resources when the template connects them through `DependsOn`, `Ref`, `Fn::GetAtt` or `${Resource}` inside `Fn::Sub`. Outputs are drawn as small end points. For SAM templates the processed template is used, so you see the resources SAM creates. JSON and YAML templates both work, short-form tags included.

## Permissions

The graph needs `cloudformation:GetTemplate`, and `cloudformation:ListStackResources` for the statuses; both are in the AWS managed `ReadOnlyAccess` policy. If GetTemplate is denied, the Graph tab says so and the stack’s other tabs still work.

## Questions

### Can I change the stack from the graph?

No. The graph is read-only. Open a resource to use its own actions, which go through your guardrails like every other change.

### Why is a resource missing from the graph?

The graph shows what the template declares. Resources a stack creates indirectly, such as the log group Lambda makes for a function, are not in the template, so they are not in the graph.

**Still stuck?**

Email [support@cloudconsole.dev](mailto:support@cloudconsole.dev) with what you tried and any message the app showed. Don’t send access keys or secrets. We reply within two working days.

## Related

- ["What changed?": the changes before an alarm fired](https://cloudconsole.dev/help/what-changed) – Using the app
- [Which AWS services are supported](https://cloudconsole.dev/help/services) – Using the app
- [Recommended read-only permissions](https://cloudconsole.dev/help/recommended-permissions) – Permissions & errors
- [Pin resources and share links](https://cloudconsole.dev/help/pins-and-links) – Using the app

[All help topics →](https://cloudconsole.dev/help/)

---

Source: https://cloudconsole.dev/help/stack-graph

CloudConsole is an independent iPhone and Android app for Amazon Web Services by Cloudconcur Ltd. It is not affiliated with Amazon Web Services.
