AWS AWS Systems Manager Error Codes

The requester doesn't have permissions to perform the requested operation.

Error returned if an attempt is made to register a patch group with a patch baseline that is already registered with a different patch baseline.

You must disassociate a document from all managed nodes before you can delete it.

The specified association already exists.

The specified association doesn't exist.

The specified execution ID doesn't exist. Verify the ID number and try again.

You can have at most 2,000 active associations.

You have reached the maximum number versions allowed for an association. Each association has a limit of 1,000 versions.

Indicates that the Change Manager change template used in the change request was rejected or is still in a pending state.

An Automation runbook with the specified name couldn't be found.

An Automation runbook with the specified name and version couldn't be found.

The number of simultaneously running Automation executions exceeded the allowable limit.

There is no automation execution information for the requested automation execution ID.

The specified step name and execution ID don't exist. Verify the information and try again.

You specified too many custom compliance types. You can specify a maximum of 10 different types.

You have exceeded the limit for custom schemas. Delete one or more custom schemas and try again.

The specified document already exists.

You can have at most 500 active SSM documents.

The document can't be shared with more Amazon Web Services accounts. You can specify a maximum of 20 accounts per API operation to share a private document. By default, you can share a private document with a maximum of 1,000 accounts and publicly share up to five documents. If you need to increase the quota for privately or publicly shared Systems Manager documents, contact Amazon Web Services Support.

The document has too many versions. Delete one or more document versions and try again.

Error returned when the ID specified for a resource, such as a maintenance window or patch baseline, doesn't exist. For information about resource quotas in Amazon Web Services Systems Manager, see Systems Manager service quotas in the Amazon Web Services General Reference.

The content of the association document matches another document. Change the content of the document and try again.

The version name has already been used in this document. Specify a different version name, and then try again.

You can't specify a managed node ID in more than one association.

You attempted to register a LAMBDA or STEP_FUNCTIONS task in a region where the corresponding service isn't available.

A hierarchy can have a maximum of 15 levels. For more information, see Requirements and constraints for parameter names in the Amazon Web Services Systems Manager User Guide.

Parameter Store doesn't support changing a parameter type in a hierarchy. For example, you can't change a parameter from a String type to a SecureString type. You must create a new, unique parameter.

Error returned when an idempotent operation is retried and the parameters don't match the original call to the API with the same idempotency token.

There is a conflict in the policies specified for this parameter. You can't, for example, specify two Expiration policies for a parameter. Review your policies, and try again.

An error occurred on the server side.

The activation isn't valid. The activation might have been deleted, or the ActivationId and the ActivationCode don't match.

The activation ID isn't valid. Verify that you entered the correct ActivationId or ActivationCode and try again.

The specified aggregator isn't valid for the group type. Verify that the aggregator you provided is supported.

The request doesn't meet the regular expression requirement.

The association isn't valid or doesn't exist.

The version you specified isn't valid. Use ListAssociationVersions to view all versions of an association according to the association ID. Or, use the $LATEST parameter to view the latest version of the association.

The supplied parameters for invoking the specified Automation runbook are incorrect. For example, they may not match the set of parameters permitted for the specified Automation document.

The signal isn't valid for the current Automation execution.

The specified update status operation isn't valid.

The specified command ID isn't valid. Verify the ID and try again.

One or more of the parameters specified for the delete operation isn't valid. Verify all parameters and try again.

The ID specified for the delete operation doesn't exist or isn't valid. Verify the ID and try again.

The specified SSM document doesn't exist.

The content for the document isn't valid.

You attempted to delete a document while it is still shared. You must stop sharing the document before you can delete it.

The version of the document schema isn't supported.

The SSM document type isn't valid. Valid document types are described in the DocumentType property.

The document version isn't valid or doesn't exist.

The filter name isn't valid. Verify that you entered the correct name and try again.

The specified key isn't valid.

The specified filter option isn't valid. Valid options are Equals and BeginsWith. For Path filter, valid options are Recursive and OneLevel.

The filter value isn't valid. Verify the value and try again.

The following problems can cause this exception: You don't have permission to access the managed node. Amazon Web Services Systems Manager Agent (SSM Agent) isn't running. Verify that SSM Agent is running. SSM Agent isn't registered with the SSM endpoint. Try reinstalling SSM Agent. The managed node isn't in a valid state. Valid states are: Running, Pending, Stopped, and Stopping. Invalid states are: Shutting-down and Terminated.

The specified filter value isn't valid.

The specified filter value isn't valid.

The specified inventory group isn't valid.

You specified invalid keys or values in the Context attribute for InventoryItem. Verify the keys and values, and try again.

The request isn't valid.

One or more content items isn't valid.

The query key ID isn't valid.

The specified token isn't valid.

One or more configuration items isn't valid. Verify that a valid Amazon Resource Name (ARN) was provided for an Amazon Simple Notification Service topic.

The delete inventory option specified isn't valid. Verify the option and try again.

The S3 bucket doesn't exist.

The output location isn't valid or doesn't exist.

You must specify values for all required parameters in the Amazon Web Services Systems Manager document (SSM document). You can only supply values to parameters defined in the SSM document.

The permission type isn't supported. Share is the only supported permission type.

The plugin name isn't valid.

A policy attribute or its value is invalid.

The policy type isn't supported. Parameter Store supports the following policy types: Expiration, ExpirationNotification, and NoChangeNotification.

The resource ID isn't valid. Verify that you entered the correct ID and try again.

The resource type isn't valid. For example, if you are attempting to tag an EC2 instance, the instance must be a registered managed node.

The specified inventory item result attribute isn't valid.

The role name can't contain invalid characters. Also verify that you specified an IAM role for notifications that includes the required trust policy. For information about configuring the IAM role for Run Command notifications, see Monitoring Systems Manager status changes using Amazon SNS notifications in the Amazon Web Services Systems Manager User Guide.

The schedule is invalid. Verify your cron or rate expression and try again.

The specified tag key or value isn't valid.

The target isn't valid or doesn't exist. It might not be configured for Systems Manager or you might not have permission to perform the operation.

TargetMap parameter isn't valid.

The parameter type name isn't valid.

The update isn't valid.

The command ID and managed node ID you specified didn't match any invocations. Verify the command ID and the managed node ID and try again.

The inventory item has invalid content.

The inventory item size has exceeded the size limit.

The specified policy document is malformed or invalid, or excessive PutResourcePolicy or DeleteResourcePolicy calls have been made.

The size limit of a document is 64 KB.

The requested operation is no longer supported by Systems Manager.

You don't have permission to view OpsItems in the specified account. Verify that your account is configured either as a Systems Manager delegated administrator or that you are logged into the Organizations management account.

The OpsItem already exists.

The specified OpsItem is in the process of being deleted.

A specified parameter argument isn't valid. Verify the available arguments and try again.

The request caused OpsItems to exceed one or more quotas.

The specified OpsItem ID doesn't exist. Verify the ID and try again.

The Amazon Resource Name (ARN) is already associated with the OpsItem.

The association wasn't found using the parameters you specified in the call. Verify the information and try again.

An OpsMetadata object already exists for the selected resource.

One of the arguments passed is invalid.

The OpsMetadata object exceeds the maximum number of OpsMetadata keys that you can assign to an application in Application Manager.

Your account reached the maximum number of OpsMetadata objects allowed by Application Manager. The maximum is 200 OpsMetadata objects. Delete one or more OpsMetadata object and try again.

The OpsMetadata object doesn't exist.

The system is processing too many concurrent updates. Wait a few moments and try again.

The parameter already exists. You can't create duplicate parameters.

You have exceeded the number of parameters for this Amazon Web Services account. Delete one or more parameters and try again.

Parameter Store retains the 100 most recently created versions of a parameter. After this number of versions has been created, Parameter Store deletes the oldest version when a new one is created. However, if the oldest version has a label attached to it, Parameter Store won't delete the version and instead presents this error message: An error occurred (ParameterMaxVersionLimitExceeded) when calling the PutParameter operation: You attempted to create a new version of parameter-name by calling

The parameter couldn't be found. Verify the name and try again. For the DeleteParameter and GetParameter actions, if the specified parameter doesn't exist, the ParameterNotFound exception is not recorded in CloudTrail event logs.

The parameter name isn't valid.

A parameter version can have a maximum of ten labels.

The specified parameter version wasn't found. Verify the parameter name and version, and try again.

You specified more than the maximum number of allowed policies for the parameter. The maximum is 10.

A sync configuration with the same name already exists.

Another UpdateResourceDataSync request is being processed. Wait a few minutes and try again.

You have exceeded the allowed maximum sync configurations.

The specified sync configuration is invalid.

The specified sync name wasn't found.

Error returned if an attempt is made to delete a patch baseline that is registered for a patch group.

Error returned when the caller has exceeded the default resource quotas. For example, too many maintenance windows or patch baselines have been created. For information about resource quotas in Systems Manager, see Systems Manager service quotas in the Amazon Web Services General Reference.

The specified parameter to be shared could not be found.

The hash provided in the call doesn't match the stored hash. This exception is thrown when trying to update an obsolete policy version or when multiple requests to update a policy are sent.

One or more parameters specified for the call aren't valid. Verify the parameters and their values and try again.

The PutResourcePolicy API action enforces two limits. A policy can't be greater than 1024 bytes in size. And only one policy can be attached to OpsItemGroup. Verify these limits and try again.

No policies with the specified policy ID and hash could be found.

The request exceeds the service quota. Service quotas, also referred to as limits, are the maximum number of service resources or operations for your Amazon Web Services account.

The specified service setting wasn't found. Either the service name or the setting hasn't been provisioned by the Amazon Web Services service team.

The updated status is the same as the current status.

The sub-type count exceeded the limit for the inventory type.

You specified the Safe option for the DeregisterTargetFromMaintenanceWindow operation, but the target is still referenced in a task.

The specified target managed node for the session isn't fully configured for use with Session Manager. For more information, see Setting up Session Manager in the Amazon Web Services Systems Manager User Guide. This error is also returned if you attempt to start a session on a managed node that is located in a different account or Region

The request or operation couldn't be performed because the service is throttling requests.

The Targets parameter includes too many tags. Remove one or more tags and try the command again.

There are concurrent updates for a resource that supports one update at a time.

The size of inventory data has exceeded the total size limit for the resource.

The calendar entry contained in the specified SSM document isn't supported.

Patching for applications released by Microsoft is only available on EC2 instances and advanced instances. To patch applications released by Microsoft on on-premises servers and VMs, you must enable advanced instances. For more information, see Turning on the advanced-instances tier in the Amazon Web Services Systems Manager User Guide.

The Context attribute that you specified for the InventoryItem isn't allowed for this inventory type. You can only use the Context attribute with inventory types like AWS:ComplianceItem.

Inventory item type schema version has to match supported versions in the service. Check output of GetInventorySchema to see the available schema version for each type.

The operating systems you specified isn't supported, or the operation isn't supported for the operating system.

This operation is not supported for the current account. You must first enable the Systems Manager integrated experience in your account.

The parameter type isn't supported.

The document doesn't support the platform type of the given managed node IDs. For example, you sent an document for a Windows managed node to a Linux node.

The request isn't valid. Verify that you entered valid contents for the command and try again.