• The AWS Systems Manager CloudWatch Dashboard will no longer be available after April 30, 2026. Customers can continue to use Amazon CloudWatch console to view, create, and manage their Amazon CloudWatch dashboards, just as they do today. For more information, see [Amazon CloudWatch Dashboard documentation](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch_Dashboards.html).
# Manage OpsItems
OpsCenter, a tool in AWS Systems Manager, tracks OpsItems from their creation to resolution. If you set up OpsCenter for cross-account administration, a delegated administrator or management account can manage OpsItems from their account. For more information, see [(Optional) Manually set up OpsCenter to centrally manage OpsItems across accounts](OpsCenter-getting-started-multiple-accounts.md).
You can view and manage OpsItems by using the following pages in the Systems Manager console:
+ **Summary** – Displays a count of open and in-progress OpsItems, count of OpsItems by source and age, and operational insights. You can filter OpsItems by source and OpsItems status.
+ **OpsItems** – Displays a list of OpsItems with multiple fields of information, such as title, ID, priority, description, the source of the OpsItem, and the date and time of last update. Using this page, you can manually create OpsItems, configure sources, change the status of an OpsItem, and filter OpsItems by new incidents. You can choose an OpsItem to display its **OpsItems details** page.
+ **OpsItem details** – Provides detailed insights and tools that you can use to manage an OpsItem. The OpsItems details page has the following tabs:
+ **Overview** – Displays related resources, runbooks that ran in the last 30 days, and a list of available runbooks that you can run. You can also view similar OpsItems, add operational data, and add related OpsItems.
+ **Related resource details** – Displays information about the resource from several AWS services. Expand the **Resource details** section to view information about this resource as provided by the AWS service that hosts it. You can also toggle through other related resources associated with this OpsItem by using the **Related resources** list.
For more information about how to manage OpsItems, see the following topics.
**Topics**
+ [
# Viewing details of an OpsItem
](OpsCenter-working-with-OpsItems-viewing-details.md)
+ [
# Editing an OpsItem
](OpsCenter-working-with-OpsItems-editing-details.md)
+ [
# Adding related resources to an OpsItem
](OpsCenter-working-with-OpsItems-adding-related-resources.md)
+ [
# Adding related OpsItems to an OpsItem
](OpsCenter-working-with-OpsItems-adding-related-OpsItems.md)
+ [
# Adding operational data to an OpsItem
](OpsCenter-working-with-OpsItems-adding-operational-data.md)
+ [
# Creating an incident for an OpsItem
](OpsCenter-working-with-OpsItems-create-an-incident.md)
+ [
# Managing duplicate OpsItems
](OpsCenter-working-deduplication.md)
+ [
# Analyzing operational insights to reduce OpsItems
](OpsCenter-working-operational-insights.md)
+ [
# Viewing OpsCenter logs and reports
](OpsCenter-logging-auditing.md)
# Viewing details of an OpsItem
Viewing details
To get a comprehensive view of an OpsItem, use the **OpsItem details** page in the OpsCenter console. The **Overview** page displays the following information:
+ **OpsItems details**– Displays general information for the selected OpsItem.
+ **Related Resources** – A related resource is the impacted resource or the resource that initiated the event that created the OpsItem.
+ **Automation executions in the last 30 days ** – A list of runbooks that ran in last 30 days.
+ **Runbooks** – You can choose a runbook from a list of available runbooks.
+ **Similar OpsItems** – This is a system-generated list of OpsItems that might be related or of interest to you. To generate the list, the system scans the titles and descriptions of all OpsItems and returns OpsItems that use similar words.
+ **Operational data** – Operational data is custom data that provides useful reference details about the OpsItem. For example, you can specify log files, error strings, license keys, troubleshooting tips, or other relevant data.
+ **Related OpsItems** – You can specify the IDs of OpsItems that are in some way related to the current OpsItem.
+ **Related Resource Details** – Displays data providers, including Amazon CloudWatch metrics and alarms, AWS CloudTrail logs, and details from AWS Config.
**To view details of an OpsItem**
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 an OpsItem to view its details.
# Editing an OpsItem
Editing an OpsItem
The **OpsItem details** section includes information about an OpsItem,
including the description, title, source, OpsItem ID, and the status.
You can edit a single OpsItem or you can select multiple OpsItems and edit the
following fields: **Status**, **Priority**,
**Severity**, **Category**.
When Amazon EventBridge creates an OpsItem, it populates the **Title**, **Source**, and **Description** fields. You can edit the **Title** and **Description** fields, but you can't edit the **Source** field.
**Note**
The console supports most markdown formatting in the OpsItem description field. For more information, see [Using Markdown in the Console](https://docs.aws.amazon.com/awsconsolehelpdocs/latest/gsg/aws-markdown.html) in the *Getting Started with the AWS Management Console Getting Started Guide.*
Generally, you can edit the following configurable data for an OpsItem:
+ **Title** – Name of the OpsItem. The source creates the title of the OpsItem.
+ **Description** – Information about this OpsItem including (if applicable) steps for reproducing the issue.
+ **Status** – Status of an OpsItem. For a list of valid status values, see [OpsItem Status](https://docs.aws.amazon.com/systems-manager/latest/APIReference/API_OpsItem.html#systemsmanager-Type-OpsItem-Status) in the *AWS Systems Manager API Reference*.
+ **Priority** – Priority of an OpsItem can be between 1 and 5. We recommend that your organization determine what each priority level means and a corresponding service level agreement for each level.
+ **Severity** – Severity of an OpsItem can be between 1 to 4, where 1 is critical, 2 is high, 3 is medium, and 4 is low.
+ **Category** – Category of an OpsItem can be availability, cost, performance, recovery, or security.
+ **Notifications** – When you edit an OpsItem, you can specify the Amazon Resource Name (ARN) of an Amazon Simple Notification Service topic in the **Notifications** field. By specifying an ARN, you ensure that all stakeholders receive a notification when the OpsItem is edited, including a status change. For more information, see the [https://docs.aws.amazon.com/sns/latest/dg/](https://docs.aws.amazon.com/sns/latest/dg/).
**Important**
The Amazon SNS topic must exist in the same AWS Region as the OpsItem. If the topic and the OpsItem are in different Regions, the system returns an error.
OpsCenter has bidirectional integration with AWS Security Hub CSPM. When you update an OpsItem status and severity related to a security finding, those changes are automatically sent to Security Hub CSPM to ensure you always see the latest and correct information.
When an OpsItem is created from a Security Hub CSPM finding, Security Hub CSPM metadata is automatically added to the operational data field of the OpsItem. If this metadata is deleted, the bidirectional updates no longer function.
**To edit OpsItem details**
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 an OpsItem ID to open the details page or choose multiple OpsItems. If you choose multiple OpsItems, you can only edit the status, priority, severity, or category. If you edit multiple OpsItems, OpsCenter updates and saves your changes as soon as you choose the new status, priority, severity, or category.
1. In the **OpsItem details** section, choose **Edit**.
1. Edit the details of the OpsItem according to the requirements and guidelines specified by your organization.
1. When you're finished, choose **Save**.
# Adding related resources to an OpsItem
Adding related resources
Each OpsItem includes a **Related resources** section that lists the Amazon Resource Name (ARN) of the related resource. A *related resource* is the impacted AWS resource that needs to be investigated.
If Amazon EventBridge creates the OpsItem, the system automatically populates the OpsItem with the ARN of the resource. You can manually specify ARNs of related resources. For certain ARN types, OpsCenter automatically creates a deep link that displays details about the resource directly in the OpsCenter console. For example, if you specify the ARN of an Amazon Elastic Compute Cloud (Amazon EC2) instance as a related resource, then OpsCenter pulls in details about that EC2 instance. This allows you to view detailed information about your impacted AWS resources without having to leave OpsCenter.
**To view and add related resources to an OpsItem**
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 the **OpsItems** tab.
1. Choose an OpsItem ID.
![\[A new OpsItem on the OpsCenter Overview page.\]](http://docs.aws.amazon.com/systems-manager/latest/userguide/images/OpsItems_working_scenario_1.png)
1. To view information about the impacted resource, choose the **Related resources details** tab.
![\[Viewing the Related resource details tab for an OpsItem.\]](http://docs.aws.amazon.com/systems-manager/latest/userguide/images/OpsItems_working_scenario_1_5.png)
This tab displays information about the resource from several AWS services. Expand the **Resource details** section to view information about this resource as provided by the AWS service that hosts it. You can also toggle through other related resources associated with this OpsItem by using the **Related resources** list.
1. To add additional related resources, choose the **Overview** tab.
1. In the **Related resources** section, choose **Add**.
1. For **Resource type**, choose a resource from the list.
1. For **Resource ID**, enter either the ID or the Amazon Resource Name (ARN). The type of information you choose depends on the resource that you chose in the previous step.
**Note**
You can manually add the ARNs of additional related resources. Each OpsItem can list a maximum of 100 related resource ARNs.
The following table lists the resource types that automatically create deep links to related resources.
**Supported resource types**
| Resource name | ARN format |
| --- | --- |
| AWS Certificate Manager certificate | arn:aws:acm:region:account-id:certificate/certificate-id
|
| Amazon EC2 Auto Scaling group | arn:aws:autoscaling:region:account-id:autoScalingGroup:groupid:autoScalingGroupName/groupfriendlyname
|
| Amazon CloudFront distribution | arn:aws:cloudfront::account-id:*
|
| AWS CloudFormation stack | arn:aws:cloudformation:region:account-id:stack/stackname/additionalidentifier
|
| Amazon CloudWatch alarm | arn:aws:cloudwatch:region:account-id:alarm:alarm-name
|
| AWS CloudTrail trail | arn:aws:cloudtrail:region:account-id:trail/trailname
|
| AWS CodeBuild project | arn:aws:codebuild:region:account-id:resourcetype/resource
|
| AWS CodePipeline | arn:aws:codepipeline:region:account-id:resource-specifier
|
| Amazon DevOps Guru insight | arn:aws:devops-guru:region:account-id:insight/proactive or reactive/resource-id
|
| Amazon DynamoDB table | arn:aws:dynamodb:region:account-id:table/tablename
|
| Amazon Elastic Compute Cloud (Amazon EC2) customer gateway | arn:aws:ec2:region:account-id:customer-gateway/cgw-id
|
| Amazon EC2 elastic IP | arn:aws:ec2:region:account-id:eip/eipalloc-id
|
| Amazon EC2 Dedicated Host | arn:aws:ec2:region:account-id:dedicated-host/host-id
|
| Amazon EC2 instance | arn:aws:ec2:region:account-id:instance/instance-id
|
| Amazon EC2 internet gateway | arn:aws:ec2:region:account-id:internet-gateway/igw-id
|
| Amazon EC2 network access control list (network ACL) | arn:aws:ec2:region:account-id:network-acl/nacl-id
|
| Amazon EC2 network interface | arn:aws:ec2:region:account-id:network-interface/eni-id
|
| Amazon EC2 route table | arn:aws:ec2:region:account-id:route-table/route-table-id
|
| Amazon EC2 security group | arn:aws:ec2:region:account-id:security-group/security-group-id
|
| Amazon EC2 subnet | arn:aws:ec2:region:account-id:subnet/subnet-id
|
| Amazon EC2 volume | arn:aws:ec2:region:account-id:volume/volume-id
|
| Amazon EC2 VPC | arn:aws:ec2:region:account-id:vpc/vpc-id
|
| Amazon EC2 VPN connection | arn:aws:ec2:region:account-id:vpn-connection/vpn-id
|
| Amazon EC2 VPN gateway | arn:aws:ec2:region:account-id:vpn-gateway/vgw-id
|
| AWS Elastic Beanstalk application | arn:aws:elasticbeanstalk:region:account-id:application/applicationname
|
| Elastic Load Balancing (Classic Load Balancer) | arn:aws:elasticloadbalancing:region:account-id:loadbalancer/name
|
| Elastic Load Balancing (Application Load Balancer) | arn:aws:elasticloadbalancing:region:account-id:loadbalancer/app/load-balancer-name/load-balancer-id
|
| Elastic Load Balancing (Network Load Balancer) | arn:aws:elasticloadbalancing:region:account-id:loadbalancer/net/load-balancer-name/load-balancer-id
|
| AWS Identity and Access Management (IAM) group | arn:aws:iam::account-id:group/group-name
|
| IAM policy | arn:aws:iam::account-id:policy/policy-name
|
| IAM role | arn:aws:iam::account-id:role/role-name
|
| IAM user | arn:aws:iam::account-id:user/user-name
|
| AWS Lambda function | arn:aws:lambda:region:account-id:function:function-name
|
| Amazon Relational Database Service (Amazon RDS) cluster | arn:aws:rds:region:account-id:cluster:db-cluster-name
|
| Amazon RDS database instance | arn:aws:rds:region:account-id:db:db-instance-name
|
| Amazon RDS subscription | arn:aws:rds:region:account-id:es:subscription-name
|
| Amazon RDS security group | arn:aws:rds:region:account-id:secgrp:security-group-name
|
| Amazon RDS cluster snapshot | arn:aws:rds:region:account-id:cluster-snapshot:cluster-snapshot-name
|
| Amazon RDS subnet group | arn:aws:rds:region:account-id:subgrp:subnet-group-name
|
| Amazon Redshift cluster | arn:aws:redshift:region:account-id:cluster:cluster-name
|
| Amazon Redshift parameter group | arn:aws:redshift:region:account-id:parametergroup:parameter-group-name
|
| Amazon Redshift security group | arn:aws:redshift:region:account-id:securitygroup:security-group-name
|
| Amazon Redshift cluster snapshot | arn:aws:redshift:region:account-id:snapshot:cluster-name/snapshot-name
|
| Amazon Redshift subnet group | arn:aws:redshift:region:account-id:subnetgroup:subnet-group-name
|
| Amazon Simple Storage Service (Amazon S3) bucket | arn:aws:s3:::bucket_name
|
| AWS Config recording of AWS Systems Manager managed node inventory | arn:aws:ssm:region:account-id:managed-instance-inventory/node_id
|
| Systems Manager State Manager association | arn:aws:ssm:region:account-id:association/association_ID
|
# Adding related OpsItems to an OpsItem
Adding related OpsItems
By using **Related OpsItems** of the **OpsItems Details** page, you can investigate operations issues and provide context for an issue. OpsItems can be related in different ways, including a parent-child relationship between OpsItems, a root cause, or a duplicate. You can associate one OpsItem with another to display it in the **Related OpsItem** section.You can specify a maximum of 10 IDs for other OpsItems that are related to the current OpsItem.
![\[Viewing related OpsItems.\]](http://docs.aws.amazon.com/systems-manager/latest/userguide/images/OpsItems_working_scenario_4.png)
**To add a related OpsItem**
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 an OpsItem ID to open the details page.
1. In the **Related OpsItem** section, choose **Add**.
1. For **OpsItem ID**, specify an ID.
1. Choose **Add**.
# Adding operational data to an OpsItem
Adding operational data
Operational data is custom data that provides useful reference details about an OpsItem. You can enter multiple key-value pairs of operational data. For example, you can specify log files, error strings, license keys, troubleshooting tips, or other relevant data. The maximum length of the key can be 128 characters, and the maximum size of the value can be 20 KB.
![\[Viewing operational data for an OpsItem.\]](http://docs.aws.amazon.com/systems-manager/latest/userguide/images/OpsItems_working_scenario_7.png)
You can make the data searchable by other users in the account, or you can restrict search access. Searchable data means that all users with access to the OpsItem **Overview** page (as provided by the [DescribeOpsItems](https://docs.aws.amazon.com/systems-manager/latest/APIReference/API_DescribeOpsItems.html) API operation) can view and search on the specified data. Operational data that isn't searchable is only viewable by users who have access to the OpsItem (as provided by the [GetOpsItem](https://docs.aws.amazon.com/systems-manager/latest/APIReference/API_GetOpsItem.html) API operation).
**To add operational data to an OpsItem**
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 an OpsItem ID to open its details page.
1. Expand **Operational data**.
1. If no operational data exists for the OpsItem, choose **Add**. If operational data already exists for the OpsItem, choose **Manage**.
After you create operational data, you can edit the key and the value, remove the operational data, or add additional key-value pairs by choosing **Manage**.
1. For **Key**, specify a word or words to help users understand the purpose of the data.
**Important**
Operational data keys *can't* begin with the following: `amazon`, `aws`, `amzn`, `ssm`, `/amazon`, `/aws`, `/amzn`, `/ssm`.
1. For **Value**, specify the data.
1. Choose **Save**.
**Note**
You can filter OpsItems by using the **Operational data** operator on the **OpsItems** page. In the **Search** box, choose **Operational data**, and then enter a key-value pair in JSON. You must enter the key-value pair by using the following format: `{"key":"key_name","value":"a_value"}`
# Creating an incident for an OpsItem
Creating an incident
Use the following procedure to manually create an incident for an OpsItem to track and manage it in AWS Systems Manager Incident Manager, which is a tool in AWS Systems Manager. An *incident* is any unplanned interruption or reduction in quality of services. For more information about Incident Manager, see [Integrate OpsCenter with other AWS services](OpsCenter-applications-that-integrate.md).
**To manually create an incident for an OpsItem**
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. If Incident Manager created an OpsItem for you, choose it and go to step 5. If not, choose **Create OpsItem** and complete the form. If you don't see this button, choose the **OpsItems** tab, and then choose **Create OpsItem**.
1. If you created an OpsItem, open it.
1. Choose **Start Incident**.
1. For **Response plan**, choose the Incident Manager response plan that you want to assign to this incident.
1. (Optional) For **Title**, enter a descriptive name to help other team members understand the nature of the incident. If you don't enter a new title, OpsCenter creates the OpsItem and the corresponding incident in Incident Manager using the title in the response plan.
1. (Optional) For **Incident impact**, choose an impact level for this incident. If you don't choose an impact level, OpsCenter creates the OpsItem and the corresponding incident in Incident Manager using the impact level in the response plan.
1. Choose **Start**.
# Managing duplicate OpsItems
OpsCenter can receive multiple duplicate OpsItems for a single source from multiple AWS services. OpsCenter uses a combination of built-in logic and configurable deduplication strings to avoid creating duplicate OpsItems. AWS Systems Manager applies deduplication built-in logic when the [CreateOpsItem](https://docs.aws.amazon.com/systems-manager/latest/APIReference/API_CreateOpsItem.html) API operation is called.
AWS Systems Manager uses the following deduplication logic:
1. When creating the OpsItem, Systems Manager creates and stores a hash based on the deduplication string and the resource that initiated the OpsItem.
1. When another request is made to create an OpsItem, the system checks the deduplication string of the new request.
1. If a matching hash exists for this deduplication string, Systems Manager checks the status of the existing OpsItem. If the status of an existing OpsItem is open or in progress, the OpsItem is not created. If the existing OpsItem is resolved, Systems Manager creates a new OpsItem.
After you create an OpsItem, you *can't* edit or change the deduplication strings in that OpsItem.
To manage duplicate OpsItems, you can do the following:
+ Edit the deduplication string for an Amazon EventBridge rule that targets OpsCenter. For more information, see [Editing a deduplication string in a default EventBridge rule](#OpsCenter-working-deduplication-editing-cwe).
+ Specify a deduplication string when you manually create an OpsItem. For more information, see [Specifying a deduplication string using AWS CLI](#OpsCenter-working-deduplication-configuring-manual-cli).
+ Review and resolve duplicate OpsItems using operational insights. You can use runbooks to resolve duplicate OpsItems.
To help you resolve duplicate OpsItems and reduce the number of OpsItems created by a source, Systems Manager provides automation runbooks. For information, see [Resolving duplicate OpsItems based on insights](OpsCenter-working-operational-insights.md#OpsCenter-working-operational-insights-resolve).
## Editing a deduplication string in a default EventBridge rule
Use the following procedure to specify a deduplication string for an EventBridge rule that targets OpsCenter.
**To edit a deduplication string for an EventBridge rule**
1. Sign in to the AWS Management Console and open the Amazon EventBridge console at [https://console.aws.amazon.com/events/](https://console.aws.amazon.com/events/).
1. In the navigation pane, choose **Rules**.
1. Choose a rule, and then choose **Edit**.
1. Go to the **Select target(s)** page.
1. In the **Additional settings** section, choose **Configure input transformer**.
1. In the **Template** box, locate the `"operationalData": { "/aws/dedup"` JSON entry and the deduplication strings that you want to edit.
The deduplication string entry in EventBridge rules uses the following JSON format.
```
"operationalData": { "/aws/dedup": {"type": "SearchableString","value": "{\"dedupString\":\"Words the system should use to check for duplicate OpsItems\"}"}}
```
Here is an example.
```
"operationalData": { "/aws/dedup": {"type": "SearchableString","value": "{\"dedupString\":\"SSMOpsCenter-EBS-volume-performance-issue\"}"}}
```
1. Edit the deduplication strings, and then choose **Confirm**.
1. Choose **Next**.
1. Choose **Next**.
1. Choose **Update rule**.
## Specifying a deduplication string using AWS CLI
You can specify a deduplication string when you manually create a new OpsItem by using either the AWS Systems Manager console or the AWS CLI. For information about entering deduplication strings when you manually create an OpsItem in the console, see [Create OpsItems manually](OpsCenter-manually-create-OpsItems.md). If you're using the AWS CLI, you can enter the deduplication string for the `OperationalData` parameter. The parameter syntax uses JSON, as shown in the following example.
```
--operational-data '{"/aws/dedup":{"Value":"{\"dedupString\": \"Words the system should use to check for duplicate OpsItems\"}","Type":"SearchableString"}}'
```
Here is an example command that specifies a deduplication string of `disk full`.
------
#### [ Linux & macOS ]
```
aws ssm create-ops-item \
--title "EC2 instance disk full" \
--description "Log clean up may have failed which caused the disk to be full" \
--priority 1 \
--source ec2 \
--operational-data '{"/aws/dedup":{"Value":"{\"dedupString\": \"disk full\"}","Type":"SearchableString"}}' \
--tags "Key=EC2,Value=ProductionServers" \
--notifications Arn="arn:aws:sns:us-west-1:12345678:TestUser"
```
------
#### [ Windows ]
```
aws ssm create-ops-item ^
--title "EC2 instance disk full" ^
--description "Log clean up may have failed which caused the disk to be full" ^
--priority 1 ^
--source EC2 ^
--operational-data={\"/aws/dedup\":{\"Value\":\"{\\"""dedupString\\""":\\"""disk full\\"""}\",\"Type\":\"SearchableString\"}} ^
--tags "Key=EC2,Value=ProductionServers" --notifications Arn="arn:aws:sns:us-west-1:12345678:TestUser"
```
------
# Analyzing operational insights to reduce OpsItems
Analyzing insights
OpsCenter *operational insights* display information about duplicate OpsItems. OpsCenter automatically analyzes OpsItems in your account and generates three types of *insights*. You can view this information in the **Operational insights** section of the OpsCenter **Summary** tab.
+ **Duplicate OpsItems** – An insight is generated when eight or more OpsItems have the same title for the same resource.
+ **Most common titles** – An insight is generated when more than 50 OpsItems have the same title.
+ **Resources generating the most OpsItems** – An insight is generated when an AWS resource has more than 10 open OpsItems. These insights and their corresponding resources are displayed in the **Resources generating the most OpsItems** table on the OpsCenter **Summary** tab. Resources are listed in decreasing order of OpsItem count.
**Note**
OpsCenter creates **Resources generating the most OpsItems** insights for the following resource types:
Amazon Elastic Compute Cloud (Amazon EC2) instances
Amazon EC2 security groups
Amazon EC2 Auto Scaling group
Amazon Relational Database Service (Amazon RDS) database
Amazon RDS cluster
AWS Lambda function
Amazon DynamoDB table
Elastic Load Balancing load balancer
Amazon Redshift cluster
AWS Certificate Manager certificate
Amazon Elastic Block Store volume
OpsCenter enforces a limit of 15 insights per type. If a type reaches this limit, OpsCenter stops displaying more insights for that type. To view additional insights, you must resolve all OpsItems associated with an OpsInsight of that type. If a pending insight is prevented from being displayed in the console because of the 15-insight limit, that insight becomes visible after another insight is closed.
When you choose an insight, OpsCenter displays information about the affected OpsItems and resources. The following screenshot shows an example with the details of a duplicate OpsItem insight.
![\[Detailed view of an OpsCenter insight with information about OpsItems.\]](http://docs.aws.amazon.com/systems-manager/latest/userguide/images/OpsCenter-insights-detailed.png)
Operational insights are turned off by default. For more information about working with operational insights, see the following topics.
**Topics**
+ [
## Enabling operational insights
](#OpsCenter-working-operational-insights-viewing)
+ [
## Resolving duplicate OpsItems based on insights
](#OpsCenter-working-operational-insights-resolve)
+ [
## Disabling operational insights
](#OpsCenter-working-operational-insights-disable)
## Enabling operational insights
You can enable operational insights on the **OpsCenter** page in the Systems Manager console. When you enable operational insights, Systems Manager creates an AWS Identity and Access Management (IAM) service-linked role called `AWSServiceRoleForAmazonSSM_OpsInsights`. A service-linked role is a unique type of IAM role that is linked directly to Systems Manager. Service-linked roles are predefined and include all the permissions that the service requires to call other AWS services on your behalf. For more information about the `AWSServiceRoleForAmazonSSM_OpsInsights` service-linked role, see [Using roles to create operational insight OpsItems in Systems Manager OpsCenter](using-service-linked-roles-service-action-4.md).
**Note**
Note the following important information:
Your AWS account is charged for operational insights. For more information, see [AWS Systems Manager Pricing](https://aws.amazon.com/systems-manager/pricing/).
OpsCenter periodically refreshes insights using a batch process. This means the list of insights displayed in OpsCenter might be out of sync.
Use the following procedure to enable and view operational insights in OpsCenter.
**To enable and view operational insights**
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. In the **Operational insight is available** message box, choose **Enable**. If you don't see this message, scroll down to the **Operational insights** section and choose **Enable**.
1. After you enable this feature, on the **Summary** tab, scroll down to the **Operational insights** section.
1. To view a filtered list of insights, choose the link beside **Duplicate OpsItems**, **Most common titles**, or **Resources generating the most OpsItems**. To view all insights, choose **View all operational insights**.
1. Choose an insight ID to view more information.
## Resolving duplicate OpsItems based on insights
To resolve insights, you must first resolve all OpsItems associated with an insight. You can use the `AWS-BulkResolveOpsItemsForInsight` runbook to resolve OpsItems associated with an insight.
To help you resolve duplicate OpsItems and reduce the number of OpsItems created by a source, Systems Manager provides the following automation runbooks:
+ The `AWS-BulkResolveOpsItems` runbook resolves OpsItems that match a specified filter.
+ The `AWS-AddOpsItemDedupStringToEventBridgeRule` runbook adds a deduplication string for all OpsItem targets that are associated with a specific Amazon EventBridge rule. This runbook doesn't add a deduplication string if a rule already has one.
+ The `AWS-DisableEventBridgeRule` turns off a rule in EventBridge if the rule is generating dozens or hundreds of OpsItems.
**To resolve an operational insight**
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 **Overview** tab, scroll down to **Operational insights**.
1. Choose **View all operational insights**.
1. Choose an insight ID to view more information.
1. Choose a runbook and choose **Execute**.
## Disabling operational insights
When you turn off operational insights, the system stops creating new insights and stops displaying insights in the console. Any active insights remain unchanged in the system, although you won't see them displayed in the console. If you enable this feature again, the system displays previously unresolved insights and starts creating new insights. Use the following procedure to turn off operational insights.
**To turn off operational insights**
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 **Settings**.
1. In the **Operational insights** section, choose **Edit** and then toggle the **Disable** option.
1. Choose **Save**.
# Viewing OpsCenter logs and reports
AWS CloudTrail logs AWS Systems Manager OpsCenter API calls to the console, the AWS Command Line Interface (AWS CLI), and the SDK. You can view the information in the CloudTrail console or in an Amazon Simple Storage Service (Amazon S3) bucket. Amazon S3 uses one bucket to store all CloudTrail logs for your account.
Logs of OpsCenter actions show create, update, get, and describe OpsItem activities. For more information about viewing and using CloudTrail logs of Systems Manager activity, see [Logging AWS Systems Manager API calls with AWS CloudTrail](monitoring-cloudtrail-logs.md).
AWS Systems Manager OpsCenter provides you with the following information about OpsItems:
+ **OpsItem status summary** – Provides a summary of OpsItems by status (Open and In progress, Open, or In Progress).
+ **Sources with most open OpsItems** – Provides a breakdown of the top AWS services with open OpsItems.
+ **OpsItems by source and age** – Provides a count of OpsItems, grouped by source and days since creation.
**To view the OpsCenter summary report**
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 OpsItems **Overview** page, choose **Summary**.
1. Under **OpsItems by source and age**, choose the Search bar to filter OpsItems according to **Source**. Use the list to filter according to **Status**.