All Integrations
CloudCloudWatch Metric Streams + IAM

AWS App Runner Integration

Monitor service request metrics, auto-scaling events, and deployment status tracking for your App Runner services. Get AI-powered deployment regression detection and cold start latency analysis.

Setup

How It Works

01

Create IAM Role for Metric Streams

Provision an IAM role with CloudWatch permissions scoped to the AWS/AppRunner namespace. TigerOps uses this role to deliver App Runner metrics via Kinesis Firehose.

02

Deploy CloudWatch Metric Streams

Run the TigerOps CloudFormation stack to stream the AWS/AppRunner namespace to your TigerOps endpoint. Request counts, latency, and instance metrics begin flowing immediately.

03

Configure Deployment Event Tracking

Enable App Runner EventBridge deployment notifications. TigerOps captures deployment start, success, and failure events and annotates your metrics timeline automatically.

04

Set Auto-Scaling and Error Alerts

Define SLOs on request latency and HTTP 5xx error rates. TigerOps fires predictive alerts when error rates trend upward and correlates spikes with recent deployments.

Capabilities

What You Get Out of the Box

Request Metrics

Total request count, active requests, 2xx/4xx/5xx response counts, and request latency per App Runner service. Understand traffic patterns and error rate baselines.

Auto-Scaling Event Visibility

Track instance count changes driven by App Runner auto-scaling. See when scale-out events happen relative to request volume increases and measure scale latency.

Deployment Status Tracking

Real-time deployment status for all App Runner services including in-progress, successful, and failed deployments. Correlate deployments with metric changes automatically.

CPU & Memory Utilization

Per-service CPU and memory utilization across all running instances. Identify services approaching resource limits before auto-scaling triggers or OOM errors occur.

Cold Start Latency Tracking

Detect latency spikes caused by App Runner instance cold starts after scale-out events. Correlate cold start duration with container image size and startup configuration.

AI Deployment Regression Detection

TigerOps AI compares error rate and latency baselines before and after each deployment. Failed deployments with metric regressions trigger automatic rollback recommendations.

Configuration

CloudFormation Stack for App Runner Metric Streams

Deploy the TigerOps CloudFormation stack to stream App Runner service metrics and deployment events.

tigerops-apprunner-streams.yaml
# TigerOps CloudFormation — App Runner Metric Streams
# aws cloudformation deploy \
#   --template-file tigerops-apprunner-streams.yaml \
#   --stack-name tigerops-apprunner \
#   --capabilities CAPABILITY_IAM

Parameters:
  TigerOpsApiKey:
    Type: String
    NoEcho: true

Resources:
  TigerOpsAppRunnerStream:
    Type: AWS::CloudWatch::MetricStream
    Properties:
      Name: tigerops-apprunner-stream
      FirehoseArn: !GetAtt TigerOpsDeliveryStream.Arn
      RoleArn: !GetAtt MetricStreamRole.Arn
      OutputFormat: opentelemetry0.7
      IncludeFilters:
        - Namespace: AWS/AppRunner
      StatisticsConfigurations:
        - AdditionalStatistics:
            - p50
            - p90
            - p99
          IncludeMetrics:
            - Namespace: AWS/AppRunner
              MetricName: RequestLatency

  # Capture deployment events via EventBridge
  AppRunnerDeploymentRule:
    Type: AWS::Events::Rule
    Properties:
      EventPattern:
        source:
          - aws.apprunner
        detail-type:
          - AppRunner Service Operation Status Change
      Targets:
        - Arn: !GetAtt DeploymentForwarder.Arn
          Id: TigerOpsDeploymentForwarder

  TigerOpsDeliveryStream:
    Type: AWS::KinesisFirehose::DeliveryStream
    Properties:
      HttpEndpointDestinationConfiguration:
        EndpointConfiguration:
          Url: https://ingest.atatus.net/api/v1/cloudwatch
          AccessKey: !Ref TigerOpsApiKey
        RequestConfiguration:
          CommonAttributes:
            - AttributeName: service
              AttributeValue: apprunner
        RetryOptions:
          DurationInSeconds: 60
FAQ

Common Questions

Which App Runner metrics does TigerOps collect?

TigerOps collects all AWS/AppRunner CloudWatch metrics including RequestCount, RequestLatency, ActiveInstances, Concurrency, 2xxStatusResponses, 4xxStatusResponses, 5xxStatusResponses, CPUUtilization, and MemoryUtilization per service.

Can TigerOps monitor App Runner services across multiple AWS accounts?

Yes. Deploy the TigerOps CloudFormation stack in each AWS account. TigerOps aggregates metrics across accounts and lets you filter by account, region, or service tag for a unified multi-account dashboard.

How does TigerOps track App Runner deployments triggered by source code changes?

TigerOps ingests App Runner EventBridge events for deployment lifecycle state changes. When a GitHub or ECR-triggered auto-deployment starts, TigerOps creates a deployment marker on your metrics timeline for instant correlation.

Does TigerOps support App Runner VPC connector monitoring?

Yes. App Runner VPC connector metrics including VpcConnectorState and network connectivity are included in the AWS/AppRunner namespace and collected by TigerOps automatically when the Metric Stream is configured.

Can I set up canary deployment analysis with App Runner and TigerOps?

Yes. TigerOps supports traffic-weighted deployment analysis. By tagging App Runner services with deployment stage labels, you can compare latency and error rates between old and new revisions during a gradual rollout.

Get Started

Stop Finding App Runner Deployment Regressions After Users Report Them

Request metrics, auto-scaling visibility, and AI deployment correlation. Deploy in 5 minutes.