convops
  • Features
  • How it works
  • Pricing
  • Blog
  • Security
Log inStart free →
convops

Root cause, not noise.

Start free →

Product

  • Features
  • How it works
  • Pricing
  • Blog
  • Security
  • Get started

Compare

  • Vs PagerDuty
  • Vs incident.io
  • Vs Datadog
  • Vs Resolve.ai
  • Vs Rootly
  • Vs Squadcast

Solutions

  • AWS incident response
  • CloudWatch alarm diagnosis
  • AWS alerts to WhatsApp
  • WhatsApp on-call
  • PagerDuty alternative

Connect

  • X (Twitter)
  • LinkedIn

© 2026 ConvOps. All rights reserved.

Built at 2am, for a 2am.

Home›Setup Guide

Setup Guide

Connect your AWS account to ConvOps in about 5 minutes from app.convops.io. No code changes, no agents, no email required.

1
Sign upapp.convops.io
2
Enter detailsAccount ID + channel
3
Deploy stackPre-filled, one click
4
VerifyPaste SNS ARN
✓
LiveFirst alert on WhatsApp
1
Sign up at app.convops.io
Create your account — takes 30 seconds.

Go to app.convops.io/sign-up. Enter your email and create a password. No credit card, no approval needed.

Create free account →
2
Connect your AWS account — enter details
Dashboard → "Connect AWS Account" → fill in Step 1 of 3.

The portal's first screen collects everything ConvOps needs. No YAML editing, no CLI yet.

app.convops.io/dashboard/connect
1
Details
2
Deploy
3
Verify
AWS Account ID
123456789012
Region
eu-central-1 (Frankfurt)
Environment
Production
Where should alerts go?
💬 WhatsApp
# Slack
🔔 Both
WhatsApp number
+49 151 12345678
Continue to deployment →
AWS Account ID — the 12-digit number from the top-right of your AWS console.
Alert channel — WhatsApp, Slack, or both. Enter your WhatsApp number if choosing WhatsApp. Slack connects after with one OAuth click.
Advanced options (optional) — enable remediation actions (restart/scale/reboot). Skip and add later.
3
Deploy the CloudFormation stack — one click
The portal generates a pre-filled URL. Click "Open AWS CloudFormation" and confirm.
app.convops.io/dashboard/connect
✓
Details
2
Deploy
3
Verify
Account123456789012
Regioneu-central-1
AccessRead-only
Everything is pre-filled. Just click the button below.
↗ Open AWS CloudFormation
Stack is deployed → Continue

Clicking “Open AWS CloudFormation” opens the AWS console with the stack pre-configured — your account ID, region, and CustomerExternalId are all filled in automatically. In the console you just:

  1. 1Review the parameters (pre-filled — nothing to change)
  2. 2Check “I acknowledge that AWS CloudFormation might create IAM resources with custom names”
  3. 3Click Create Stack — takes ~60 seconds
  4. 4Come back to the portal and click “Stack is deployed → Continue”
What the stack creates in your account:
  • › IAM Role (ConvOpsAccessRole) — read-only by default, protected by your unique ExternalId via STS.
  • › SNS Topic (ConvOpsAlerts) — receives CloudWatch alarm events and forwards to ConvOps.
  • › EventBridge Rule (ConvOpsAlarmStateChanges) — automatically routes every alarm state change in your account. No per-alarm wiring needed.
4
Verify the connection — paste your SNS Topic ARN
Back in the portal, Step 3 of 3. The only thing you copy-paste.
app.convops.io/dashboard/connect
✓
Details
✓
Deploy
3
Verify
SNS Topic ARN
arn:aws:sns:eu-central-1:123456789012:ConvOpsAlerts

Find this in CloudFormation → stack convops-setup → Outputs tab → SNSTopicArn

Verify & connect

Where to find the SNS Topic ARN:

  1. 1Go to AWS Console → CloudFormation
  2. 2Click the stack convops-setup
  3. 3Click the Outputs tab
  4. 4Copy the value next to SNSTopicArn
When you click Verify & connect, the portal calls the ConvOps API which confirms the SNS subscription and registers your workspace automatically. No email, no waiting, no manual step from ConvOps.
✓
You're live — activate your channels
The portal shows next steps after successful verification.
1
Activate WhatsApp

Send Hi to +4915511520510 on WhatsApp. This activates your number so alerts can be delivered. One-time setup.

2
Connect Slack (if you chose Slack)

The portal shows an “Add to Slack” button after verification. One OAuth click — ConvOps will DM you alerts and accept replies in Slack.

Add to Slack →
That's it. The next time any CloudWatch alarm in your account fires, ConvOps will receive it via EventBridge, run AI root cause analysis, and send you a message. Reply 4 to deep-dive or 1 + YES to take action.

What the CloudFormation stack creates in your AWS account

ResourceTypeWhat it does
ConvOpsAccessRoleIAM RoleLets ConvOps read your metrics + take approved actions. Protected by your unique ExternalId via STS.
ConvOpsAlertTopicSNS TopicReceives CloudWatch alarm events and forwards them to ConvOps via HTTPS subscription.
ConvOpsAlertTopicPolicySNS PolicyAuthorises CloudWatch and EventBridge to publish to the topic.
ConvOpsAlarmStateChangesEventBridge RuleAutomatic. Catches every ALARM + OK state change across your whole account. No per-alarm setup needed.

What ConvOps can and cannot do

ConvOps CAN
  • ✓Read CloudWatch metrics, alarms, logs (all resources)
  • ✓Restart / scale / rollback ECS services (if actions enabled)
  • ✓Reboot / stop-start EC2 (if actions enabled)
  • ✓Reboot / failover RDS / Aurora (if actions enabled)
  • ✓Throttle / rollback Lambda, scale EKS, redrive SQS DLQ (if actions enabled)
ConvOps CANNOT
  • ✗Terminate or delete any resource
  • ✗Modify security groups, VPCs, or IAM policies
  • ✗Access S3 or Secrets Manager
  • ✗Take any action without your explicit WhatsApp / Slack confirmation
  • ✗Act on anything if actions are not enabled

Troubleshooting

Verification failed in the portal?
The most common cause is pasting the wrong ARN. Make sure you're copying SNSTopicArn from the Outputs tab (not RoleArn). It should look like: arn:aws:sns:REGION:ACCOUNT_ID:ConvOpsAlerts
Not receiving alerts after setup?
  • ›Did you send “Hi” to +4915511520510 on WhatsApp? That activates your number for delivery.
  • ›Confirm EventBridge rule ConvOpsAlarmStateChanges is ENABLED in EventBridge → Rules
  • ›Check SNS → Subscriptions — the HTTPS subscription should show Confirmed
  • ›Test by temporarily lowering a CloudWatch alarm threshold to trigger it
CloudFormation deploy failed?
Your IAM user/role needs: cloudformation:*iam:CreateRoleiam:PutRolePolicyiam:AttachRolePolicysns:CreateTopicevents:PutRuleevents:PutTargets The checkbox for IAM resources must be ticked.
Action failed with permission denied?
Check that you enabled actions during setup (Advanced options → Allow ConvOps to take actions). If not, delete and redeploy the stack with that option checked, or update the stack's EnableActions parameter to true.
Still stuck?

Email us — we'll walk you through it. Usually responds within a few hours.

nitesh@convops.io
Create your free account →