Article

Set up private-CA trust for AgentCore Identity

For platform and identity teams, configure AgentCore’s private CA trust, preserve it during updates, rotate certificates and check separate costs.

Editorial illustration for Set up private-CA trust for AgentCore Identity: a controlled task flows from input to output. Not documentary evidence.

Enterprise identity teams can connect Amazon Bedrock AgentCore Identity to their existing private certificate authority (CA); buying AWS Private CA is optional. AWS’s November 18, 2026 walkthrough explains how. Configure a private network endpoint, then reference a CA certificate stored in S3 or Secrets Manager in the custom OAuth provider.

An identity provider issues access tokens. A CA certificate lets AgentCore verify that it is connecting to the intended identity-provider server. This guide covers outbound OAuth connections, where an agent obtains credentials to access another service. The capability predates the walkthrough: AWS’s November 11 SDK changelog already records private-CA support.

Prepare the private connection

Check that your deployment Region supports private identity providers and VPC Lattice. The AgentCore Region table lists Identity generally, not private-CA support separately; do not treat that row alone as confirmation for your deployment.

Choose between managed and self-managed VPC Lattice. Managed connectivity lets AgentCore create the networking resources from your VPC, subnet and security-group choices. Self-managed connectivity lets the network owner control those resources and share them directly across accounts through AWS Resource Access Manager. An existing peering or transit network is a separate routing choice.

Confirm private DNS resolution and reachability for the discovery, signing-key and token endpoints. For the related task of routing tool traffic through central inspection, see AgentCore private-API firewall routing. That backend route does not configure Identity’s trust in its sign-in server.

Store the CA bundle and grant read access

The certificate requirements are specific: PEM-encoded X.509 CA certificates, CA:TRUE, valid dates, and a maximum bundle size of 16,384 bytes. Include root or intermediate certificates, not a server leaf certificate or private key. The HTTPS server certificate must still match its hostname and chain to configured trust. Failed private-CA validation does not fall back to public trust.

Choose one certificate source, not one source per CA. A single bundle can contain multiple CAs. Store it in the provider’s Region. For Secrets Manager, use a plain PEM string—not JSON or binary—as specified in the console setup guide. AWS requires that secret to be in the provider’s account.

For cross-account S3 storage, supply s3.uri and s3.bucketOwnerAccountId for the actual bucket owner. The S3 certificate configuration supports this account identifier; access must also be authorized. A central certificate bucket and a cross-account network connection solve different problems, so plan their permissions separately.

The configuring IAM identity needs s3:GetObject or secretsmanager:GetSecretValue, plus decrypt permission for a customer-managed KMS key. Cross-account resource and key policies must permit access. The networking service-linked role does not replace these permissions.

Restrict bundle changes to the identity team or its deployment pipeline. The operational concern is integrity: a future provider update will trust the CA material that this source supplies.

Configure the outbound OAuth provider

Follow the custom-provider console setup:

  1. Open AgentCore’s Outbound Auth area and add an OAuth client. Select the custom provider and enter its discovery URL and registered client ID.

  2. Choose the required client authentication method. If it uses a secret, reference the stored client secret through Secrets Manager rather than putting it in a command or example.

  3. Under Additional configurations, set the private endpoint: your managed VPC settings or self-managed Lattice resource configuration ARN.

  4. Under Root certificate authority, choose Add root certificate. Select the stored CA source, choose Apply, then add the OAuth client.

For API automation, use oauth2ProviderConfigInput.customOauth2ProviderConfig.certificateConfigurations. The custom OAuth API requires privateEndpoint alongside it and permits exactly one source entry. Select either s3 or secretsManager; the latter uses secretArn. This reference contains no certificate bytes. Keep the CA source distinct from the OAuth client-secret reference.

Read GetOauth2CredentialProvider and wait for status to become READY. If creation or updating fails, inspect failureReason. Check source ownership, read access, certificate validity and private connectivity before retrying.

Then have the deployment owner verify an intended token request and a denied application action. Readiness is not proof of correct downstream permissions. The separate AgentCore user-versus-service access guide explains that choice for Snowflake.

Rotate trust with an explicit provider update

Replacing the stored bundle does not refresh active trust. AgentCore retains the certificate content fetched during configuration. After changing the source, call UpdateOauth2CredentialProvider with the certificate reference again.

Keep the reference in unrelated updates, too. Omitting certificateConfigurations removes private-CA configuration and restores public-CA trust. Do not send an empty list. Preserve the other provider settings you want to retain, following the documented update rules.

Use the provider update API with its name, vendor and desired OAuth configuration. Treat updating the certificate store and updating the provider as two coordinated deployment steps; completing only the first leaves the previous trust in place.

AWS documents an overlap-based CA rotation:

  1. Store both still-valid CAs in one bundle. Update the provider and wait for READY.

  2. Switch the identity provider’s server certificate to the new CA. Verify token requests.

  3. Store only the new CA and update the provider again. Confirm readiness before closing the change.

The overlap temporarily broadens trusted issuers. Keep it deliberate and time-limited, with an owner for removing the old CA. It is a cutover procedure, not a guarantee of uninterrupted authentication.

Monitor expiry and understand revocation limits

AWS says EarliestCertificateDaysToExpiry in AWS/Bedrock-AgentCore reports the earliest expiry in the bundle when tokens are requested. Alarm configuration needs all three dimensions: ProviderName, ProviderArn and TokenVault.

Because requests trigger emission, an idle provider may lack fresh samples. Decide how alarms handle missing data, and track the server certificate’s expiry separately; the bundle metric is not evidence that the server certificate remains healthy.

AWS also documents no certificate-revocation-list or OCSP checks. Publishing a revocation does not make Identity reject the server certificate; trust can persist until expiry or removal of the issuing CA through a provider update.

Budget for the CA and network separately

At the November 18 listed rates, one AWS Private CA in general-purpose mode costs $400 per full billed month outside the applicable trial, before other charges. Reusing an existing CA avoids adding that optional service, not the costs of operating your existing certificate infrastructure.

The first CA per account per Region has a 30-day CA-operation trial. Directly issued certificates are billed on issuance; certificates requested through AWS Certificate Manager are billed on their first export. Do not automatically add a direct-issuance fee to an unexported ACM certificate. The cheaper $50-per-month short-lived mode issues certificates valid for no more than seven days, so it is not a like-for-like replacement. These distinctions are on the Private CA pricing page.

AgentCore Identity pricing adds no Identity charge when used through Runtime or Gateway. Other usage costs $0.010 per 1,000 successful OAuth-token or API-key requests for non-AWS resources. Illustratively, 1,000,000 billable requests ÷ 1,000 × $0.010 = $10 for that component—not an all-in deployment estimate. These are access tokens, not model tokens.

The connectivity pricing comparison lists data-processing charges for managed Lattice, versus hourly resource charges plus processing for self-managed Lattice. Identity-provider hosting, storage, logging, Runtime or Gateway and model usage can add further costs. Decide whether existing certificate infrastructure and connectivity meet the requirement before provisioning replacements.