AWS Bedrock basics

Amazon Bedrock is an AWS service: a managed way for applications to call foundation models through AWS APIs, under an AWS account’s billing and permissions. It is a cloud platform, not an Anthropic product.

You can finish this lesson without creating an AWS account, enabling models, or deploying anything.

What Bedrock is (and isn’t)

Bedrock is	Bedrock is not
AWS’s door to many foundation models	“Where Claude lives” by default
API + permissions + quotas on AWS	Claude chat or Claude Code
One example of cloud-hosted frontier models	The only cloud that hosts large models

Claude models may be available through Bedrock when an account enables them — as one of several model choices. Teams also use Bedrock for models from other providers. Same AWS door; different model behind it.

Why teams use it (intuition)

• One cloud neighborhood — Models sit next to other AWS resources the company already runs.
• Model choice — Compare or switch models without rebuilding the whole app (still test carefully).
• IAM mental model — Access is usually “this role may invoke that model,” not a consumer chat login.

Chat app vs Bedrock

	Consumer chat (e.g. Claude chat)	Bedrock
Maker focus	Model vendor’s product UI	AWS platform
You see	Conversation	App/code calling an API
Typical bill	Subscription / usage with the vendor	AWS usage
Setup	App signup	Org AWS account + permissions

What this lesson skips on purpose

• No console click-paths, no account setup walkthrough
• No access keys, account IDs, or live API calls
• No requirement to spend money to “complete” Foundations

See also: Glossary — Amazon Bedrock, API.

Takeaway

Bedrock = AWS’s managed model platform. Claude = Anthropic’s models/products. They can connect; they are not the same thing.