docs(forest-runtime): document Amazon Bedrock as an AI provider - #33
Open
Scra3 wants to merge 3 commits into
Open
docs(forest-runtime): document Amazon Bedrock as an AI provider#33Scra3 wants to merge 3 commits into
Scra3 wants to merge 3 commits into
Conversation
AI_PROVIDER now accepts bedrock, for customers who need their LLM calls to stay inside their AWS account. It is the one provider that takes no AI_API_KEY: credentials come from the AWS chain, and a key set alongside it fails at startup rather than being ignored — worth stating, since the previous wording made the three variables sound inseparable. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
![macroscopeapp[bot]](https://avatars.githubusercontent.com/in/900172?s=60&v=4){kind=small}
|
|
||
| ```bash | ||
| AI_PROVIDER=bedrock | ||
| AI_MODEL=us.anthropic.claude-sonnet-4-6-v1:0 |
There was a problem hiding this comment.
🟠 High workflows/forest-runtime.mdx:237
The copy-paste configuration cannot invoke us.anthropic.claude-sonnet-4-6-v1:0 from AWS_REGION=eu-west-3: it is a US geo profile, and it is not the documented Sonnet 4.6 profile ID. Use the Paris-compatible eu.anthropic.claude-sonnet-4-6 profile, or pair the US profile with a supported US source Region.
Suggested change
| AI_MODEL=us.anthropic.claude-sonnet-4-6-v1:0 | |
| AI_MODEL=eu.anthropic.claude-sonnet-4-6 |
🚀 Reply "fix it for me" or copy this AI Prompt for your agent:
In file @product/process/workflows/forest-runtime.mdx around line 237:
The copy-paste configuration cannot invoke `us.anthropic.claude-sonnet-4-6-v1:0` from `AWS_REGION=eu-west-3`: it is a US geo profile, and it is not the documented Sonnet 4.6 profile ID. Use the Paris-compatible `eu.anthropic.claude-sonnet-4-6` profile, or pair the US profile with a supported US source Region.
A customer's devops asked whether they can assume a role instead of providing keys. They can — the SDK's own chain handles it — but the previous wording only named task roles, profiles and static keys, so it read as if those were the whole list. Also warns that AWS_REGION is required even when the profile declares one: the Bedrock client does not read the region from the profile, and that is the one place where the chain does not behave as a reader would expect. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
| | Static keys | `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`. | | ||
|
|
||
| <Warning> | ||
| `AWS_REGION` is required even when your profile already declares a `region` — the Bedrock client does not read the region from the profile. Forest Runtime refuses to start without it rather than failing on the first AI step. |
There was a problem hiding this comment.
🟡 Medium workflows/forest-runtime.mdx:245
The documentation incorrectly says AWS_REGION is mandatory, even though the executor also accepts AWS_DEFAULT_REGION; users with only the standard AWS variable are therefore told their valid setup will be rejected. Document both accepted variables here.
Suggested change
| `AWS_REGION` is required even when your profile already declares a `region` — the Bedrock client does not read the region from the profile. Forest Runtime refuses to start without it rather than failing on the first AI step. | |
| `AWS_REGION` or `AWS_DEFAULT_REGION` is required even when your profile already declares a `region` — the Bedrock client does not read the region from the profile. Forest Runtime refuses to start without either variable rather than failing on the first AI step. |
🚀 Reply "fix it for me" or copy this AI Prompt for your agent:
In file @product/process/workflows/forest-runtime.mdx around line 245:
The documentation incorrectly says `AWS_REGION` is mandatory, even though the executor also accepts `AWS_DEFAULT_REGION`; users with only the standard AWS variable are therefore told their valid setup will be rejected. Document both accepted variables here.
Bedrock resells hundreds of models and the runtime only accepts Claude Sonnet, Haiku and Opus, so the page needs to say which ids work rather than leave the reader to try one and get a startup refusal. Also warns against the global. prefix: it routes worldwide, which defeats the data residency that sends most customers to Bedrock in the first place. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Companion to ForestAdmin/agent-nodejs#1897, which adds
AI_PROVIDER=bedrockto the self-hosted executor.Bedrock is the one provider that takes no
AI_API_KEY— credentials come from the AWS chain, and a key set alongside it fails at startup rather than being ignored. The previous wording made the three variables sound inseparable, so the note and the table both needed adjusting, not just a new row.Adds a short Amazon Bedrock subsection with the required
AWS_REGION, thebedrock:InvokeModelpermission, and a copy-pasteable example.Merge after the agent-nodejs PR ships.
🤖 Generated with Claude Code
Note
Document Amazon Bedrock as an AI provider in
forest-runtimeUpdates the AI provider configuration docs to include
bedrock, adjusts the API-key wording so it is not required for Bedrock, and revises the all-or-nothing configuration note. Adds a Bedrock section covering supported Anthropic model families, model and inference-profile identifiers, regional residency guidance, AWS credential-chain behavior, required IAM permission, role-assumption setup options, theAWS_REGIONsetting, and a Bedrock environment-variable example.Macroscope summarized 73f4231.