• The AWS Systems Manager CloudWatch Dashboard will no longer be available after April 30, 2026. Customers can continue to use Amazon CloudWatch console to view, create, and manage their Amazon CloudWatch dashboards, just as they do today. For more information, see [Amazon CloudWatch Dashboard documentation](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch_Dashboards.html).
# Exploring nodes
Exploring nodes
You can use the **Explore nodes** page in Systems Manager to review details of managed nodes in your organization or account according to the criteria you specify in filters. You can also use Systems Manager integration with Amazon Q Developer (Amazon Q), an AWS generative AI solution, to search using text prompts.
**Before you begin**
In order to use the **Explore nodes** feature, you must first onboard your organization or account to the unified Systems Manager console. For more information, see [Setting up Systems Manager unified console for an organization](systems-manager-setting-up-organizations.md).
After onboarding, open the [Systems Manager console](https://console.aws.amazon.com/systems-manager/) and choose **Explore nodes**.
**Note**
If you've created an aggregator index for Resource Explorer in a Region different than your home Region, Systems Manager demotes the current index. Then, Systems Manager promotes the local index in your home Region as the new aggregator index. During this time, only nodes for your home Region are displayed. This process can take up to 24 hours to complete.
**Topics**
+ [
# Exploring nodes using console filters
](view-aggregated-node-details-console.md)
+ [
# Exploring nodes using text prompts in Amazon Q
](view-aggregated-node-details-Q.md)
+ [
# Viewing individual node details and taking action on a node
](node-detail-actions.md)
+ [
# Downloading or exporting a managed node report
](explore-nodes-download-report.md)
+ [
# Managing node report content and appearance
](explore-nodes-manage-report-display.md)
# Exploring nodes using console filters
In the Systems Manager console, you can then group your managed nodes according to the following views:
------
#### [ All nodes (No filter) ]
Lists all managed nodes in your organization or account.
![\[A list of managed nodes in the Explore nodes page\]](http://docs.aws.amazon.com/systems-manager/latest/userguide/images/2-explore-nodes-managed-nodes.png)
------
#### [ Node types ]
Provides tabs for viewing data separately for Amazon Elastic Compute Cloud (Amazon EC2) instances and other machine types, including servers on your own premises (on-premises servers), AWS IoT Greengrass core devices, AWS IoT and non-AWS edge devices, and virtual machines (VMs), including VMs in other cloud environments.
![\[Lists of managed nodes on node type tabs\]](http://docs.aws.amazon.com/systems-manager/latest/userguide/images/2-explore-nodes-node-types.png)
------
#### [ Operating systems ]
Provides a tab for each operating system type in your organization or account, such as **Amazon Linux** and **Microsoft Windows Server 2022 Datacenter**. On each tab, you can further filter the list by selecting only specific versions of the operating systems, such as *Amazon Linux 2* and *Amazon Linux 2023*.
![\[Lists of managed nodes on OS tabs\]](http://docs.aws.amazon.com/systems-manager/latest/userguide/images/2-explore-nodes-operating-system.png)
------
#### [ SSM Agent versions ]
Provides a tab for each version of SSM Agent installed on managed nodes in your fleet. On each tab, you can further filter the list by selecting only specific operating systems, such as **Amazon Linux** and **Microsoft Windows Server 2022 Datacenter**.
![\[Lists of managed nodes on agent tabs\]](http://docs.aws.amazon.com/systems-manager/latest/userguide/images/2-explore-nodes-agent-versions.png)
------
In addition, for each of these views, you can further refine the list of nodes reported by choosing to view only nodes for a certain property, such as node status, AWS account ID, organization unit ID, and more.
You can customize the report display by choosing which of the available data columns are displayed in the **Explore nodes** page. You can also download reports in `CSV` or `JSON` formats, or export reports to Amazon S3 in `CSV` format.
**Topics**
+ [
# Choosing a filter view for managed node summaries
](explore-nodes-filter-view.md)
# Choosing a filter view for managed node summaries
The **Explore nodes** page in Systems Manager lets you view aggregated data about your fleet according to a number of available filter views.
**To choose a filter view for managed node summaries**
1. Open the AWS Systems Manager console at [https://console.aws.amazon.com/systems-manager/](https://console.aws.amazon.com/systems-manager/).
1. In the navigation pane, choose **Explore nodes**.
1. For **Filter view**, select one of the filter options and optionally further refine the report:
+ **Managed nodes** – In the search (![\[The search icon\]](http://docs.aws.amazon.com/systems-manager/latest/userguide/images/search-icon.png)) box, you can select a property and delimiter, such as `Node type = Managed EC2 instances`.
+ **Operating systems** – In the **Filter Operating system versions** list, you can select an OS version number. In the search (![\[The search icon\]](http://docs.aws.amazon.com/systems-manager/latest/userguide/images/search-icon.png)) box, you can select a property and delimiter, such as `Node type = Managed EC2 instances`.
+ **SSM Agent versions** – In the **Filter Operating systems** list, you can select an OS name. In the search (![\[The search icon\]](http://docs.aws.amazon.com/systems-manager/latest/userguide/images/search-icon.png)) box, you can select a property and delimiter, such as `Node type = Managed EC2 instances`.
+ **Node types** – In the **Filter Operating systems** list, you can select an OS name. In the search (![\[The search icon\]](http://docs.aws.amazon.com/systems-manager/latest/userguide/images/search-icon.png)) box, you can select a property and delimiter, such as `Node type = Managed EC2 instances`.
After optionally filtering the list, you can view details about a specific managed node by choosing its ID in the **Node ID** column. From that detailed view, you can perform a number of actions on the node.
# Exploring nodes using text prompts in Amazon Q
Using Systems Manager integration with Amazon Q Developer, you can use text prompts to view information created by generative AI about your managed nodes.
Amazon Q Developer is a generative AI-powered conversational assistant that can help you to understand, build, extend, and operate AWS applications. To accelerate your building on AWS, the model that powers Amazon Q is augmented with high-quality AWS content to produce more complete, actionable, and referenced answers. For more information, see [What is Amazon Q Developer?](https://docs.aws.amazon.com/amazonq/latest/aws-builder-use-ug/what-is.html) in the *Amazon Q Developer User Guide*.
The integration between Systems Manager and Amazon Q lets you quickly get visibility and control over large, distributed environments across multiple AWS accounts and Regions. You can use natural language querying to quickly search node data, and then identify issues and take action faster.
When you ask a natural language question about managed nodes or managed instances, Amazon Q uses the Systems Manager `ListNodes` action and creates filters based on your textual input to retrieve results.
For example, say that you give Amazon Q the following prompt:
**List my managed nodes running Red Hat Enterprise Linux 9.2**
Amazon Q determines what filters to include in a request, and then runs a query similar to the following:
```
aws ssm list-nodes \
--filters Key=PlatformName,Values='Red Hat Enterprise Linux',Type=Equal Key=PlatformVersion,Values=9.2,Type=Equal
```
Amazon Q then generates a report about Red Hat Enterprise Linux instances in your account, listing information such as the number of instances, their IDs, and their Regions.
You can also view a JSON summary of each instance's details, as well open a link to view the entire lists of EC2 instances or managed nodes in the Systems Manager **Explore nodes** page. The **Explore nodes** displays results that match the filter criteria you included in your prompt. From there, you can change or refine the filters for your request, as described in [Exploring nodes](view-aggregated-node-details.md).
**Topics**
+ [
# Learning to craft effective prompts to ask Amazon Q about your fleet
](view-aggregated-node-details-Q-prompts.md)
+ [
# Exploring managed nodes using Amazon Q
](explore-managed-nodes-using-Q.md)
# Learning to craft effective prompts to ask Amazon Q about your fleet
The better quality of the question, or the prompt, that you give to Amazon Q, the better the result it provides you with.
**Tips for query prompts**
Keep in mind the following tips when querying Amazon Q about your fleet:
1. To help improve the accuracy of your results, use the terms "managed nodes" and "managed instances" in your prompts instead of just "nodes" and "instances".
1. To query for results across multiple accounts that are part of an *organization*, as configured in AWS Organizations, you must be logged into the delegated administrator account in the designated home Region.
1. In the delegated administrator account, use terms to help Amazon Q understand that you are asking about nodes and instances across the organization by specifically using terms such as "in my organization" or "in my account 123456789012".
**Topics**
+ [
## Sample questions for Amazon Q
](#sample-questions-Q)
+ [
## Supported operating system names and versions for prompts
](#supported-os-names-Q)
## Sample questions for Amazon Q
In the following table, we provide sample questions demonstrate some ways you can create queries of Amazon Q that lead to better results.
We also provide examples of the filters Amazon Q will apply when running the [ListNodes](https://docs.aws.amazon.com/systems-manager/latest/APIReference/API_ListNodes.html) command, which are generated from the content of your prompt.
| Sample natural language question | Amazon Q applied filters |
| --- | --- |
| Show me my Windows managed nodes. | PlatformType = Windows
|
| List my managed instances in account 123456789012. | AccountId = 123456789012
|
| Show me all managed nodes running Amazon Linux 2 across my organization. | PlatformName = Amazon Linux
PlatformVersion = 2
|
| Show me all managed instances running Microsoft Windows Server 2019 Datacenter in my organization. | PlatformName = Microsoft Windows Server 2019 Datacenter
|
| Can you show me all managed nodes with SSM Agent version 3.3.1142.0? | AgentType = amazon-ssm-agent
AgentVersion = 3.3.1142.0
|
| List all Amazon Linux 2 managed instances in account 123456789012 that have SSM Agent version 3.3.1230.0. | PlatformName = Amazon Linux
PlatformVersion = 2
AccountId = 123456789012
AgentType = amazon-ssm-agent
AgentVersion = 3.3.1230.0
|
| What Microsoft Windows Server 2012 R2 Enterprise managed nodes are running in the eu-central-1 region across my entire organization? | PlatformName = Microsoft Windows Server 2012 R2 Enterprise
Region = eu-central-1
|
| Show me all managed instances running Red Hat Linux 7 in ou-d6ty-gxdma6vm. | PlatformName = RHEL Linux
PlatformVersion = 7
OrganizationalUnitId = ou-d6ty-gxdma6vm
|
| What Ubuntu managed instances are in account 123456789012? | PlatformName = Ubuntu
AccountId = 123456789012
|
| List my Linux managed instances. | PlatformType = Linux
|
| Find my macOS managed nodes. | PlatformType = macOS
|
| Show me all versions of Amazon Linux managed nodes in my org. | PlatformName = Amazon Linux
|
| List managed nodes running Amazon Linux 2. | PlatformName = Amazon Linux
PlatformVersion = 2
|
| List the managed nodes with Ubuntu 16.04 in account 123456789012. | PlatformName = Ubuntu
PlatformVersion = 16.04
AccountId = 123456789012
|
| Find all managed nodes that have an SSM Agent version that is not 3.3.987.0. | AgentType = amazon-ssm-agent
AgentVersion != 3.3.987.0
|
| List all managed instances that are not running a Linux operating system. | PlatformType != Linux
|
## Supported operating system names and versions for prompts
When you are asking Amazon Q about the managed nodes in your account, it's helpful to provide the name of an operating system as its labeled in Systems Manager. You can also provide version numbers to further narrow down your results. For example, as represented in the following tables, you could ask for results specifically about **macOS 14.5**, **Microsoft Windows Server 2019 Datacenter**, and **AlmaLinux 9.2 through 9.4**, to name just a few examples.
These lists might not be exhaustive and are offered as examples only.
**macOS**
| Platform name | Version numbers |
| --- | --- |
| macOS | 13.2, 13.4, 13.7, 14.1, 14.5, 14.6.1, 15.0 |
**Windows**
| Releases | Version numbers |
| --- | --- |
| Microsoft Windows Server 2012 R2 Datacenter | 6.3.9600 |
| Microsoft Windows Server 2012 R2 Standard | 6.3.9600 |
| Microsoft Windows Server 2012 Standard | 6.2.9200 |
| Microsoft Windows Server 2016 Datacenter | N/A |
| Microsoft Windows Server 2016 Standard | 10.0.14393 |
| Microsoft Windows Server 2019 Datacenter | N/A |
| Microsoft Windows Server 2019 Standard | N/A |
| Microsoft Windows Server 2022 Datacenter | N/A |
| Microsoft Windows Server 2022 Standard | 10.0.20348 |
**Linux**
| Platform names | Version numbers |
| --- | --- |
| AlmaLinux | 8.10, 9.2, 9.3, 9.4 |
| Amazon Linux 2 | 2.0 and greater |
| Amazon Linux 2023 | 2023.0.20230315.0 and greater |
| BottleRocket | 1.14.3, 1.16.1, 1.18.0, 1.19.1, 1.19.2, 1.19.5, 1.20.0, 1.20.1, 1.20.2, 1.20.3, 1.20.5, 1.21.1, 1.23.0, 1.24.0, 1.24.1, 1.25.0, 1.26.1, |
| CentOS Stream | 9 |
| Debian GNU/Linux | 11-12 |
| Oracle Linux Server | 7.8, 8.2, 8.3, 8.8, 8.9, 8.10, 9.4 |
| Red Hat Enterprise Linux | 8.2, 8.3, 8.4, 8.5, 8.6, 8.7, 8.8, 8.9, 8.10, 9.2, 9.3, 9.4 |
| Red Hat Enterprise Linux Server | 17.3, 7.6, 7.7, 7.8,7.9 |
| Rocky Linux | 8.6, 8.7, 8.8, 8.9, 8.10, 9.1, 9.2, 9.3, 9.4 |
| Ubuntu Server | 16.04, 18.04, 20.04, 22.04, 24.04 |
# Exploring managed nodes using Amazon Q
Systems Manager integration with Amazon Q Developer lets you ask questions about managed nodes in your fleet from anywhere in the AWS Management Console where the Amazon Q interface is available.
For more information about interacting with Amazon Q, see [Chatting with Amazon Q Developer about AWS](https://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/chat-with-q.html) in the *Amazon Q Developer User Guide*.
**To explore managed nodes using Amazon Q**
1. From anywhere in the AWS Management Console, choose the Amazon Q icon (![\[The Amazon Q icon\]](http://docs.aws.amazon.com/systems-manager/latest/userguide/images/q-icon-white.png)).
1. In the prompt field at the bottom of the Amazon Q pane, ask a question about managed nodes in your account or organization.
**Tip**
For tips on creating effective prompts, review the information in [Learning to craft effective prompts to ask Amazon Q about your fleet](view-aggregated-node-details-Q-prompts.md) .
1. Examine information about specific nodes, or choose **Open AWS Systems Manager console** to continue exploring.
# Viewing individual node details and taking action on a node
From a list in the **Explore nodes** page in Systems Manager, you can select an individual node in order to view comprehensive details about the machine or perform a variety of actions on the node. The **General** page in the detail page presents comprehensive information about the node.
**To view individual node details and take action on a node**
1. Open the AWS Systems Manager console at [https://console.aws.amazon.com/systems-manager/](https://console.aws.amazon.com/systems-manager/).
1. In the navigation pane, choose **Explore nodes**.
1. (Optional) Follow the steps in [Choosing a filter view for managed node summaries](explore-nodes-filter-view.md) to refine the list of managed nodes displayed for your organization or account.
1. In the **Node ID** column, choose the linked ID of a node.
1. To view more details about the node, in the left navigation, in the **Properties** list, choose a property to view more information about:
+ **Tags** – View a list of tags applied to the node. You can also add or remove tags.
+ **Inventory** – Choose an inventory type, such as **AWS:Application** or **AWS:Network**, to view inventory details for the node.
+ **Associations** – View details about all State Manager associations applied to the node, including details such as status and associated SSM document name.
+ **Patches** – View summary information about patches and patch status for the node.
+ **Configuration compliance** – View compliance details for the node, such as compliance status and compliance issue severity.
For more information about details on the tabs, see [What is the unified console?](systems-manager-unified-console.md).
1. To take actions on the node, use the following options in the **Node actions** menu:
**Note**
These actions are available only for managed nodes in the AWS account and Region you are currently working in. For managed nodes you might have access to in other accounts or Regions, you can instead access a **Properties** list.
+ **Connect, Start terminal session** – Connect to the node using [AWS Systems Manager Session Manager](session-manager.md).
+ **Tools**
+ **View file system** – Browse the contents of the node's directory structure. Add, rename, and remove directories. Cut or copy and paste files.
+ **View performance counters** – View performance information about the node such as CPU utilization, network traffic, and other utilization types.
+ **Managed processes** – View information about resource usage on the node. Start or stop processes on the node.
+ **Manage users and groups** – View, add, or delete user accounts and user groups on the node.
+ **Execute run command** – Use [AWS Systems Manager Run Command](run-command.md) to manage the configuration of the node. Run Command uses [Systems Manager documents](documents.md) to perform on-demand changes such as updating applications or running Linux shell scripts and Windows PowerShell commands.
+ **Patch nodes** – Use the **Patch now** feature in [AWS Systems Manager Patch Manager](patch-manager.md) to run an on-demand patching operation on the node from the console.
**Note**
The preceding tasks can also be initiated from the **Tools** menu in the left navigation.
+ **Node settings**
+ **Add tags** – Apply additional tag key-value pairs to the node.
+ **Reset node user password** – Set a new password for a specified user on the node.
+ **Modify IAM role** – Change the IAM role that's associated with the node. Create a new IAM role to attach to the node.
# Downloading or exporting a managed node report
You can use the Systems Manager **Explore nodes** feature to view filtered or unfiltered lists of managed nodes for your AWS organization or account in the Systems Manager console. For cases where you want to view the data offline or process it in another application, you can save the report as a `CSV` or `JSON` file.
Depending on the size of the report, you're prompted to download the report to your local machine or export it to an Amazon S3 bucket. Reports are saved to S3 buckets in `CSV` format only.
**To download or export a managed node report**
1. Open the AWS Systems Manager console at [https://console.aws.amazon.com/systems-manager/](https://console.aws.amazon.com/systems-manager/).
1. In the navigation pane, choose **Explore nodes**.
1. (Optional) Follow the steps in [Choosing a filter view for managed node summaries](explore-nodes-filter-view.md) to refine the list of managed nodes displayed for your organization or account.
1. Choose **Report** (![\[The download report icon\]](http://docs.aws.amazon.com/systems-manager/latest/userguide/images/download-arrow-icon.png)).
1. If the **Download report** dialog box is displayed, do the following:
1. For **File name**, enter a name for the file. We recommend specifying a name that represents the scope of the report, such as `all-organization-nodes` or `ec2-instances-out-of-date-agent`.
1. For **Included columns**, specify whether to include columns for all available node details, or only those you've selected for your current display.
**Tip**
For information about managing the columns in your report display, see [Managing node report content and appearance](explore-nodes-manage-report-display.md).
1. For **File format**, select **CSV** or **JSON**, depending on how you will use the file.
1. For **Spreadsheet heading**, to include a column headings row in a `CSV` file, select **Include row of column names**.
1. Choose **Download**.
The report is saved to the default download location according to your browser's settings.
1. If the **Export to Amazon S3** dialog box is displayed, do the following:
1. For **S3 URI**, enter the URI for the bucket to export the report to.
**Tip**
To view a list of your buckets in the Amazon S3 console, choose **View**. To select from a list of buckets in your account, choose **Browse S3**.
1. For **Authorization method**, specify the service role to use to provide permissions for exporting the report to the bucket.
If you choose to let Systems Manager create the role for you, it provides all needed permissions and trust statements for the operation.
If you want to use or create your own role, the role must include the required permissions and trust statements. For information about creating this role, see [Creating a custom service role to export diagnosis reports to S3](create-s3-export-role.md).
1. Choose **Submit**.
# Creating a custom service role to export diagnosis reports to S3
When you are viewing filtered or unfiltered lists of managed nodes for your AWS organization or account in the Systems Manager **Explore nodes** page, you can export the list as a report to an Amazon S3 bucket as a `CSV` file.
To do so, you must specify a service role with the necessary permissions and trust policy for the operation. You can choose for Systems Manager to create the role for you during the process of downloading the report. Optionally, you can create the role and its required policy yourself.
**To create a custom service role to export diagnosis reports to S3**
1. Follow the steps in [Creating policies using the JSON editor](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_create-console.html#access_policies_create-json-editor) in the *IAM User Guide*.
+ Use the following for the policy content, making sure to replace the *placeholder values* with your own information.
------
#### [ JSON ]
****
```
{
"Version":"2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"s3:GetObject",
"s3:PutObject"
],
"Resource": "arn:aws:s3:::amzn-s3-demo-bucket/*",
"Condition": {
"StringEquals": {
"aws:ResourceAccount": "111122223333"
}
}
},
{
"Effect": "Allow",
"Action": [
"s3:GetBucketAcl",
"s3:ListBucket",
"s3:PutLifecycleConfiguration",
"s3:GetLifecycleConfiguration"
],
"Resource": "arn:aws:s3:::amzn-s3-demo-bucket",
"Condition": {
"StringEquals": {
"aws:ResourceAccount": "111122223333"
}
}
},
{
"Effect": "Allow",
"Action": [
"ssm:ListNodes"
],
"Resource": "*"
}
]
}
```
------
+ Give the policy a name to help you recognize it easily in the next step.
1. Follow the steps in [Creating an IAM role using a custom trust policy (console)](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-custom.html) in the *IAM User Guide*.
+ For step 4, enter the following trust policy, making sure to replace the *placeholder values* with your own information.
------
#### [ JSON ]
****
```
{
"Version":"2012-10-17",
"Statement": [
{
"Sid": "SSMAssumeRole",
"Effect": "Allow",
"Principal": {
"Service": "ssm.amazonaws.com"
},
"Action": "sts:AssumeRole",
"Condition": {
"StringEquals": {
"aws:SourceAccount": "111122223333"
}
}
}
]
}
```
------
1. For step 10, choose **Step 2: Add permissions** and select the name of the policy you created in the previous step.
After you create the role, you can select it when following the steps in [Downloading or exporting a managed node report](explore-nodes-download-report.md).
# Managing node report content and appearance
You can use the Systems Manager **Explore nodes** feature to view filtered or unfiltered lists of managed nodes for your AWS organization or account in the Systems Manager console. You can choose from over a dozen fields to include in your lists of nodes, such as **Node ID**, **Operating system name**, **Region**, and more. You can also reorder the columns for your lists and reports and change how the list is displayed in the console.
**To manage node report content and appearance**
1. Open the AWS Systems Manager console at [https://console.aws.amazon.com/systems-manager/](https://console.aws.amazon.com/systems-manager/).
1. In the navigation pane, choose **Explore nodes**.
1. In the **Nodes** area, choose the preferences gear icon (![\[The preferences gear icon\]](http://docs.aws.amazon.com/systems-manager/latest/userguide/images/preferences-icon.png)).
1. In the **Preferences** dialog box, do the following:
1. For **Page size**, choose how many rows are included in each console view display, **10**, **25**, or **50**.
1. For **Wrap lines**, select the box to display all content of a cell in the available column width.
1. For **Striped rows**, select the box to display alternating rows of clear and shaded backgrounds.
1. For **Select visible content**, do the following:
+ Turn on or off individual columns for your list display and reports.
+ To change the order of columns, click and hold the drag handle (![\[The drag handle\]](http://docs.aws.amazon.com/systems-manager/latest/userguide/images/drag-handle-dashboard.png)) of a column name and drag it up or down in the list.
1. Choose **Confirm**.