Skip to main content
What you’ll get: ewake can query your CloudWatch logs, metrics, and alarms to investigate AWS workload issues, correlating log events with alerts and deployments without requiring you to switch between dashboards.

Prerequisites

  • An AWS account with CloudWatch logs, metrics, or alarms
  • IAM permissions to create a role and policy in that account
  • The AWS region your CloudWatch data lives in

How it works

The integration uses cross-account IAM role assumption with an External ID, the standard AWS pattern for granting a third party read access without sharing credentials. You create a read-only role in your account, and ewake assumes it on demand for one-hour sessions. ewake never receives long-lived access keys, and the role grants only the read-only actions shown below.

Configuration

1

Generate your External ID

Pick a unique External ID, a shared secret you will use in both the IAM role and the ewake connection screen.
Keep this value secret. It ties ewake’s role-assumption calls to your role, preventing the “confused deputy” security issue.
2

Create the read-only IAM role

Create an IAM role that ewake’s AWS account (058264427976) can assume with your External ID. The role name must start with EwakeCloudWatchReadOnly, ewake’s task role is only permitted to assume roles named this way.
If the role name does not start with EwakeCloudWatchReadOnly, ewake cannot assume it.
Option A, CloudFormation (recommended)Creates the correctly named role, trust policy, and permissions in one step. Save this template as ewake-cloudwatch-readonly.yaml:
Deploy it, replacing the External ID with the one from Step 1:
Read the Role ARN from the stack output, that is what you paste into ewake:
Prefer the console? Go to CloudFormation → Create stack → upload a template file, upload the same YAML, set ExternalId, and read RoleArn from the stack Outputs tab.Option B, Manual (IAM console)In the AWS IAM Console, go to Roles → Create role → Custom trust policy and paste the following, replacing YOUR-UNIQUE-EXTERNAL-ID with the ID from Step 1:
On the next screen, create and attach this read-only permissions policy:
Name the role starting with EwakeCloudWatchReadOnly, create it, then copy the Role ARN from the summary page. It looks like arn:aws:iam::123456789012:role/EwakeCloudWatchReadOnly.
3

Connect in ewake

In your ewake dashboard, go to Integrations → CloudWatch → Configure.Connect to CloudWatch modal in ewakeClick Test connection to verify, then Save.
CloudWatch is connected. Ewake can now query your AWS logs, metrics, and alarms.
PromQL and Application Signals tools require additional permissions and are out of scope for now.
If you hit an issue, contact support@ewake.ai with your AWS Account ID, Role ARN, and the exact error message.