Fix aws_region platform list in Anthropic connection docs#69373
Merged
vincbeck merged 1 commit intoJul 6, 2026
Conversation
vincbeck
approved these changes
Jul 6, 2026
|
Awesome work, congrats on your first merged pull request! You are invited to check our Issue Tracker for additional contributions. |
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
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.
The Anthropic connection documentation describes the
aws_regionextra as applying only to thebedrockplatform, but the hook also passes it to theawsplatform (Claude Platform on AWS) client — added during review of #69003 ("Pass aws_region to the AnthropicAWS (Claude Platform on AWS) client"). The hook docstring already lists both platforms; this updatesconnections.rstto match, so users configuringplatform="aws"know the key applies to them.related: #69003
Was generative AI tooling used to co-author this PR?
Claude Code
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.