AWS Systems Manager endpoints and quotas

100

When you add an application in Application Manager, Systems Manager automatically creates a resource group to organize all of the resources for that application. The maximum number of applications is based on the underlying quota for AWS Resource Groups.

For applications based on AWS CloudFormation stacks: 200

For applications based on AWS Resource Groups: Unlimited

100

Each AWS account can run 100 automations concurrently. This quota can be increased up to 500 by enabling adaptive concurrency. Additionally, you can run up to 400 concurrent automations with blocking actions. Blocking actions include aws:approve, aws:pause, and aws:sleep. If you attempt to run more automations than this, Systems Manager adds the additional automations to a queue and displays a status of Pending. For more information about adaptive concurrency, see Allowing Automation to adapt to your concurrency needs in the AWS Systems Manager User Guide.

5000

If you attempt to run more automations than the concurrent automation limit, subsequent automations are added to a queue. Each AWS account can queue 5,000 automations. When an automation completes (or reaches a terminal state), the first automation in the queue is started.

25

Each AWS account can run 25 rate control automations simultaneously. If you attempt to run more rate control automations than the concurrent rate control automation limit, Systems Manager adds the subsequent rate control automations to a queue and displays a status of Pending.

1000

If you attempt to run more automations than the concurrent rate control automation limit, subsequent automations are added to a queue. Each AWS account can queue 1,000 rate control automations. When an automation completes (or reaches a terminal state), the first automation in the queue is started.

5

A parent-level Automation runbook can start a child-level Automation runbook. This represents one level of nested automation. The child-level Automation runbook can start another Automation runbook, resulting in two levels of nested automation. This can continue up to a maximum of five (5) levels below the top-level parent Automation runbook.

30

30

1,000

12 hours

If you expect an automation to run longer than 12 hours, then you must run the automation by using a service role (or assume role).

10 minutes

Each executeScript action can run up to a maximum duration of 10 minutes.

Up to 100KB.

5 minutes

Each invokeLambdaFunction action can run up to a maximum duration of five (5) minutes.

Up to 200KB.

5

Each runbook can have up to five (5) attachments.

256 MB

Each attachment can be up to 256 MB.

Maximum size of any single AWS:ComplianceItem object

800 KB

Maximum number of attachments in a Distributor package

20

Maximum size per attachment in a Distributor package

1 GB

Maximum number of files in a Distributor package

1000

Maximum number of Distributor packages per AWS account, per Region

500

Maximum number of package versions per Distributor package

25

Maximum package size in Distributor

20 GB

Maximum package manifest size in Distributor

64 KB

Maximum number of resource data syncs (per AWS account per Region)

5

Maximum Remote Desktop session limit

60 minutes

Maximum number of Remote Desktop sessions (per AWS account per Region)

The maximum number of concurrent Remote Desktop sessions (per AWS account per Region) for AWS Systems Manager GUI Connect. Service quota increase requests up to 25 are automatically approved. Service quota increases can take up to two and a half hours to take effect.

5

Maximum number of resource data syncs (per AWS account per Region)

5

Inventory data collected per instance per call

1 MB

This maximum adequately supports most inventory collection scenarios. When this quota is reached, no new inventory data is collected for the instance. Inventory data previously collected is stored until the expiration.

Inventory data collected per instance per day

5000 KB

When this quota is reached, no new inventory data is collected for the instance. Inventory data previously collected is stored until the expiration.

Custom inventory types

20

You can add up to 20 custom inventory types.

Custom inventory type size

200 KB

This is the maximum size of the type, not the inventory collected.

Custom inventory type attributes

50

This is the maximum number of attributes within the custom inventory type.

Inventory data expiration

30 days

If you terminate an instance that is configured to collect inventory data, Systems Manager retains the inventory data for 30 days and then deletes it. For running instances, inventory data older than 30 days is deleted. If you need to store inventory data longer than 30 days, you can use AWS Config to record history or periodically query and upload the data to an Amazon S3 bucket. For more information, see, Recording Software Configuration for Managed Instances in the AWS Config Developer Guide.

Maintenance windows per AWS account

50

Tasks per maintenance window

20

Targets per maintenance window

100

Managed node IDs per target

50

Targets per task

10

Concurrent executions of a single maintenance window

1

Concurrent executions of maintenance windows

5

Execution history retention

30 days

2400

If your use case requires more managed nodes, contact AWS Support to increase your fleet size.

Standard instances: 1,000 (per account per Region)

Advanced instances: Advanced instances are available on a pay-per-use basis. Advanced instances also enable you to connect to your non-EC2 machines by using AWS Systems Manager Session Manager. For more information about activating non-EC2 machines for use in your hybrid and multicloud environment, see Setting up Systems Manager for hybrid and multicloud environments in the AWS Systems Manager User Guide. For more information about enabling advanced instances, see Configuring instance tiers.

Total number of OpsItems allowed per AWS account per Region (including Open and Resolved OpsItems)

500,000

Maximum number of OpsItems per AWS account per month

10,000

Maximum operational data value size

20 KB

Maximum number of associated Automation runbooks per OpsItem

10

Maximum number of Automation runbook executions stored in operational data under a single associated runbook

10

Maximum number of related resources you can specify per OpsItem

100

Maximum number of related OpsItems you can specify per OpsItem

10

Maximum length of a deduplication string

512 characters

Total number of parameters allowed

(per AWS account and Region)

Standard parameters: 10,000

Advanced parameters: 100,000

For more information about advanced parameters, see Managing parameter tiers in the AWS Systems Manager User Guide.

Maximum size for parameter value

Standard parameter: 4 KB

Advanced parameter: 8 KB

Maximum number of parameter policies per advanced parameter

10

Maximum throughput (transactions per second)

Standard throughput: 40 (Shared by the following API actions: GetParameter, GetParameters, GetParametersByPath)

Higher throughput: 10,000 (GetParameter)

Higher throughput: 1,000 (GetParameters)

Higher throughput: 100 (GetParametersByPath)

SecureStrings may be limited to KMS throughput limits depending on the region. For more information on KMS limits, see Request quotas in the AWS Key Management Service Developer Guide

For more information about Parameter Store throughput, see Increasing Parameter Store throughput in the AWS Systems Manager User Guide.

Maximum history for a parameter

100 past values

Patch baselines per AWS account

50

Patch groups per patch baseline

25

30 days

The history of each command is available for up to 30 days. In addition, you can store a copy of all log files in Amazon Simple Storage Service or have an audit trail of all API calls in AWS CloudTrail.

Idle time before session termination

Default: 20 minutes

Configurable to between 1 and 60 minutes.

Execution history retention

30 days

The history of each command is available for up to 30 days. In addition, you can store a copy of all log files in Amazon Simple Storage Service or have an audit trail of all API calls in AWS CloudTrail.

64 KB

A single SSM document can have a maximum size of 64 KB.

500

Each AWS account can create a maximum of 500 documents per Region.

1000

A single SSM document can have a maximum of 1,000 versions.

1000

A single SSM document can be shared with a maximum of 1000 AWS accounts.

5

Each AWS account can publicly share a maximum of five documents.

20

2,000

Each AWS account can have a maximum of 2,000 associations per Region.

1,000

A single State Manager association can have a maximum of 1,000 versions.