[DOCS] Bedrock onboarding docs omit login-screen setup wizard

Open 💬 5 comments Opened Apr 4, 2026 by coygeek

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/quickstart

Section/Topic

Step 2: Log in to your account and Bedrock/third-party provider onboarding during first-run setup

Current Documentation

No documentation currently exists for the interactive Bedrock setup wizard that opens from the login screen when users choose 3rd-party platform.

The quickstart page currently says:

Claude Code requires an account to use. When you start an interactive session with the claude command, you'll need to log in: You can log in using any of these account types: * Amazon Bedrock, Google Vertex AI, or Microsoft Foundry (enterprise cloud providers)

The authentication page currently says:

* Cloud providers: if your organization uses Amazon Bedrock, Google Vertex AI, or Microsoft Foundry, set the required environment variables before running claude. No browser login is needed.

The Bedrock page currently documents only the manual setup flow:

### 2. Configure AWS credentials Claude Code uses the default AWS SDK credential chain. Set up your credentials using one of these methods: ### 3. Configure Claude Code Set the following environment variables to enable Bedrock: ### 4. Pin model versions

What's Wrong or Missing?

Changelog v2.1.92 added:

Added interactive Bedrock setup wizard accessible from the login screen when selecting "3rd-party platform" — guides you through AWS authentication, region configuration, credential verification, and model pinning

Current docs explain Bedrock prerequisites and manual environment-variable setup, but they do not explain that Claude Code now has an in-product onboarding flow for Bedrock users.

Users reading the onboarding and authentication docs cannot discover:

  • that choosing 3rd-party platform on the login screen can launch Bedrock setup
  • that the wizard guides AWS authentication, region configuration, credential verification, and model pinning
  • how this guided flow relates to the existing manual Bedrock setup instructions

Because that workflow is undocumented, first-time Bedrock users are still directed only to preconfigure everything manually before starting Claude Code.

Suggested Improvement

Add a short Bedrock onboarding subsection to the quickstart and authentication docs that explains the new guided flow.

It should document:

  • how to launch it: start claude, choose 3rd-party platform on the login screen, then select Bedrock
  • what the wizard covers: AWS authentication, region configuration, credential verification, and model pinning
  • when to use the wizard versus the existing manual Bedrock setup guide
  • where to go for prerequisites, IAM configuration, and troubleshooting

Then add a note to the Bedrock page clarifying that users can either configure Bedrock manually or use the interactive setup wizard added in v2.1.92.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

| Page | Context |
|------|---------|
| https://code.claude.com/docs/en/quickstart | First-run login flow currently lists Bedrock as an account type but does not explain the new guided setup path |
| https://code.claude.com/docs/en/authentication | Cloud-provider auth currently points users to manual environment-variable setup only |
| https://code.claude.com/docs/en/amazon-bedrock | Bedrock page documents manual AWS credentials, region setup, and model pinning, but not the interactive wizard |
| https://code.claude.com/docs/en/third-party-integrations | Enterprise provider overview links to Bedrock setup docs but does not mention the login-screen onboarding workflow |

Total scope: 4 pages affected

Source: Changelog v2.1.92

Exact changelog entry:

Added interactive Bedrock setup wizard accessible from the login screen when selecting "3rd-party platform" — guides you through AWS authentication, region configuration, credential verification, and model pinning

View original on GitHub ↗

This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗