docs(aigw): update the AWS assumed-role trust ARN for SaaS - #1086
Merged
Merged
Conversation
The SaaS AI Gateway now assumes customer roles from arn:aws:iam::039293892788:role/AirsGwEnterpriseRole. The erstwhile Portkey ARN (arn:aws:iam::299329113195:role/portkey-app) no longer works, so trust policies copied from these pages fail. Update the Bedrock and Claude Platform on AWS assumed-role guides, retitle the code fences and placeholder to "AI Gateway Account ARN", reword the note to say the ARN applies to the SaaS deployment managed through Strata Cloud Manager, and fix a "Porktey" typo. The KMS role and the hybrid-deployment VPC endpoint principal still reference account 299329113195 and are left alone -- they are separate roles that were not part of this change. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
krishnachandra1709
approved these changes
Sep 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
The SaaS AI Gateway now assumes customer roles from
arn:aws:iam::039293892788:role/AirsGwEnterpriseRole. The erstwhile Portkey ARNarn:aws:iam::299329113195:role/portkey-appno longer works, so any trust policy copied from these pages fails to let the gateway in.Reported in Slack by a customer hitting exactly that; new ARN confirmed by Avanish Yadav.
Changed
aigw/product/model-catalog/connect-bedrock-with-amazon-assumed-role.mdxaigw/product/ai-gateway/virtual-keys/bedrock-amazon-assumed-role.mdxaigw/integrations/llms/claude-platform-aws/setup-assumed-role.mdxAll three are live in
docs.jsonnav.Alongside the ARN swap, on the same pages:
Portkey Account ARNcode fences and the<Portkey Account ARN>placeholder toAI Gateway Account ARN.Porkteytypo on the model-catalog page.Deliberately not changed
aigw/product/enterprise-offering/kms.mdx— uses299329113195:role/EnterpriseKMSPolicy, a different role for a different purpose.aigw/self-hosting/hybrid-deployments/aws/{ecs,eks}.mdx— use299329113195:rootas the management-plane principal for a VPC endpoint service.aigw/copies of these pages (product/,integrations/,virtual_key_old/), since the ask was scoped to the aigw docs.If the whole SaaS control plane moved to account
039293892788, the first two are stale too and worth a follow-up.🤖 Generated with Claude Code