Troubleshooting Systems Manager Explorer - AWS Systems Manager

Troubleshooting Systems Manager Explorer

This topic includes information about how to troubleshoot common problems with AWS Systems Manager Explorer.

Not able to filter AWS resources in Explorer after updating tags on the Settings page

If you update tags keys or other data settings in Explorer, the system can take up to six hours to synchronize data based on your changes.

The AWS Organizations options on the Create resource data sync page are greyed out

The Include all accounts from my AWS Organizations configuration and Select organization units in AWS Organizations options on the Create resource data sync page are only available if you set up and configured AWS Organizations. If you set up and configured AWS Organizations, then either the AWS Organizations management account or an Explorer delegated administrator can create resource data syncs that use these options.

For more information, see Setting up Systems Manager Explorer to display data from multiple accounts and Regions and Configuring a delegated administrator.

Explorer doesn't display any data at all

  • Verify that you completed Integrated Setup in each account and Region where you want Explorer to access and display data. If you don't, Explorer won't display OpsData and OpsItems for those accounts and Regions in which you didn't complete Integrated Setup. For more information, see Getting started with Systems Manager Explorer and OpsCenter.

  • When using Explorer to view data from multiple accounts and Regions, verify that you're logged into the AWS Organizations management account. To view OpsData and OpsItems from multiple accounts and Regions, you must be signed in to this account.

Widgets about Amazon EC2 instances don't display data

If widgets about Amazon Elastic Compute Cloud (Amazon EC2) instances, such as the Instance count, Managed instances, and Instance by AMI widgets don't display data, then verify the following:

  • Verify that you waited several minutes. OpsData can take several minutes to display in Explorer after you completed Integrated Setup.

  • Verify that you configured AWS Config configuration recorder. Explorer uses data provided by AWS Config configuration recorder to populate widgets with information about your EC2 instances. For more information, see Managing the Configuration Recorder.

  • Verify that the Amazon EC2 OpsData source is active on the Settings page. Also, verify that more than 6 hours have passed since you activated configuration recorder or since you made changes to your instances. Systems Manager can take up to six hours to display data from AWS Config in Explorer EC2 widgets after you initially activated configuration recorder or make changes to your instances.

  • Be aware that if an instance is either stopped or terminated, then Explorer stops showing those instances after 24 hours.

  • Verify that you're in the correct AWS Region where you configured your Amazon EC2 instances. Explorer doesn't display data about on-premises instances.

  • If you configured a resource data sync for multiple accounts and Regions, verify that you're signed in to the Organizations management account.

Patch widget doesn't display data

The Non-compliant instances for patching widget only displays data about patch instances that aren't compliant. This widget displays no data if your instances are compliant. If you suspect that you have non-compliant instances, then verify that you set up and configured Systems Manager patching and use AWS Systems Manager Patch Manager to check your patch compliance. For more information, see AWS Systems Manager Patch Manager.

Miscellaneous issues

Explorer doesn't let you edit or remediate OpsItems: OpsItems viewed across accounts or Regions are read-only. They can only be updated and remediated from their home account or Region.