Skip to main content
Superlog connects to AWS through IAM roles you create with one CloudFormation stack. It uses short-lived credentials from STS. No AWS keys are stored.

What Superlog reads

The read-only role uses the AWS-managed AIOpsAssistantPolicy. It covers read access across the account, including:
  • CloudWatch alarms, alarm history, metrics, and Logs Insights.
  • Lambda configuration, SQS queues, and other resources.
An explicit deny blocks reading Secrets Manager values and SSM parameters, and decrypting with KMS.

Connect AWS

1

Open the AWS page

Open Setup → Sources, click Add source, and choose AWS CloudWatch.
2

Launch the stack

Click Launch stack in AWS and sign in to the account you want to connect. The stack opens with everything filled in. To review it first, click Download the template.
3

Create the stack

Check the box to allow IAM resources, then click Create stack. It usually finishes in about a minute.
4

Come back to Superlog

The page updates on its own. Superlog assumes the role once to check it works, then shows the account as connected.
In Integrations, Add on AWS asks for your 12-digit AWS account ID, opens the same template in CloudFormation, and connects when you click Verify connection.

What the stack creates

The stack creates IAM roles and nothing else: The stack has no Lambda functions, Firehose streams, or buckets, so it creates nothing that AWS bills. AWS bills the queries Superlog runs, such as Logs Insights queries, at its usual rates.

Send new errors to Superlog

After the account connects, choose the regions to read under Telemetry from. For each region, Superlog creates one account-level subscription policy, superlog-<region>, that sends error lines from every log group to Superlog. Superlog then sees each new error as it arrives. Without a region, Superlog reads CloudWatch only while it investigates. Removing a region or the connection deletes its policy.

How findings use AWS

  • New errors. Error lines from your chosen regions become error issues, and Superlog investigates new and regressed ones.
  • Investigations. Superlog reads CloudWatch logs, metrics, and alarms, and resource configuration, for evidence.

Automations

AWS does not send webhooks to Superlog. Send CloudWatch alarms to a Slack channel with Amazon Q Developer in chat applications. Then add a Slack New message in channel trigger on that channel, or mention Superlog in the alarm’s thread for tag mode. Superlog acts only on ALARM notifications.

Limits

  • AIOpsAssistantPolicy grants read access in every region of the account. Review the template before you create the stack.
  • CloudWatch Logs allows one account-level subscription policy per account and region. If a region already has one, Superlog cannot add its own there.
  • Only the commercial AWS partition is supported.
  • To stream CloudWatch metrics and all logs to Superlog for storage, see AWS CloudWatch telemetry.