Amazon App Runner

Amazon Web Services

Overview

Integrates with AWS App Runner to inventory the App Runner services running in the configured AWS accounts and regions. App Runner is a fully managed service that builds and runs containerized web applications and APIs. For each service the connector reads its configuration (network ingress, instance sizing, status) and tags, and emits one Brinqa object per App Runner service.

Data retrieved from Amazon App Runner

Connector Object	Required	Maps to Data Model
App Runner Service	Yes	Serverless

note

For detailed steps on how to view the data retrieved from Amazon App Runner in the Brinqa Platform, see How to view your data.

Setup

Connection settings

When setting up a data integration, select Amazon App Runner from the Connector dropdown and provide the following:

Setting	Required	Default	Description
Access key ID	No	—	AWS user access key ID, if not specified, the connector consults the default credentials provider chain to try and determine the \
Secret access key	No	—	AWS user secret access key, if not specified, the connector consults the default credentials provider chain to try and determine the \
Default region	No	—	Default AWS region, if not specified, the connector consults the default region provider chain to try and determine the region to use.
Assume role	No	—	Amazon Resource Name for the role to assume.
Session duration	No	900	Assume role session duration in seconds.
Page size	No	100	The maximum number of results to retrieve per operation.

Authentication

Authentication is shared across the AWS connector bundle via the AwsConfiguration base class. The App Runner sub-connector uses the AWS SDK for Java v2 AppRunnerClient, which signs every request with AWS SigV4 using credentials resolved through the following chain (in order):

1. STS AssumeRole — if assumeRoleARN is configured, the connector assumes that role (using the credentials below as the principal) and uses the resulting temporary session credentials.
2. Static access keys — if accessKey / secretKey are configured, they are used directly.
3. Default credentials provider chain — environment variables, ~/.aws/credentials, container role, or EC2 instance metadata.

Assumed-role sessions use the configurable sessionDuration (default 900 s) with a unique session name per sync. assumeRoleARN may be a comma-separated list to sync multiple accounts in one run. An AppRunnerClient is constructed per role per region and closed when its region has been fully synced.

Required AWS API permissions

Permission	Purpose
apprunner:ListServices	List and page through App Runner services in a region
apprunner:DescribeService	Retrieve full configuration for each service
apprunner:ListTagsForResource	Retrieve tags for each service
sts:AssumeRole	Only when assumeRoleARN is set

How to obtain Amazon App Runner credentials

Create an IAM user for AWS access

The connector authenticates using the AWS SDK's credential resolution chain. If an assume-role ARN is configured, the connector assumes that IAM role using the provided credentials. Otherwise, it uses the provided access keys directly, falling back to the AWS Default Credential Provider Chain (environment variables, ~/.aws/credentials, or EC2 instance metadata).

The IAM user or role must have the following permissions:

apprunner:ListServices
apprunner:DescribeService
apprunner:ListTagsForResource

Data & mappings

Attribute mappings

Expand the sections below to view the mappings between the source and the Brinqa data model attributes:

App Runner Service

Source Field Name	SDM Attribute
constant "AWS"	CLOUD_PROVIDER
ListTagsForResource.tags[] (key:value)	TAGS (multivalued)
Service.createdAt	FIRST_SEEN
Service.instanceConfiguration().cpu	CPU
Service.instanceConfiguration().instanceRoleArn	INSTANCE_ROLE_ARN
Service.instanceConfiguration().memory	MEMORY
Service.networkConfiguration().ingressConfiguration().isPubliclyAccessible	IS_PUBLICLY_ACCESSIBLE
Service.serviceArn	UID
Service.serviceArn	SERVICE_ARN
Service.serviceId	SERVICE_ID
Service.serviceName	SERVICE_NAME
Service.serviceName (fallback Service.serviceArn)	NAME
Service.serviceUrl	URL
Service.statusAsString	SOURCE_STATUS
Service.updatedAt	SOURCE_LAST_MODIFIED
sync region	REGION
sync timestamp	LAST_CAPTURED

Operations & API

Operations & API

Expand each connector object to see its operation options, delta-sync behavior, and the API it uses. See connector operation options for how to apply operation options (keys and values are case-sensitive).

App Runner Service

Operation options

Option	Type	Default	Description
region / regions	Comma-separated list of regions to query (one client per region). regions takes precedence over region.	Resolved from configuration / region provider chain
pageSize	Page size (maxResults) for each ListServices call.	Shared pageSize configuration (100)
parallelismLevel	Number of parallel worker threads.	min(4, CPU cores)	No

Delta sync

The connector README does not document sync behavior for this object.

API

• Type: AWS SDK for Java v2 (AppRunnerClient) · Endpoint: apprunner:ListServices

Changelog

Changelog

The Amazon App Runner connector has undergone the following changes:

Version	Description	Migration Steps
3.2.1	No changes in this release.	N/A
3.2.0	No changes in this release.	N/A
3.1.0	New Features - New connector — syncs AWS App Runner services, including a derived flag identifying unauthenticated public endpoints. Improvements - Sync failures are now visible. Previously, certain AWS API errors (throttling, server errors, transient network failures, validation errors) could be silently swallowed during multi-region sync, producing empty results without indicating a problem. These now surface as sync failures with a clear log entry detailing the HTTP status, AWS error code, request id, and service name. Per-region permission gaps (HTTP 401 / 403) still allow the sync to continue across other regions, but are now visible in logs.	N/A