Amazon Systems Manager Pricing

With Amazon Systems Manager, you pay only for what you use on the following priced features, as you use them. There are no minimum fees or upfront commitments. Features that are provided at no additional charge are listed here. Limits may apply.

No additional charges. Limits may apply.

No additional charges. Limits may apply.

No additional charges. Limits may apply.

No additional charges. Limits may apply.

No additional charges. Limits may apply.

No additional charges. Limits may apply.

No additional charges. Limits may apply.

No additional charges. Limits may apply.

No additional charges. Limits may apply.

No additional charges. Limits may apply.

Amazon 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 Amazon Systems Manager documentation or product page.

Information about Parameter Store API throughput limits is available on the Systems Manager limits page. Higher throughput limit settings are applied per account per region. After a higher throughput is enabled, you will be charged per Parameter Store API interaction for standard and advanced parameters. 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.

Parameter Store pricing example 1

Assume you have 5,000 parameters, of which 500 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.352 per advanced parameter = ¥176

Cost of 3.6M API interactions = 3.6M * ¥0.352 per 10,000 interactions = ¥126.72

Total monthly cost = ¥176 + ¥126.72 = ¥302.72

 

Parameter Store pricing example 2

Assume you have 15,000 parameters, of which 7,000 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 50M times a month, of which only 20M 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.0074 (monthly rate prorated for 15 hours) = ¥22.2

Cost of 4,000 parameters stored for one month = 4000 * ¥0.352 = ¥1408

Cost of 7,000 advanced parameters = ¥1408 + ¥22.2 = ¥1430.2

Cost of 20M API interactions = 20M * ¥0.352 per 10,000 interactions = ¥704

Total monthly cost = ¥1430.2 + ¥704 = ¥2134.2

Amazon Web Services AppConfig enables you to provide validation logic to ensure your configuration data is syntactically and semantically correct according to your definitions before making it available to your application. Amazon Web Services AppConfig also gives you the ability to roll out configuration changes over a defined time period while monitoring your application so that you can catch errors and roll back the changes if needed, to help you minimize the impact to the users.
You pay only for what you use.

With Amazon Web Services AppConfig, you pay for each GetConfiguration API call made by your targets, and for each configuration a target receives from Amazon AppConfig in response to a GetConfiguration API call.
Note: Amazon Web Services AppConfig’s GetConfiguration API uses the value of the ClientConfigurationVersion parameter to identify the configuration version last received by your target. If you do not send the ClientConfigurationVersion parameter with each call to GetConfiguration, your target will receive the most current configuration available, even if your target already has that configuration. Since you are charged based on the number of configurations received, not sending the ClientConfigurationVersion could also result in unwanted charges.

A target refers to the host that receives the application configuration (this could be an Amazon EC2 instance, on-premises server, container, Amazon Lambda function, mobile app, or IOT device etc).

Amazon AppConfig pricing example

Assume you have one application configuration that updates three times a day. Also assume that you have 2000 targets in your fleet that are calling the GetConfiguration API, every two minutes, to check if an updated configuration is available. Each time an updated configuration is available, Amazon AppConfig sends the updated configuration in response to the GetConfiguration API call. 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 GetConfiguration API Calls = 1 (configurations)* 2000(Servers)*0.5(calls per minute)*60(minutes)*24(Hours)*30(days)* ¥1.43 Per 1M calls
= ¥61.78
Cost of configurations received =1(configurations)* 2000(servers)*3(updates a day)*30(days) *(price per configuration received ) ¥0.00572
= ¥ 1029.6
Total Bill = ¥ 1091.376

You can set your account- and Region-level settings for on-premises instances to either standard or advanced. With standard on-premises instances, you will be able to register up to 1,000 on-premises instances per account per Region at no additional charge.

If you need to register a larger number of on-premises instances, you can change your account- and Region-level settings for on-premises instances to advanced. This will convert all the existing instances in the account and Region from standard to “advanced.” With advanced on-premises instances, you will also be able to use Systems Manager Session Manager to interactively access your on-premises instances. With this setting, you will also be able to use Systems Manager Patch Manager to patch Microsoft applications hosted on on-premises instances.

Systems Manager advanced instances are priced on a pay-as-you-go basis. You are charged based on the number of advanced instances activated as Systems Manager managed instances and the hours those instances are running. Charges are not incurred for the hours where an advanced on-premises instance is de-registered, shut down, or terminated for the entire hour. This pricing applies to instances (on-premises, other cloud, or Amazon EC2) registered using Systems Manager activations.

Visit the Amazon Systems Manager documentation or product page to learn more about advanced on-premises instance management. 

Pricing example

You have 500 on-premises instances registered in account A with standard on-premises instance management setting and 1,500 on-premises instances registered in account B for 10 days with advanced on-premises instance management setting.

Cost of 500 instances on standard on-prem instance management in account A = No charge

Cost of 1,500 instances on advanced on-prem instance management in account B = 1,500 * ¥0.049 * 10 * 24 = ¥17,640

Total monthly cost for account A and B would be ¥17,640
 

Distributor, a Systems Manager feature, helps you distribute and maintain software packages, such as software agents, on your instances. These packages can be Amazon Web Services service agents or your own agents imported into Systems Manager. Distribution and update checks of Amazon Web Services agents are provided at no additional charge.

For your own packages, you pay only for what you use. Upon transferring a package into Distributor, you will be charged based on the size and duration of storage for that package, the number of Get and Describe API calls made, and the amount of out-of-Region and on-premises data transfer out of Distributor for those packages.

Distributor pricing example

Assume you have 100 Amazon EC2 instances and 25 on-premises instances, each requiring three Amazon Web Services packages and two 100 MB non-Amazon Web Services packages to be updated on a monthly basis. You choose to check for updates twice a day, resulting in 15,000 Get/Describe API calls for the non-Amazon Web Services packages.

Your monthly bill will be as follows:

Cost of distributing 3 Amazon Web Services packages across 125 instances = ¥0

Storage: Cost of storing 2 non-Amazon Web Services packages = 2*100 MB * ¥0.323 per GB = ¥64.6
Get, Describe API calls: Cost of 15,000 API calls = 15,000 * ¥0.176 per 1,000 API calls = ¥2.64
Data Transfer: Cost of updating 2 non-Amazon Web Services packages on 25 on-premises instances = 25 * 2 * 100 MB * ¥6.336 per GB = ¥31.68

Total monthly charges = ¥64.6 + ¥2.64 + ¥31.68 = ¥98.92 or ¥0.7913 per instance

Automation, an Amazon Systems Manager feature, allows you to safely automate common and repetitive IT operations and management tasks across Amazon Web Services resources. You pay only for what you use and are charged based on the number and type of steps.

Basic steps

A step is defined as an initiated action performed in the Automation execution on a per-resource basis. There is a free tier of 100,000 basic steps per account per month. Beyond the free tier, each basic step is charged at ¥0.0137 per step. All steps are considered basic steps unless otherwise categorized below as special steps.

Special steps

Special steps are free-tier ineligible. Below are the types of special steps:

Multi-account/multi-Region steps – Each multi-account/multi-Region step will be charged at ¥0.0274 per step. The multi-account/multi-Region steps are counted in the originating location (account and Region) only. They are not counted in the target locations.

Automation pricing example

Assume you execute 125,000 steps in a calendar month. 5,000 are multi-account special steps from account A to account B. Both accounts are in Amazon Web Services China (Beijing) Region, operated by Sinnet and 120,000 are local to account A. Your bill will be as follows:

Account A Basic steps:

Total steps (120,000) - Free tier (100,000) = billable basic steps (20,000)

20,000 basic steps * ¥0.0137/basic step = ¥274

Account A Special steps:

5,000 multi-account steps * ¥0.0274/multi-account step = ¥137

Total monthly charges for account A = ¥274 + ¥137 = ¥411

Total monthly charges for account B = No charge in this example

Your application workflow may incur other charges if it uses other Amazon Web Services services or transfers data. For example, if your application workflow invokes an Amazon Lambda function, you will be billed for that Amazon Lambda use based on your Amazon Lambda pricing. For details, see the pricing section of the Amazon Web Services service or the data transfer type you’re using.

Amazon Systems Manager Change Manager provides a central location where operators and engineers can request operational changes for their IT infrastructure and configuration. Once created, each change request will use a pre-defined approval workflow based on that change's template. Once approved, the change can be implemented automatically or initiated manually.

Any new account to Change Manager can try the feature for 30 days at no additional cost in Amazon Web Services China (Beijing) Region, operated by Sinnet, and Amazon Web Services China (Ningxia) Region, operated by NWCD. You will have access to the full feature set during the free trial. The Change Manager console indicates how many days are left on the 30-day period and estimates how much the monthly average cost for your account is based on your activity. This makes it easy for you to try Change Manager at no additional cost.

Change Manager pricing example

Assume over the course of the month you create 50 new change requests to make changes. During the same month you also make 10,000 Get, Describe, Update, and GetOpsSummary API requests for your change requests. Your monthly bill will be as follows:

Cost of creating 50 change requests: 50 change requests * ¥1.909 per change request created = ¥95.46

Cost of 50 create API requests =¥0

Cost of 10,000 Get, Describe, Update, and GetOpsSummary API requests = 10,000 * ¥0.252 per 1,000 API requests = ¥2.515

Total monthly cost = Cost of creating new change requests + Cost of Get, Describe, Update, and GetOpsSummary API requests = ¥97.97

OpsCenter provides a central location that operations engineers and IT professionals can use to view, investigate, and resolve operational issues related to any Amazon Web Services 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

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 * ¥20.91 per 1,000 OpsItems created = ¥20.91

Cost of 100,000 create API request = 0

Cost of 100,000 Get, Describe, Update, and GetOpsSummary API requests = 100,000 * ¥0.275 per 1,000 API = ¥27.5

Total monthly cost = Cost of creating new OpsItems + Cost of Get, Describe, Update, and GetOpsSummary API requests = ¥48.41 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 Amazon Web Services services or transfers data. For example, if your application workflow invokes an Amazon Lambda function, you will be billed for each request and for the duration of each Lambda function. For details on Amazon Web Services service pricing, see the pricing section of the relevant Amazon Web Services service detail pages.