canonical: https://jentic.com/apis/amazonaws.com/aws-app-runner # AWS App Runner Jentic publishes the only available OpenAPI specification for AWS App Runner, keeping it validated and agent-ready. Deploy containerized web applications and APIs directly from source code or container images without managing infrastructure. App Runner automatically handles provisioning, scaling, load balancing, and TLS certificate management across AWS regions, reducing deployment from days to minutes. ## For AI agents Deploy and manage container-based web services on AWS App Runner. Automate service creation, custom domain mapping, autoscaling configuration, and VPC connectivity without managing infrastructure. ## Scope Does not handle container orchestration, batch processing, or function-as-a-service - use for deploying persistent HTTP web services from container images or source code only. ## Capabilities - Deploy web services from container images or source code repositories with automatic build pipelines - Configure autoscaling thresholds that respond to concurrent request volume per service instance - Map custom domains to App Runner services with automatic TLS certificate provisioning - Connect services to private VPC resources through VPC connectors for database and internal API access - Pause and resume services to eliminate compute costs during idle periods without losing configuration - Attach observability configurations for X-Ray tracing and CloudWatch log aggregation per service - Trigger manual deployments or set up automatic deployment from source repository commits ## Use cases ### AI Agent Service Deployment AI agents use AWS App Runner through Jentic to deploy containerized microservices without managing cluster infrastructure. An agent searches for the deployment operation, receives the CreateService schema with source configuration and instance settings, and executes the call. App Runner handles provisioning compute, configuring the load balancer, and issuing TLS certificates. Deployment completes in under 5 minutes for standard container images. Example prompt: Create a new App Runner service from the container image 'myapp:latest' in ECR with 1 vCPU, 2GB memory, and autoscaling set to min 1 max 10 instances ### Auto-Scaling Web Applications Configure App Runner services to scale automatically based on concurrent request volume. Each autoscaling configuration defines minimum and maximum instance counts along with a concurrency threshold that triggers scale-out. App Runner adds instances when requests per instance exceed the threshold and scales in during low-traffic periods, maintaining response latency without manual intervention. Example prompt: Create an autoscaling configuration with max concurrency of 100 requests per instance, minimum 2 instances, and maximum 20 instances ### Private VPC Network Integration Connect App Runner services to resources inside a private VPC using VPC connectors. This allows deployed services to reach RDS databases, ElastiCache clusters, and internal APIs that are not publicly accessible. Each VPC connector specifies subnets and security groups, establishing a network path from App Runner's managed infrastructure into your private network without exposing services to the public internet. Example prompt: Create a VPC connector targeting subnets subnet-abc123 and subnet-def456 with security group sg-789012 for database access ### Custom Domain Mapping with TLS Map branded domains to App Runner services with automatic certificate provisioning and renewal. The AssociateCustomDomain operation links a domain name to a service and returns DNS validation records. Once DNS propagation completes and validation succeeds, App Runner provisions a TLS certificate and routes traffic from the custom domain to the service endpoint. Example prompt: Associate the custom domain 'api.example.com' with the App Runner service identified by its ARN and retrieve the DNS validation records ### Cost Optimization with Service Pause Pause App Runner services during non-production hours to eliminate compute costs while preserving the service configuration, custom domains, and deployment history. A paused service retains its URL and can be resumed in seconds when traffic needs to be served again. This is particularly effective for development and staging environments that only need availability during business hours. Example prompt: Pause the App Runner service with ARN 'arn:aws:apprunner:us-east-1:123456789:service/my-dev-service' and verify the status changes to PAUSED ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | /#X-Amz-Target=AppRunner.CreateService | Deploy a new service from source code or container image | | POST | /#X-Amz-Target=AppRunner.DescribeService | Retrieve service configuration and current status | | POST | /#X-Amz-Target=AppRunner.ListServices | List all App Runner services in the account | | POST | /#X-Amz-Target=AppRunner.CreateAutoScalingConfiguration | Define scaling thresholds for service instances | | POST | /#X-Amz-Target=AppRunner.AssociateCustomDomain | Link a custom domain to a service | | POST | /#X-Amz-Target=AppRunner.CreateVpcConnector | Create a connector for private VPC access | | POST | /#X-Amz-Target=AppRunner.StartDeployment | Trigger a manual deployment | | POST | /#X-Amz-Target=AppRunner.PauseService | Pause a service to stop compute charges | ## Key resources - **Services** — App Runner web services deployed from container images or source code with associated runtime configuration - **AutoScaling Configurations** — Scaling policies defining concurrency thresholds, minimum and maximum instance counts - **Custom Domains** — Domain name associations with automatic TLS certificate provisioning - **VPC Connectors** — Network bridges connecting App Runner services to private VPC subnets - **Connections** — Source code repository connections for automatic build and deployment pipelines - **Observability Configurations** — Tracing and logging configurations for service monitoring ## Why Jentic - **Setup:** Wiring AWS App Runner by hand means creating IAM credentials, choosing the right regional host from apprunner.{region}.amazonaws.com, signing every request with AWS SigV4, and passing the X-Amz-Target action header on each call yourself. Through Jentic you install once, import AWS App Runner from the API Directory, store the AWS access key once, and your agent calls it. - **Permission scoping:** AWS App Runner carries the service and configuration targets in the request body rather than the URL path, so limit the agent to the operations it needs, such as CreateService, DescribeService, or ListServices. You choose the operations it may call, so destructive ones like deleting a service or pausing it are not included unless you add them. - **Credential handling:** Your AWS access key for AWS App Runner is stored once, encrypted, by your own Jentic One instance and signed with SigV4 at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'deploy a container service on AWS' or 'link a custom domain to a service', and Jentic returns the matching AWS App Runner operation with its input schema so the agent calls the right endpoint without browsing the AWS service reference. ## Related APIs - **AWS Lambda** — Lambda runs individual functions while App Runner deploys full containerized web services with built-in load balancing - **Render API** — Render provides similar container deployment with a simpler pricing model but less AWS ecosystem integration - **DigitalOcean API** — DigitalOcean App Platform offers similar PaaS deployment with a broader feature set including managed databases ## FAQ ### Why is there no official OpenAPI spec for AWS App Runner? AWS does not publish an OpenAPI specification for App Runner. Jentic generates and maintains this spec so that AI agents and developers can call AWS App Runner via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer. ### What authentication does the AWS App Runner API use? App Runner uses AWS Signature Version 4 (SigV4) authentication via an HMAC-signed Authorization header. Through Jentic, your AWS credentials are stored encrypted in your Jentic One instance and agents receive scoped access tokens, so raw AWS secret keys never enter the agent context. ### Can I deploy a service from a GitHub repository using the App Runner API? Yes. First create a connection to your GitHub account using the CreateConnection operation, then use CreateService with a SourceConfiguration that references the repository URL, branch, and build settings. App Runner builds the container from source and deploys it automatically on each commit. ### What are the scaling limits for AWS App Runner? Each App Runner service can scale from 1 to 25 instances by default (adjustable via service quotas). Autoscaling triggers based on concurrent requests per instance, with configurable thresholds via CreateAutoScalingConfiguration. Each instance supports 1-4 vCPUs and 2-12 GB memory. ### How do I connect an App Runner service to a private RDS database through Jentic? Search Jentic for 'create VPC connector for App Runner'. The agent receives the CreateVpcConnector schema requiring subnet IDs and security group IDs. After creating the connector, update the service with UpdateService to attach the VPC connector. The service then routes outbound traffic through your private subnets to reach RDS. ### Can I pause an App Runner service to reduce costs? Yes. The PauseService operation stops all running instances and eliminates compute charges while preserving the service URL, custom domains, and configuration. Resume with ResumeService when you need the service active again. Paused services still incur minimal charges for the paused state. ### How does Jentic help AI agents deploy services on App Runner? Agents search by intent (e.g., 'deploy a container on AWS') and Jentic returns the matching CreateService operation with its full input schema. The agent fills in the image URI, instance configuration, and scaling settings, then executes through Jentic. No AWS SDK setup or credential management required - install with pip install jentic and authenticate through Jentic One, the self-hosted execution layer. ### Can I limit what my agent is allowed to do with the AWS App Runner API? Yes. Because Jentic One is self-hosted, you decide which App Runner operations your agent may call, restricting it to what it needs such as CreateService, DescribeService, or ListServices. App Runner carries the service and configuration targets in the request body rather than the URL, so destructive operations like deleting or pausing a service are excluded unless you explicitly add them. Your AWS access key stays under your own rules and is signed at execution time, so the agent only ever exercises the operations you have permitted.