Troubleshooting problems with Systems Manager Inventory - AWS Systems Manager

Troubleshooting problems with Systems Manager Inventory

This topic includes information about how to troubleshoot common errors or problems with AWS Systems Manager Inventory. If you're having trouble viewing your instances in Systems Manager, see Troubleshooting managed instance availability.

Multiple apply all associations with document 'AWS-GatherSoftwareInventory' are not supported

An error that Multiple apply all associations with document 'AWS-GatherSoftwareInventory' are not supported means that one or more AWS Regions where you're trying to configure an Inventory association for all instances are already configured with an inventory association for all instances. If necessary, you can delete the existing inventory association for all instance and then create a new one. To view existing inventory associations, choose State Manager in the Systems Manager console and then locate associations that use the AWS-GatherSoftwareInventory SSM document. If the existing inventory association for all instances was created across multiple Regions, and you want to create a new one, you must delete the existing association from each Region where it exists.

Inventory execution status never exits pending

There are two reasons why inventory collection never exits the Pending status.

  1. No instances in the selected AWS Region:

    If you create a global inventory association by using Systems Manager Quick Setup, the status of the inventory association (AWS-GatherSoftwareInventory document) shows Pending if there are no instances available in the selected Region.

  2. Insufficient permissions:

    An inventory association shows Pending if one or more instances don't have permission to run Systems Manager Inventory. Verify that the AWS Identity and Access Management (IAM) instance profile includes the AmazonSSMManagedInstanceCore managed policy. For information about how to add this policy to an instance profile, see Task 2: Add permissions to a Systems Manager instance profile (console).

    At a minimum, the instance profile must have the following IAM permissions.

    { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "ssm:DescribeAssociation", "ssm:ListAssociations", "ssm:ListInstanceAssociations", "ssm:PutInventory", "ssm:PutComplianceItems", "ssm:UpdateAssociationStatus", "ssm:UpdateInstanceAssociationStatus", "ssm:UpdateInstanceInformation", "ssm:GetDocument", "ssm:DescribeDocument" ], "Resource": "*" } ] }

The AWS-ListWindowsInventory document fails to run

The AWS-ListWindowsInventory document is deprecated. Don't use this document to collect inventory. Instead, use one of the processes described in Configuring inventory collection.

Console doesn't display Inventory Dashboard | Detailed View | Settings tabs

The Inventory Detailed View page is only available in AWS Regions that offer Amazon Athena. If the following tabs aren't displayed on the Inventory page, it means Athena isn't available in the Region and you can't use the Detailed View to query data.


                    Displaying Inventory Dashboard | Detailed View | Settings tabs

UnsupportedAgent

If the detailed status of an inventory association shows UnsupportedAgent, and the Association status shows Failed, then the version of AWS Systems Manager SSM Agent on the instance isn't correct. To create a global inventory association (to inventory all instances in your AWS account) for example, you must use SSM Agent version 2.0.790.0 or later. You can view the agent version running on each of your instances on the Managed Instances page in the Agent version column. For information about how to update SSM Agent on your instances, see Update SSM Agent by using Run Command.

Skipped

If the status of the inventory association for an instance shows Skipped, this means that you created a global inventory association (to collect inventory from all instances), but the skipped instance already had an inventory association assigned to it. The global inventory association wasn't assigned to this instance, and no inventory was collected by the global inventory association. However, the instance will still report inventory data when the existing inventory association runs.

If you don't want the instance to be skipped by the global inventory association, you must delete the existing inventory association. To view existing inventory associations, choose State Manager in the Systems Manager console and then locate associations that use the AWS-GatherSoftwareInventory SSM document.

Failed

If the status of the inventory association for an instance shows Failed, this could mean that the instance has multiple inventory associations assigned to it. An instance can only have one inventory association assigned at a time. An inventory association uses the AWS-GatherSoftwareInventory AWS Systems Manager document (SSM document). You can run the following command by using the AWS Command Line Interface (AWS CLI) to view a list of associations for an instance.

aws ssm describe-instance-associations-status --instance-id instance ID