Skip to main content

Overview

AWS Systems Manager provides a unified user interface where you can track and resolve operational issues across your applications and resources on AWS, including Amazon Elastic Compute Cloud (EC2), Amazon Relational Database Service (RDS), Amazon Elastic Container Service (ECS), and Amazon Elastic Kubernetes Service (EKS) instances and in multicloud and hybrid environments. With AWS Systems Manager, you can start for free with features included with the AWS Free Tier. There are no minimum fees or upfront commitments. Limits may apply.

AWS Pricing Calculator

Calculate your AWS Systems Manager and architecture cost in a single estimate.

Create your custom estimate now

Just-in-time Node Access

Just-in-time node access helps remove long-standing permissions to nodes while maintaining operational efficiency. Customers can move towards zero-standing privileges by requiring operators to request access to Amazon EC2, hybrid, and multicloud nodes managed by AWS Systems Manager.

Just-in-time node access is an account level feature. When you enable just-in-time node access in an account, all nodes managed by AWS Systems Manager are enabled with the feature. For accounts enabled across an AWS Organization, all usage across accounts and Regions is aggregated in the Consolidated Billing family.

Just-in-time node access also provides a one-time free trial. Every AWS account in each Region that is enabled with just-in-time node access receives a free trial. You will be able to use just-in-time node access at no additional charge for the remainder of the billing cycle that just-in-time node access was enabled as well as one additional billing cycle.

If an account is opted into just-in-time node access, any nodes in that account using the advanced on-premises instance tier will not incur a cost. See the “On-Premises Instance Management” section of this page for more information on the advanced on-premises instance tier.

Pricing

Just-in-time node access is priced per node per hour for nodes managed by the SSM Agent. You are billed per node per hour at the hourly rate based on the below table:

Volume
Price per node per hour
First 72,000 hours
$0.0137 
Next 647,999 hours (72,001 hours to 720,000 hours)
$0.0103
Next 6,479,999 hours (720,001 hours to 7,200,000 hours)
$0.0034
Hours above 7,200,001 hours
$0.0014

Pricing Examples

Example #1

You enable just-in-time node access for an account. That account has 200 EC2 instances which were managed by AWS Systems Manager over the course of a billing period. Each of those 200 AWS Systems Manager managed nodes were managed for 100 hours, resulting in a total usage of 20,000 Systems Manager managed node hours.

All 20,000 node hours are billed at $0.0137/hour, for a total expected billing period cost of $274.00.

Example #2

You have a Consolidated Billing family for your AWS Organization. You enable just-in-time node access for half of the Organization Units in your AWS Organization, and the nodes in those Organization Units accumulate 1,000,000 Systems Manager managed node hours over the course of a billing period.

First 72,000 node hours = 72,000 node hours * $0.0137/node/hour = $986.40

Next 647,999 node hours = (720,000 node hours – 72,001 node hours) * $0.0103/node/hour = $6,674.39

Next 279,999 node hours = (1,000,000 node hours – 720,001 node hours) * $0.0034/node/hour = $952.00

Total expected billing period cost = $986.40 + $6,674.39 + $952.00 = $8,612.79

Average cost per node per hour = $0.0086

AWS Free Tier

As part of the AWS Free Tier, you can get started with the following AWS Systems Manager features for free. Limits may apply.

Explorer

No additional charges apply for enabling Explorer. Limits may apply.

Explorer uses priced OpsCenter APIs (GetOpsSummary) to populate its dashboard. Charges from these API requests will apply. The Export to CSV option executes an Automation document with an aws:executeScript action step. These steps may be charged as per Automation pricing.

OpsCenter

OpsCenter provides a central location that operations engineers and IT professionals can use to view, investigate, and resolve operational issues related to any AWS resource. Operational issues, referred to as OpsItems, are aggregated and standardized in a consolidated view, providing contextually relevant data that helps with diagnosis and remediation.

OpsCenter is priced on a pay-per-use model. You’ll be charged based on the number of OpsItems created in your account per month, as well as the number of Get, Describe, Update, and GetOpsSummary API calls made. Additionally, the service calls other public APIs in order to surface relevant diagnostic information, which will be included in the bill from each respective service.

Pricing

OpsCenter Details
Pricing
Number of OpsItems
$2.97 per 1,000 OpsItems
Get, Describe, Update, and GetOpsSummary API requests
$0.039 per 1,000 requests

Pricing example

Assume you begin a month with 10,000 OpsItems in your account, and over the course of the month you create 1,000 new OpsItems. Over the course of the month you also make 100,000 Get, Describe, Update, and GetOpsSummary API requests for your OpsItems. Your monthly bill will be as follows:

Cost of creating 1,000 OpsItems = 1,000 OpsItems * $2.97 per 1,000 OpsItems created = $2.97

Cost of 100,000 create API request = 0

Cost of 100,000 Get, Describe, Update, and GetOpsSummary API requests = 100,000 * $0.039 per 1,000 API = $3.90

Total monthly cost = Cost of creating new OpsItems + Cost of Get, Describe, Update, and GetOpsSummary API requests = $6.87 per 1,000 OpsItems and corresponding 100,000 API requests

Additional charges: You may incur additional charges if the operation of your application workflow utilizes other AWS services or transfers data. For example, if your application workflow invokes an AWS Lambda function, you will be billed for each request and for the duration of each Lambda function. For details on AWS service pricing, see the pricing section of the relevant AWS service detail pages. Except as otherwise noted, our prices are exclusive of applicable taxes and duties, including VAT, GST, and applicable sales tax.

Incident Manager

Incident Manager helps you prepare for incidents with automated response plans. Response plans execute runbook actions, track incident updates, and enable chat-based collaboration while automatically notifying the appropriate people to respond. With Incident Manager, you are charged based on the number of response plans active in a month. Incident Manager includes up to 100 SMS or Voice messages per month; additional messages are charged based on the recipient’s country.

Additionally, response plans use Systems Manager OpsCenter and Automation to track actions and execute runbooks; you will be charged based on OpsCenter and Automation pricing for OpsItems created and runbook steps executed. CloudWatch customers will also be billed separately for their metrics, alarms, and dashboards.

Pricing

Details
Pricing
Response plans
$7 per response plan per month
SMS & Voice messages * Incident Manager includes 100 SMS or Voice message free per month
Per message, based on destination country rates for SMS and 1-minute Voice messages

Pricing Examples

Example 1

Assume your team has two response plans: one that helps automate failover to a backup system and another that automates response to all other application alarms. Over the course of the month, you handle 20 incidents resulting in 120 messages via SMS to the United States. Your monthly bill will be as follows:

Cost of 2 response plans: 2 response plans * $7 = $14

100 messages included free per month: 100 messages

Cost of 120 messages: 120 messages - 100 included messages = 20 additional messages

Cost of 20 messages to the US: 20 * Cost per SMS message @ $0.01 = $0.20

Total monthly cost = Cost of response plans + cost of additional messages = $14 + $0.20 = $14.20

Example 2

Assume your major incident team has one response plan that was created on the 15th day of the month for automating major incident response. The response plan automates sending 50 messages via SMS to the United Kingdom. Over the course of the month, you handle three incidents resulting in 150 notifications. Your bill for the month will be as follows:

Cost of 1 response plan for part of a month (0.5 month): 0.5 response plan months * $7 = $3.50

100 messages included free per month: 100 messages

Cost of 150 messages: 150 messages - 100 included messages = 50 additional messages

Cost of 50 messages to the UK: 50 * Cost per SMS message @ $0.04 = $2.00

Total monthly cost = Cost of response plans + Cost of additional messages = $3.50 + $2.00 = $5.50

AppConfig

With AppConfig, you can configure, validate, deploy, and monitor your feature flags or any dynamic configuration. Those flags and configurations can be validated syntactically or semantically in the pre-deployment phase, and can be monitored and automatically rolled back if an Amazon CloudWatch alarm that you have configured is triggered. Using AWS AppConfig, you can reduce errors in configuration changes, deploy changes across a set of targets quickly, update applications with reduced opportunities for interruption, and control deployment of changes across your applications.

You pay only for what you use.

With AWS AppConfig, you pay each time you request configuration data from AWS AppConfig via API calls, as well as each time your requesting target receives configuration data in response to that request.

A target refers to the host that receives the application configuration (this could be an Amazon EC2 instance, on-premises server, container, AWS Lambda function, mobile app, IoT device, etc.).  If you are using multi-variant feature flags, you will not be charged when requesting data on multiple variants within the same version of a flag or configuration profile, as variant data is cached locally.

Pricing

Configuration requests via API Calls
$0.0000002 per configuration request
Configurations Received
$0.0008 per configuration received

AWS AppConfig pricing example

Assume you have one application configuration that updates three times a day. Also assume that you have 2,000 targets in your fleet that are requesting configuration data via API, every two minutes, to check if an updated configuration is available. Each time an updated configuration is available, AWS AppConfig sends the updated configuration in response to the request for configuration. Over the course of a month, your targets will receive a total of 180,000 (updated) configurations and your bill would be as follows:

Cost of configuration requests = 1 (configurations) * 2000 (servers) * 0.5 (calls per minute) * 60 (minutes) * 24 (Hours)* 30 (days) * $0.0000002 (price per request)
=$8.64

Cost of configurations received =1 (configurations) * 2000 (servers) * 3 (updates a day) * 30 (days) * $0.0008 (price per configuration received)
=$144

Total monthly cost = $152.64

Parameter Store

AWS Systems Manager Parameter Store consists of standard and advanced parameters. Standard parameters are available at no additional charge. When you create advanced parameters, you are charged based on the number of advanced parameters stored each month and per API interaction. Charges for parameters stored for less than a month are prorated on an hourly basis. To learn more about advanced parameters visit the AWS Systems Manager documentation or product page.

Pricing - Parameter Store

Parameter type
Pricing
Standard
No additional charge
Advanced
$0.05 per advanced parameter per month (prorated hourly if the parameter is stored less than a month)

Pricing - API Interactions

Parameter type
Pricing - Standard Throughput
Pricing - Higher Throughput
Standard
No additional charge
$0.05 per 10,000 Parameter Store API interactions
Advanced
$0.05 per 10,000 Parameter Store API interactions
$0.05 per 10,000 Parameter Store API interactions

A Parameter Store API interaction is defined as an interaction between an API request and an individual parameter. For example, if a Get request returns ten parameters, that counts as ten Parameter Store API interactions.

Pricing Examples

Example 1

Assume you have 5,000 parameters, 500 of which are advanced parameters. Assume that you have enabled higher throughput limits and interact with each parameter 24 times per day, equating to 3,600,000 interactions per 30-day month. Because you have enabled higher throughput, your API interactions will be charged for standard and advanced parameters. Your monthly bill will be the sum of the cost of the advanced parameters and the API interactions, as follows:

Cost of 500 advanced parameters = 500 * $0.05 per advanced parameter = $25

Cost of 3.6M API interactions = 3.6M * $0.05 per 10,000 interactions = $18

Total monthly cost = $25 + $18 = $43

Example 2

Assume you have 15,000 parameters, 7,000 of which are advanced parameters. Further assume that 3,000 of these advanced parameters expire after 15 hours, and that you have disabled the higher throughput limit. You interact with your parameters 50 million times a month, of which only 20 million interactions are with advanced parameters. Your monthly bill will be the sum of the cost of advanced parameters and API interactions for advanced parameters, as follows:

Cost of 3,000 parameters stored for less than one month = 3,000 * 0.001008 (monthly rate prorated for 15 hours) = $3.02

Cost of 4,000 parameters stored for one month = 4000 * $0.05 = $200

Cost of 7,000 advanced parameters = $200 + $3.02 = $203.02

Cost of 20M API interactions = 20M * $0.05 per 10,000 interactions = $100

Total monthly cost = $203.02 + $100 = $303.02