Why should you care?

AwsVerse monitors golden signals (latency, traffic, errors, saturation) per banking API tier.

See it live — copy this example

Run in AWS CloudShell / local AWS CLI v2, or follow the matching steps in the AWS Console (Free Tier).

aws synthetics create-canary \
  --name awsverse-login-canary \
  --artifact-s3-location 's3://awsverse-synthetics-artifacts/canary/' \
  --execution-role-arn arn:aws:iam::123:role/CloudWatchSyntheticsRole \
  --schedule '{"Expression":"rate(5 minutes)"}' \
  --runtime-version syn-nodejs-puppeteer-9.0 \
  --code '{"Handler":"index.handler","Script":"const synthetics = require(\"Synthetics\"); exports.handler = async () => { await synthetics.executeStep(\"login\", async () => { /* navigate */ }); };"}'

What happened?

• CloudWatch Synthetics canary runs every five minutes simulating login.
• Failed runs trigger alarms before customers notice.

Practice next

1. Enable detailed monitoring on EC2 ASG.
2. Create canary for critical user journey.
3. Wire canary failure to SNS on-call topic.
4. Add Container Insights on EKS cluster.
5. Dashboard combining ALB and RDS metrics.

Remember

Combine metrics logs traces synthetics. Canaries test real user paths. Alert on symptoms users feel.

AwsVerse synthetic login

DNS change might break mobile login.

Outcome: Canary fails in Mumbai region; rollback before customer tickets.