AWS App Runner
Browse all Amazonaws APIs★ Only Publicly Available OpenAPI DocumentCloud InfrastructureServerlessapiKey35 EndpointsREST
For 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.
Use for: I need to deploy a container image as a web service on AWS, Set up automatic scaling for my App Runner service based on request concurrency, I want to connect my App Runner service to a database in a private VPC, List all running App Runner services in my AWS account
Not supported: 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.
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.
Install Jentic One Beta
Connect the AWS App Runner to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AWS App Runner, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with AWS App Runner API.
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
Patterns agents use AWS App Runner API for, with concrete tasks.
★ 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.
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.
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.
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.
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.
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
35 endpoints — jentic publishes the only available openapi specification for aws app runner, keeping it validated and agent-ready.
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
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
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
AWS access keys and secret keys are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped session tokens with SigV4 signing handled automatically — raw AWS credentials never enter the agent's context window.
Intent-based discovery
Agents search by intent (e.g., 'deploy a container service on AWS') and Jentic returns matching App Runner operations with their full request schemas, including required parameters for source configuration, instance settings, and networking options.
Time to first call
Direct AWS App Runner integration: 1-3 days for SDK setup, IAM policy configuration, and SigV4 signing implementation. Through Jentic: under 1 hour — search for the operation, receive the schema, execute the call with automatic credential handling.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using AWS App Runner API through Jentic.
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 at https://app.jentic.com/sign-up.
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 the MAXsystem vault 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 at https://app.jentic.com/sign-up.
GET STARTED