LaunchpadHQ

Amazon Bedrock

by AWS

Getting-started guide

Getting Started with Amazon Bedrock

AWS's single door to AI models from Anthropic, OpenAI, Meta and a dozen more labs — billed by what you use.

Last reviewed 2026-09-08 · for Amazon Bedrock

How it works

You sign in to AWS, open Bedrock, and pick a model (the AI "brain" that does the actual thinking) from a catalog. You type a question in the browser and read the reply. When you want it inside your own software, you generate a key and call the same models from code — swapping models means changing one line.

What it is

Amazon Bedrock is AWS's single door to AI models built by other companies. Instead of an account with Anthropic, another with OpenAI, another with Mistral, you reach models from around eighteen labs behind one login and one AWS bill. It's built for people making software — an API (a way for programs to talk to each other without a person clicking), not a chat app.

Before you start

The barrier here is AWS, not Bedrock. There's no Bedrock signup — you open an AWS account, which needs a real credit or debit card even on the free plan, and you meet AWS's permissions and regions before you meet a model.

Cost is per use, with no subscription. A new AWS account gets a starting credit at signup and can earn more by trying services, Bedrock among them — but the free plan ends six months in, or when the credit runs out. A trial, not an allowance.

Anthropic's models need a one-time use-case form per AWS account before your first call. Other providers' models subscribe themselves on first use.

Which models you can reach depends on the AWS region you pick, and newer ones are called through a geographic profile — the same name with us. or eu. in front.

Security & privacy

The reason companies pick Bedrock over calling each lab directly is in AWS's own FAQ: your content isn't used to improve the base models and isn't shared with any model provider. Claude runs here without Anthropic seeing your text.

Your key spends your money — so give it a lifespan

  • You choose the expiry when you create a long-term key, and AWS's own docs recommend those keys only for exploring.
  • It's shown once — copy it somewhere private, never into a public code repository or a screenshot.

One honest wrinkle: geographic profiles spread a request across regions inside a geography like US or EU. Your data stays in that geography, but AWS states inputs and outputs may leave the region you picked, and may be stored there for abuse detection.

What it's good (and not good) at

Best at

  • Putting one question to rival labs' models without an account at each
  • Building on Claude, GPT or Llama with your text staying inside your own AWS account
  • Teams already on AWS, who inherit the billing, permissions and logging they have

Okay at

  • Being a first AI tool — there's no consumer app here
  • Predictable monthly cost, since the bill follows use
  • Launch-day access — new frontier models often reach their own lab's API first

Avoid

  • Assuming a model you read about is callable — it depends on your region
  • Long-term API keys in production, which AWS's own docs advise against
  • Following an older tutorial into Bedrock Agents — AWS closed it to new customers on 30 July 2026 and points new builders at AgentCore

First things to try

Compare models before you write any code

Put one question to up to three models in the console and read the replies side by side.

Why this one: Bedrock's catalog names around eighteen providers, OpenAI and Anthropic among them, and the console runs one question across three at once. That's how you find out a cheap model answers as well as the expensive one.

Give yourself a key with an expiry date

Generate a long-term key in the console and set it to expire; AWS's quickstart uses 30 days.

Why this one: Bedrock lets you choose the lifespan as you create the key, and its short-term keys last about twelve hours. A forgotten Bedrock key stops working; a forgotten permanent key keeps spending.

Set a budget, and know what it actually does

Create an AWS Budget with an email threshold before your first call.

Why this one: On AWS the alarm and the brake are separate: a budget threshold sends a notification, while stopping spend means configuring a budget action that applies a deny policy.

Clear the Anthropic form first

Submit the one-time use-case form for Anthropic models, once per AWS account.

Why this one: Anthropic is the provider on Bedrock that gates first use this way; access opens the moment you submit, and a form filed at an organisation's management account carries down to the accounts beneath it.

Common pitfalls

  • Most Bedrock confusion is AWS confusion. Permissions, regions and billing all belong to AWS, and a free-plan account closes itself six months after signup.
  • A first call to a provider you haven't used can fail while Bedrock subscribes you in the background. Wait a couple of minutes and try again before assuming you set something up wrong.

Where to next

Want the full picture first? See the Amazon Bedrock overview for pricing, the free tier and related tools.