To view information about recent releases and updates, see https://docs.aws.amazon.com/systems-manager/latest/userguide/systems-manager-release-history.html

Author: mark-amzn

doc_source/OpsCenter-about-incident-manager.md

@@ -1,6 +1,6 @@
 # Incident Manager<a name="OpsCenter-about-incident-manager"></a>
 
-Incident Manager, a capability of AWS Systems Manager, provides an incident management console that helps you mitigate and recover from incidents affecting your AWS hosted applications\. An *incident* is any unplanned interruption or reduction in quality of services\. After you set up and configure [Incident Manager](https://docs.aws.amazon.com/latest/userguide/what-is-incident-manager.html), the system automatically creates OpsItems in OpsCenter\. 
+Incident Manager, a capability of AWS Systems Manager, provides an incident management console that helps you mitigate and recover from incidents affecting your AWS hosted applications\. An *incident* is any unplanned interruption or reduction in quality of services\. After you set up and configure [Incident Manager](https://docs.aws.amazon.com/incident-manager/latest/userguide/what-is-incident-manager.html), the system automatically creates OpsItems in OpsCenter\. 
 
 When the system creates an incident in Incident Manager, it also creates an OpsItem in OpsCenter, and displays the incident as a related item\. If the OpsItem already exists, Incident Manager doesn't create an OpsItem\. The first OpsItem is known as the parent OpsItem\. If an incident grows in scale and scope, you can add incidents to an existing OpsItem\. If required, you can manually create an incident for an OpsItem\. After an incident is closed, you can create an analysis in Incident Manager to review and improve the remediation process for similar issues\. 
 

doc_source/OpsCenter-getting-started-multiple-accounts.md

@@ -1,8 +1,8 @@
 # \(Optional\) Setting up OpsCenter to centrally manage OpsItems across accounts<a name="OpsCenter-getting-started-multiple-accounts"></a>
 
-You can set up a central account to create manual OpsItems for member accounts, and manage and remediate those OpsItems\. The central account can be the AWS Organizations management account, or both the AWS Organizations management account and Systems Manager administrator account\. You can only use this feature after you configure AWS Organizations\. 
+You can set up a central account to create manual OpsItems for member accounts, and manage and remediate those OpsItems\. The central account can be the AWS Organizations management account, or both the AWS Organizations management account and Systems Manager delegated administrator account\. We recommend that you use the Systems Manager delegated administrator account as a central account\. You can only use this feature after you configure AWS Organizations\. 
 
-With AWS Organizations, you can consolidate multiple AWS accounts into an organization that you create and manage centrally\. A management account user, or both management account user and delegated administrator, can create OpsItems for all selected member accounts simultaneously, and manage those OpsItems\.
+With AWS Organizations, you can consolidate multiple AWS accounts into an organization that you create and manage centrally\. The central account user can create OpsItems for all selected member accounts simultaneously, and manage those OpsItems\.
 
 Use the process in this section to enable the Systems Manager service principal in Organizations and configure AWS Identity and Access Management \(IAM\) permissions for working with OpsItems across accounts\. 
 

doc_source/OpsCenter-settingup.md

@@ -0,0 +1,38 @@
+# Setting up OpsCenter<a name="OpsCenter-settingup"></a>
+
+AWS Systems Manager uses an integrated setup experience to help you get started with OpsCenter and Explorer, which are capabilities of Systems Manager\. Explorer is a customizable operations dashboard that reports information about your AWS resources\. In this documentation, Explorer and OpsCenter setup is called *Integrated Setup*\.
+
+You must use Integrated Setup to set up OpsCenter with Explorer\.  You can't set up Explorer and OpsCenter programmatically\. For more information, see [Getting started with Systems Manager Explorer and OpsCenter](Explorer-setup.md)\. 
+
+**To set up OpsCenter**
+
+1. Open the AWS Systems Manager console at [https://console\.aws\.amazon\.com/systems\-manager/](https://console.aws.amazon.com/systems-manager/)\.
+
+1. In the navigation pane, choose **OpsCenter**\.
+
+1. On the OpsCenter home page, choose **Get started**\.
+
+1. On the OpsCenter setup page, choose **Enable this option to have Explorer configure AWS Config and Amazon CloudWatch events to automatically create OpsItems based on commonly\-used rules and events**\. If you don't choose this option, OpsCenter remains disabled\.
+**Note**  
+Amazon EventBridge \(formerly Amazon CloudWatch Events\) provides all functionality of CloudWatch Events and some new features, such as custom event buses, third\-party event sources and schema registry\.
+
+1. Choose **Enable OpsCenter**\.
+
+After you enable OpsCenter, you can do the following from **Settings**:
++ Create CloudWatch alarms using the **Open CloudWatch console** button\. For more information, see [Configure CloudWatch alarms to create OpsItems](OpsCenter-create-OpsItems-from-CloudWatch-Alarms.md)\.
++ Enable operational insights\. For more information, see [Analyzing operational insights to reduce duplicate OpsItems](OpsCenter-working-operational-insights.md)\.
++ Enable AWS Security Hub findings alarms\. For more information, see [Security Hub](OpsCenter-integrate-with-security-hub.md)\.
++ Enable or disable the default EventBridge rules and custom rules that you have created\. You can also edit the category and severity for default and custom EventBridge rules\. The following EventBridge rules are available by default: 
+  + **SSMOpsItems\-Autoscaling\-instance\-launch\-failure** – This rule creates OpsItems when the launch of the EC2 auto scaling instance is failed\. 
+  + **SSMOpsItems\-Autoscaling\-instance\-termination\-failure** – This rule creates OpsItems when the termination of the EC2 auto scaling instance is failed\.
+  + **SSMOpsItems\-EBS\-snapshot\-copy\-failed** – This rule creates OpsItems when the system failed to copy the Amazon Elastic Block Store \(Amazon EBS\) snapshot\. 
+  + **SSMOpsItems\-EBS\-snapshot\-creation\-failed** – This rule creates OpsItems when the system failed to create the Amazon EBS snapshot\.
+  + **SSMOpsItems\-EBS\-volume\-performance\-issue** – This rule creates OpsItems whenever there is a performance issue with Amazon EBS volume\. 
+  + **SSMOpsItems\-EC2\-issue** – This rule creates OpsItems whenever there is an issue with EC2 instances\.
+  + **SSMOpsItems\-EC2\-scheduled\-change** – This rule creates OpsItems for EC2 scheduled updates\.
+  + **SSMOpsItems\-RDS\-issue** – This rule creates OpsItems whenever there is an issue with Amazon Relational Database Service \(Amazon RDS\)\.
+  + **SSMOpsItems\-RDS\-scheduled\-change** – This rule creates OpsItems for Amazon RDS scheduled updates\.
+  + **SSMOpsItems\-SSM\-maintenance\-window\-execution\-failed** – This rule creates OpsItems when the execution of the Systems Managermaintenance window is failed\. 
+  + **SSMOpsItems\-SSM\-maintenance\-window\-execution\-timedout** – This rule creates OpsItems when the execution of the Systems Manager maintenance window is timeout\. 
+
+  You can choose a rule to view, edit, and manage in EventBridge\. For more information, see [Configure EventBridge rules to create OpsItems](OpsCenter-automatically-create-OpsItems-2.md)

doc_source/OpsCenter-setup.md

@@ -1,27 +1,7 @@
 # Set up OpsCenter<a name="OpsCenter-setup"></a>
 
-AWS Systems Manager uses an integrated setup experience to help you get started with OpsCenter and Explorer, which are capabilities of Systems Manager\. Explorer is a customizable operations dashboard that reports information about your AWS resources\. In this documentation, Explorer and OpsCenter setup is called *Integrated Setup*\.
+Set up OpsCenter, a capability of AWS Systems Manager, for your AWS Region\. Based on your requirements, you can set up OpsCenter by performing the following steps: 
 
-You must use Integrated Setup to set up OpsCenter with Explorer\. If you already set up OpsCenter, you still need to complete Integrated Setup to verify settings and options\. Integrated Setup is only available in the AWS Systems Manager console\. You can't set up Explorer and OpsCenter programmatically\. For more information, see [Getting started with Systems Manager Explorer and OpsCenter](Explorer-setup.md)\. 
+1. [Set up OpsCenter using the Integrated Setup experience ](OpsCenter-settingup.md) available for OpsCenter and Explorer\. 
 
-**To set up OpsCenter**
-
-1. Open the AWS Systems Manager console at [https://console\.aws\.amazon\.com/systems\-manager/](https://console.aws.amazon.com/systems-manager/)\.
-
-1. In the navigation pane, choose **OpsCenter**\.
-
-1. Choose **Enable OpsCenter**\.
-
-1. Choose **Enable this option to have Explorer configure AWS Config and Amazon CloudWatch events to automatically create OpsItems**\. If you don't choose this option, OpsCenter remains disabled\.
-**Note**  
-Amazon EventBridge \(formerly Amazon CloudWatch Events\) provides all functionality of CloudWatch Events and some new features, such as custom event buses, third\-party event sources and schema registry\.
-
-1. Choose **Enable OpsCenter**\.
-
-After you enable OpsCenter, you can do the following:
-+ Create CloudWatch alarms using the **Open CloudWatch console** button\. For more information, see [Configure CloudWatch alarms to create OpsItems](OpsCenter-create-OpsItems-from-CloudWatch-Alarms.md)\.
-+ Enable operational insights\. For more information, see [Analyzing operational insights to reduce duplicate OpsItems](OpsCenter-working-operational-insights.md)\.
-+ Enable AWS Security Hub findings alarms\. For more information, see [Security Hub](OpsCenter-integrate-with-security-hub.md)\.
-+ Edit the category, severity, and state of EventBridge rules\. You can choose a rule to view, edit, and manage in EventBridge\. For more information, see [Configure EventBridge rules to create OpsItems](OpsCenter-automatically-create-OpsItems-2.md)\.
-
-After you set up OpsCenter, you can decide if you want to use a central account to create and manage OpsItems for member accounts\. For more information, see [\(Optional\) Setting up OpsCenter to centrally manage OpsItems across accounts](OpsCenter-getting-started-multiple-accounts.md)\. 
+1. \(Optional\) [Set up OpsCenter to use a central account](OpsCenter-getting-started-multiple-accounts.md) to create and manage OpsItems for member accounts if needed\. 

doc_source/OpsCenter.md

@@ -16,7 +16,7 @@ You can view quotas for all Systems Manager capabilities in [Systems Manager ser
 
 To set up and work with OpsCenter to remediate OpsItems, perform the following steps:
 
-1. [Set up OpsCenter using Integrated Setup](OpsCenter-setup.md)\.
+1. [Set up OpsCenter using Integrated Setup](OpsCenter-setup.md)\. You can also [set up OpsCenter to centrally manage OpsItems across accounts ](OpsCenter-getting-started-multiple-accounts.md) if needed\. 
 
 1. [Integrate AWS services with OpsCenter](OpsCenter-applications-that-integrate.md)\. OpsCenter can integrate with Amazon CloudWatch, Amazon CloudWatch Application Insights, Amazon EventBridge, Amazon DevOps Guru, AWS Config, AWS Security Hub, and AWS Systems Manager Incident Manager\. 
 

doc_source/automation-action-executeAwsApi.md

@@ -1,6 +1,6 @@
 # `aws:executeAwsApi` – Call and run AWS API operations<a name="automation-action-executeAwsApi"></a>
 
-Calls and runs AWS API operations\. Most API operations are supported, although not all API operations have been tested\. Streaming API operations, such as the [GetObject](https://docs.aws.amazon.com/AmazonS3/latest/API/RESTObjectGET.html) operation, aren't supported\. If you're not sure if an API operation you want to use is a streaming operation, review the [Boto3](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/index.html) documentation for the service to determine if an API requires streaming inputs\. Each `aws:executeAwsApi` action can run up to a maximum duration of 25 seconds\. For more examples of how to use this action, see [Additional runbook examples](automation-document-examples.md)\.
+Calls and runs AWS API operations\. Most API operations are supported, although not all API operations have been tested\. Streaming API operations, such as the [GetObject](https://docs.aws.amazon.com/AmazonS3/latest/API/RESTObjectGET.html) operation, aren't supported\. If you're not sure if an API operation you want to use is a streaming operation, review the [Boto3](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/index.html) documentation for the service to determine if an API requires streaming inputs\. We regularly update the Boto3 version used by this action\. However, following the release of a new Boto3 version it can take up to a few weeks for changes to be reflected in this action\. Each `aws:executeAwsApi` action can run up to a maximum duration of 25 seconds\. For more examples of how to use this action, see [Additional runbook examples](automation-document-examples.md)\.
 
 **Inputs**  
 Inputs are defined by the API operation that you choose\. 

doc_source/automation-actions.md

@@ -45,6 +45,11 @@ If you run an automation workflow that invokes other services by using an AWS Id
 
 Common properties are parameters or options that are found in all actions\. Some options define behavior for a step, such as how long to wait for a step to complete and what to do if the step fails\. The following properties are common to all actions\.
 
+[description](#descriptProp)  
+Information you provide to describe the purpose of a runbook or a step\.  
+Type: String  
+Required: No
+
 [name](#nameProp)  
 An identifier that must be unique across all step names in the runbook\.  
 Type: String  

doc_source/getting-started-create-preferences-cli.md

@@ -1,13 +1,19 @@
-# Create Session Manager preferences \(command line\)<a name="getting-started-create-preferences-cli"></a>
+# Create a Session Manager preferences document \(command line\)<a name="getting-started-create-preferences-cli"></a>
 
-The following procedure describes how to use your preferred command line tool to create AWS Systems Manager Session Manager preferences for your AWS account in the selected AWS Region\. Use Session Manager preferences to specify options for logging session data in an Amazon Simple Storage Service \(Amazon S3\) bucket or Amazon CloudWatch Logs log group\. You can also use Session Manager preferences to encrypt your session data\.
+Use the following procedure to create SSM documents that define your preferences for AWS Systems Manager Session Manager sessions\. You can use the document to configure session options including data encryption, session duration, and logging\. For example, you can specify whether to store session log data in an Amazon Simple Storage Service \(Amazon S3\) bucket or Amazon CloudWatch Logs log group\. You can create documents that define general preferences for all sessions for an AWS account and AWS Region, or that define preferences for individual sessions\. 
 
-For information about using command line tools to update existing Session Manager preferences, see [Update Session Manager preferences \(command line\)](getting-started-configure-preferences-cli.md)\.
+**Note**  
+You can also configure general session preferences by using the Session Manager console\.
+
+Documents used to set Session Manager preferences must have a `sessionType` of `Standard_Stream`\. For more information about Session documents, see [Session document schema](session-manager-schema.md)\.
+
+For information about using the command line to update existing Session Manager preferences, see [Update Session Manager preferences \(command line\)](getting-started-configure-preferences-cli.md)\.
 
 For an example of how to create session preferences using AWS CloudFormation, see [Create a Systems Manager document for Session Manager preferences](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ssm-document.html#aws-resource-ssm-document--examples) in the *AWS CloudFormation User Guide*\.
 
 **Note**  
-You can use this procedure to create custom Session documents for your Session Manager preferences that override account level settings\. When you create your custom Session documents, specify a value other than `SSM-SessionManagerRunShell` for the name parameter and modify the inputs as needed\. To use your custom Session documents, you must provide the name of your custom Session document for the `--document-name` parameter when starting a session from the AWS Command Line Interface \(AWS CLI\)\. When you start a session from the console, you can't specify custom Session documents\.
+This procedure describes how to create documents for setting Session Manager preferences at the AWS account level\. To create documents that will be used for setting session\-level preferences, specify a value other than `SSM-SessionManagerRunShell` for the file name related command inputs \.   
+To use your document to set preferences for sessions started from the AWS Command Line Interface \(AWS CLI\), provide the document name as the `--document-name` parameter value\. To set preferences for sessions started from the Session Manager console, you can type or select the name of your document from a list\.
 
 **To create Session Manager preferences \(command line\)**