Amazon CloudWatch Health Check

To add an Amazon CloudWatch monitor or alarm as a health check, you'll need three pieces of information:

The AWS integration requires the cloudwatch::DescribeAlarms permission when used with a Cloudwatch Healthcheck.

  1. Your AWS account ID.
  2. An AWS access key. If you need to create one, see Managing access keys for IAM users.
  3. The URL of the CloudWatch monitor or alarm you wish to use.

To add an Amazon CloudWatch health check:

  1. Open the Health Checks page in the Gremlin web app, click + Health Check, then select AWS from the Integrations drop-down.
  2. If you've already authenticated AWS, continue to step 3. Otherwise, follow these steps:
  3. ^Enter your AWS account ID in the appropriate text box.
  4. ^In the Authentication section, enter your AWS Access Key ID and AWS Secret Access Key in the respective boxes.
  5. ^You can optionally change the Authentication Endpoint, e.g. to test authenticating with a different AWS region. In most cases, you can leave this as the default.
  6. ^Click Authenticate Observability Tool. If the authentication passes, click Save Authentication. Otherwise, try changing your settings and retry authenticating.
  7. Click Next.
  8. Confirm that your newly added AWS account is selected in the Health Checks drop-down, then click Next.
  9. Select whether to use an Amazon CloudWatch alarm as the basis of the Health Check, or the AWS API. Using a CloudWatch alarm is the most straightforward and recommended method while using the API gives you more control.
  10. ^If you're using a CloudWatch alarm:
  11. ^Select Create a Health Check from an Amazon CloudWatch alarm URL.
  12. ^Enter the URL of the alarm. To get the URL, open the alarm (or monitor) in a web browser, then copy and paste the URL into the text box.
  13. ^Click Test Health Check to confirm that it works.
  14. ^If you're using the AWS API:
  15. ^Enter a name for the health check in the Health Check Name box.
  16. ^Enter the URL of the alarm. To get the URL, open the alarm (or monitor) in a web browser, then copy and paste the URL into the text box.
  17. ^Click Test Connection to confirm that the health check works. This also shows the response code and body, which you can use to adjust your success criteria.
  18. ^Adjust the Success Evaluation criteria to your needs. By default, Gremlin considers the check to be successful if it returns an HTTP 200 status code within 1000 milliseconds, and the .DescribeAlarmsResponse.DescribeAlarmsResult.MetricAlarms[0].StateValue field contains OK. You can change these values to fit your requirements or keep the defaults. Read adding success evaluation criteria for more information.
  19. ^Click Test Evaluation to send another test request to your endpoint. This is to ensure the response meets your criteria.
  20. Click Create Health Check.
No items found.
This is some text inside of a div block.
Installing the Gremlin Agent
Authenticating the Gremlin Agent
Configuring the Gremlin Agent
Managing the Gremlin Agent
User Management
Health Checks
Command Line Interface
Updating Gremlin
Quick Start Guide
Services and Dependencies
Detected Risks
Reliability Tests
Reliability Score
Deploying Failure Flags on AWS Lambda
Deploying Failure Flags on AWS ECS
Deploying Failure Flags on Kubernetes
Classes, methods, & attributes
API Keys
Container security
Additional Configuration for Helm
Amazon CloudWatch Health Check
AppDynamics Health Check
Application Level Fault Injection (ALFI)
Blackhole Experiment
CPU Experiment
Certificate Expiry
Custom Health Check
Custom Load Generator
DNS Experiment
Datadog Health Check
Disk Experiment
Dynatrace Health Check
Grafana Cloud Health Check
Grafana Cloud K6
IO Experiment
Install Gremlin on Kubernetes manually
Install Gremlin on OpenShift 4
Installing Gremlin on AWS - Configuring your VPC
Installing Gremlin on Kubernetes with Helm
Installing Gremlin on Windows
Installing Gremlin on a virtual machine
Installing the Failure Flags SDK
Latency Experiment
Memory Experiment
Network Tags
New Relic Health Check
Packet Loss Attack
PagerDuty Health Check
Preview: Gremlin in Kubernetes Restricted Networks
Private Network Integration Agent
Process Collection
Process Killer Experiment
Prometheus Health Check
Role Based Access Control
Running Failure Flags experiments
Scheduling Scenarios
Shared Scenarios
Shutdown Experiment
Time Travel Experiment
Troubleshooting Gremlin on OpenShift
User Authentication via SAML and Okta
Integration Agent for Linux
Test Suites
Restricting Testing Times
Enabling DNS collection