synthetiq infra provision registers a target here after provisioning the account; deploys resolve an app’s target to know which account, role, and domain to use.
An organization can hold multiple targets (e.g. a shared target plus a dedicated BYOI one); one is the default. Each production app pins to a target.
Node SDK: sdk.awsConfig.*. See Node SDK.
List deployment targets
Register / update a deployment target
(organization, aws_account_id). Called by synthetiq infra provision once the AWS account is provisioned. Only the deploy key hash is sent — the raw key never leaves the customer account.
| Parameter | Type | Description |
|---|---|---|
aws_account_id | body | Target AWS account id |
deploy_role_arn | body | Role the deploy pipeline assumes |
deploy_api_key_hash | body | Hash of the in-account deploy key |
domain | body | Base domain for apps (e.g. apps.acme.com) |
cert_arn | body | CloudFront (CDN) ACM certificate ARN |
api_cert_arn | body | ALB (API) ACM certificate ARN |
db_flavor | body | Database flavor for new apps (e.g. aws-serverless-rds) |
provision_config | body | Snapshot of the synthetiq.yaml used, for audit |
status | body | ready once all required fields are present |
ready and no default exists.
Authentication: Organization member + infra:provision scope (token: platform:infra:write).
See also
- CLI:
synthetiq infra(init,generate,provision,status) - BYOI overview and Prerequisites

