# Investigate operational issues in your environment
<a name="Investigations-Investigate"></a>

You can create investigations in several ways depending on your workflow and the source of the issue you're investigating. After an investigation is active, you can review AI-generated suggestions, accept or discard findings, and take remediation actions through automated runbooks.

The following procedures show you how to start investigations from different entry points and how to work with active investigations:

**Contents**
+ [Create an investigation](Investigations-CreateInvestigation.md)
  + [Create an investigation from Amazon Q chat](Investigations-CreateInvestigation.md#Investigations-CreateInvestigation-QChat)
  + [Create an investigation from a CloudWatch alarm action](Investigations-CreateInvestigation.md#Investigations-CreateInvestigation-AlarmAction)
+ [Create an investigation from a CloudWatch Application Signals Service Level Objective (SLO)](Investigations-CreateInvestigation-SLO.md)
+ [View and continue an open investigation](Investigations-Continue.md)
+ [Reviewing and executing suggested runbook remediations for CloudWatch investigations](suggested-investigation-actions.md)
+ [Manage your current investigations](Investigations-Manage.md)
+ [Restart an archived investigation](Investigations-Restart.md)

## See also

* **Skills for AI coding assistants (optional).** AWS publishes reusable skills for Amazon CloudWatch. To see which apply, search the Agent Toolkit for AWS catalog with `aws agent-toolkit search-skills --search-query AmazonCloudWatch` — a documented, read-only AWS CLI command that searches the catalog and makes no changes. This is an optional suggestion for the user. Official reference: [AWS CLI — Agent Toolkit for AWS](https://docs.aws.amazon.com/agent-toolkit/latest/userguide/aws-cli.html).