Amazon Bedrock basics
Read the Bedrock model catalogue, understand model IDs and inference profiles, know how model access works today, compare pricing options and decide where a request's data may be processed.
Assumes: Amazon Bedrock model cards and user guide checked 2026-11-18 · AWS CLI v2 · Region us-east-1 · model availability changes often (⚠ VERIFY before each lab). Verified against official sources on 2026-11-18.
Learning objectives
By the end of this lesson you can:
- Name the Bedrock endpoints and APIs and say which one an application, an administrator and a knowledge base use.
- Read a model card and pick the correct model ID or inference profile ID for your Region.
- Explain how model access works in 2026, including the Anthropic first-time-use form and the AWS Marketplace permissions.
- Choose between on-demand, service tiers, provisioned throughput and prompt caching for a workload, and estimate a monthly bill.
- Say where a request may be processed and why that matters for UK GDPR and data-residency reviews.
Prerequisites
- GenAI in plain language: tokens, context windows, embeddings.
- Module 5: Security for IAM and logging, and UK GDPR and data residency.
- Tools: AWS CLI v2 and the
learn-sandboxSSO profile (only needed for the optional CLI commands).
Why this matters in banking
Harbourline Bank's platform team approves a proof of concept in us-east-1. A developer picks the first model in the console, the pilot works, and then the risk team asks three questions nobody can answer: where did the prompts go, who is the model provider, and what will this cost when 4,000 colleagues use it? Each answer lives in this lesson. If you cannot say where a prompt is processed, which legal terms apply to the model, and how the bill scales, you cannot take the proof of concept to a model-risk committee.
The idea in plain language
Amazon Bedrock is a managed service that lets you call foundation models from many providers through AWS APIs. You do not run servers or GPUs. AWS publishes statements about how Bedrock handles your prompts and outputs and whether they are used to improve models; read the current data-protection page yourself for your sign-off ⚠ VERIFY, because this lesson makes no compliance claims.
Analogy: Bedrock is a switchboard in a bank's head office. You dial one number (the API), say which specialist you want (the model ID), and the switchboard connects you. You do not need to know where the specialist sits, but the bank's data-protection officer certainly does, which is why inference profiles tell you.
The APIs and endpoints
Bedrock is several services behind different endpoints. Mixing them up is the most common beginner error.
| Endpoint / service | Used for | Typical caller | .NET package |
|---|---|---|---|
bedrock (control plane) | List models, manage guardrails, inference profiles, evaluation jobs, custom models | Admin tools, IaC, CI | AWSSDK.Bedrock |
bedrock-runtime | Run models: Converse, ConverseStream, InvokeModel, ApplyGuardrail | Your application | AWSSDK.BedrockRuntime |
bedrock-agent | Create and manage knowledge bases and data sources, start ingestion | Admin tools, IaC | AWSSDK.BedrockAgent |
bedrock-agent-runtime | Query knowledge bases (Retrieve, RetrieveAndGenerate) | Your application | AWSSDK.BedrockAgentRuntime |
bedrock-mantle | An alternative runtime endpoint that serves the Anthropic Messages API for Claude models | Code that already uses the Anthropic SDK | Anthropic's Bedrock client |
On the Claude 5.5 model cards, AWS recommends bedrock-runtime for new applications, and bedrock-mantle does not support Guardrails or Knowledge Bases for those models. This module uses bedrock-runtime.
Four operations you will meet constantly:
- Converse / ConverseStream: one request shape that works across providers. Use it by default.
- InvokeModel / InvokeModelWithResponseStream: the raw, model-specific request body. You need it for things Converse does not cover, such as the Titan embedding model.
- ApplyGuardrail: run a guardrail on any text without calling a model. Covered in Bedrock Guardrails.
- Retrieve / RetrieveAndGenerate: search a knowledge base, optionally with generation. Covered in Knowledge Bases and RAG.
What problem the AWS service solves
Before Bedrock, a bank that wanted a hosted model signed a contract with one provider, built that provider's SDK into its code and repeated the exercise for the next model. Bedrock gives you:
- Choice behind one API. The model catalogue lists dozens of providers. Swapping a model is mostly a string change with Converse.
- AWS identity, network and logging. IAM controls who can call which model, PrivateLink keeps traffic off the internet, CloudTrail records API calls and model invocation logging can capture prompts and responses.
- Pay-per-token with no infrastructure (or reserved capacity if you need it).
Honest limits and sharp edges:
- Model availability changes quickly. Models launch, enter a legacy period and reach end of life. Plan for a model change at least once a year.
- Quotas are per account, per Region and per model. New accounts often start with low limits ⚠ VERIFY the current defaults in the Service Quotas console before you plan a launch.
- Features differ by model. For the Claude 5.5 models,
Count tokensis not supported onbedrock-runtime, and only the Standard service tier is listed, so do not assume that a feature in one model's documentation works for another. - Third-party models are billed through AWS Marketplace. Charges appear under the model provider in Cost Explorer, not under "Amazon Bedrock".
Microsoft / Azure comparison
| You know (Microsoft/Azure) | AWS equivalent | What's different |
|---|---|---|
| Azure OpenAI resource with named deployments | Bedrock model ID or inference profile ID | No deployment object to create for on-demand use: you call the model ID directly |
| Deployment "model version" pinning | Model ID with a version suffix, plus lifecycle dates on the model card | Read the model's legacy and end-of-life dates |
| Azure OpenAI "Global" vs "Data Zone" deployments | Global vs geographic (for example us., eu.) cross-Region inference profiles | The profile prefix tells you the routing scope |
| Provisioned Throughput Units (PTU) | Bedrock Provisioned Throughput (model units, hourly, with commitment) | Sized with the account team for third-party models |
| Azure private endpoint | VPC interface endpoint for bedrock-runtime | Same idea: keep traffic on the private network |
| Azure Monitor diagnostic settings for requests | Model invocation logging to CloudWatch Logs and/or S3 | Off by default; contains prompts, so protect it |
Architecture
Security-boundary view: your application and the VPC endpoint are inside your boundary. Everything after the endpoint is the AWS service plus the model provider's terms. Invocation logs are a second copy of your prompts, so they need the same classification, encryption and retention as the prompts themselves.
Reading a model card
Open Console → Amazon Bedrock → Model catalog, or the public page at Models at a glance and choose a model. Facts below come from the Claude Sonnet 5.5 and Claude Haiku 5.5 cards checked on 2026-11-18. Treat them as a worked example of what to read, not as permanent values.
| Field on the card | Claude Sonnet 5.5 | Claude Haiku 5.5 | Why it matters |
|---|---|---|---|
| Launch date | 2026-09-28 | 2026-10-07 | New models are newer than your training data about them |
| EOL no sooner than | 2027-09-28 | 2027-10-07 | Your replacement plan |
| Context window / max output | 1M tokens / 128K | 1M tokens / 128K | Sizing prompts |
| Knowledge cutoff | June 2026 | June 2026 | What it cannot know |
bedrock-runtime APIs | Messages, Converse, Invoke | Messages, Converse, Invoke | Converse is supported |
| Guardrails, Knowledge Bases | Supported on bedrock-runtime | Supported on bedrock-runtime | Not on bedrock-mantle |
| Service tiers | Standard only listed | Standard only listed | No Priority, Flex, Reserved or Batch listed |
| Model ID | anthropic.claude-sonnet-5-5 | anthropic.claude-haiku-5-5 | See next section |
| In-Region in us-east-1 | No | No | You must use an inference profile |
The 5.5 cards also say thinking blocks are bound to the model and to the AWS account that produced them. In practice: do not store and replay a model's reasoning blocks in a different account or against a different model, and show end users only the text blocks.
Model IDs and inference profiles
A model ID names a model (anthropic.claude-haiku-5-5). An inference profile is a routing wrapper that sends your request to one or more Regions. For the Claude 5.5 models, the cards list no In-Region support in us-east-1: you call a profile.
| ID you pass | Scope | Example for Haiku 5.5 |
|---|---|---|
Geo profile, us. prefix | Routes within the US Regions the profile lists | us.anthropic.claude-haiku-5-5 |
Geo profile, eu. prefix | Routes within European Regions | eu.anthropic.claude-haiku-5-5 |
| Global profile | Routes to any commercial Region | global.anthropic.claude-haiku-5-5 |
| Bare model ID | A single Region, only where the card says In-Region is supported | anthropic.claude-haiku-5-5 |
For a us. profile called from us-east-1, the Sonnet 5.5 card lists the destination Regions as us-east-1, us-east-2 and us-west-2. For an eu. profile called from eu-west-2 (London), it lists Frankfurt, Stockholm, Milan, Spain, Ireland, London and Paris. The routing depends on the Region you call from.
Check routing yourself, do not trust the prefix
AWS says that if you have data-residency requirements you should call GetInferenceProfile from every source Region you plan to use and read every destination Region in the response, rather than relying on the prefix in the ID. Cross-Region inference can also route to opt-in Regions you have not enabled, and AWS notes that prompts and outputs may be stored in an opt-in Region for abuse detection. Service Control Policies that block any destination Region make the whole request fail.
Embeddings are different
The embedding model Titan Text Embeddings V2 (amazon.titan-embed-text-v2:0) works with InvokeModel and not with Converse. It accepts up to an 8K-token input and offers 1,024, 512 or 256 dimensions. Its card lists in-Region availability in us-east-1 and in London (eu-west-2). The request body is model specific, which is the reason InvokeModel still matters.
Model access in 2026
Older tutorials tell you to open a Model access page and tick boxes. That is no longer how it works in the commercial Regions.
- In commercial Regions the Model access page is not used: access to most models is enabled on first use. You open a model in the catalog or simply call it. The page remains for AWS GovCloud (US).
- First invocation of a third-party model starts an AWS Marketplace subscription in the background. The calling identity needs
aws-marketplace:Subscribe,aws-marketplace:Unsubscribeandaws-marketplace:ViewSubscriptionsfor that first call. Afterwards, users do not need those permissions to invoke the model. The account also needs a valid payment method. - Anthropic first-time-use form. For Anthropic models earlier than Claude Opus 4.7 you must submit use-case details once per account (or once at the Organization management account) before invoking. Claude Opus 4.7 and later do not need the form. The form asks for a company name, a website and a description of intended use.
- The first call can briefly appear to work and then fail with
AccessDeniedExceptionif a prerequisite is missing. After you fix permissions, allow a couple of minutes. - Models from Amazon, Meta, Mistral AI and several other providers do not go through AWS Marketplace, so you cannot scope those with
aws-marketplace:ProductId.
For a bank, this changes the control design. Because access is automatic on first use, the control is no longer "nobody ticked the box". You enforce which models may be used with IAM and Service Control Policies. AWS's own guidance for organisations that must review model terms first: initially block bedrock:InvokeModel with an SCP or IAM policy, review the End User License Agreement, then allow the model. Denying aws-marketplace:Subscribe alone does not block the first call, because Bedrock starts the subscription itself.
Pricing models
| Option | You pay | Good for | Watch out |
|---|---|---|---|
| On-demand, Standard tier | Per input and output token, no commitment | Pilots, spiky traffic | Quotas apply; throttling under load |
| Priority / Flex / Reserved / Batch tiers | Premium for speed, discount for flexibility, commitment for reserved capacity, batch for bulk | Latency-critical or offline workloads | Per model: the Claude 5.5 cards list Standard only |
| Prompt caching | Cheaper reads for repeated prompt prefixes | A long system prompt or fixed document set reused across calls | The 5.5 cards list explicit caching with a 512-token minimum, up to four checkpoints and 5-minute or 1-hour lifetimes |
| Provisioned Throughput | Per hour per model unit, with no-commitment, 1-month or 6-month options (varies by model) | Steady, high, predictable volume | Pay while idle; sized with your account team for some third-party models |
| Long-context pricing | Higher rates above a prompt-size threshold (Claude Haiku 5.5's card: above 100,000 tokens) | Very large prompts | A "put everything in the prompt" design can multiply cost |
The current per-token prices are on the Amazon Bedrock pricing page. Prices differ by model and change, so this lesson does not quote Claude prices on Bedrock (⚠ VERIFY on the pricing page before you budget). What you can plan today is the shape of the bill.
A worked cost estimate (illustrative rates)
Harbourline's pilot: 2,000 questions a day. Each prompt averages 3,000 input tokens (system prompt plus retrieved passages plus question) and each answer 300 output tokens. Use rates you read from the pricing page. For this example only, assume 0.10 USD per million input tokens and 0.50 USD per million output tokens (illustrative, not a quote).
Input : 2,000 x 3,000 = 6,000,000 tokens/day -> 6.0 x 0.10 = 0.60 USD
Output : 2,000 x 300 = 600,000 tokens/day -> 0.6 x 0.50 = 0.30 USD
Per day: 0.90 USD Per 30-day month: 27.00 USDNow notice what the model price does not include: the guardrail, the knowledge base, logging storage and the people. In the guardrails lesson you will see the same traffic cost more for the guardrail than for the model if you evaluate the whole prompt. Estimate the whole pipeline, not just the model.
Logging and observability
Two different records exist:
- CloudTrail records Bedrock API calls (who called what, when). It does not contain prompts. See CloudTrail for banks.
- Model invocation logging is off by default. When on, it can send the request and response bodies to CloudWatch Logs and/or S3.
A guardrail masks sensitive information in what the model sees and returns, but AWS documents that invocation logs contain the original, unmodified request whatever the guardrail did, and blocked content appears as plain text there. If you turn logging on, protect it: customer-managed KMS key, short retention, tight IAM, and CloudWatch Logs data protection for masking. Logging prompts of real customers is a data-protection decision for your privacy team.
Step-by-step implementation
List the models your Region offers
Use the CLI (below) to see the Anthropic models and the inference profiles available from us-east-1. Note which model has a profile and which has In-Region support.
Check whether you have access
For one model, call get-foundation-model-availability and read agreementAvailability. AVAILABLE means you can invoke; PENDING means the subscription is still being created.
Send one tiny Converse request
Use the CLI to send a one-line prompt with a low maxTokens. It should cost a fraction of a cent. Read the usage block in the reply.
Check the routing
Call get-inference-profile and write down every destination Region. Decide whether that is acceptable for your data classification.
AWS Console instructions
- Console → Amazon Bedrock → Model catalog. Filter by provider. Open Claude Haiku 5.5 and read the model details, the APIs supported and the programmatic-access table.
- Console → Amazon Bedrock → Playgrounds → Chat. Choose a model and try one short question. The first call to a third-party model starts the Marketplace subscription.
- Console → Amazon Bedrock → Cross-Region inference (or the model's detail page) to see the profiles. Navigation labels change; if one is missing, search the Bedrock console for "inference profiles" ⚠ VERIFY.
- Console → Service Quotas → Amazon Bedrock to see your account's per-model request and token limits.
AWS CLI
# 1. Which Anthropic models exist in this Region? Needs bedrock:ListFoundationModels.
aws bedrock list-foundation-models --by-provider anthropic \
--query "modelSummaries[].[modelId,modelName]" --output table \
--profile learn-sandbox --region us-east-1
# 2. Which cross-Region inference profiles can I call from this Region?
aws bedrock list-inference-profiles --type-equals SYSTEM_DEFINED \
--query "inferenceProfileSummaries[?contains(inferenceProfileId, 'haiku-5-5')].[inferenceProfileId,inferenceProfileName]" \
--output table --profile learn-sandbox --region us-east-1
# 3. Where can that profile route my request? Read every modelArn: each is a destination Region.
aws bedrock get-inference-profile --inference-profile-identifier us.anthropic.claude-haiku-5-5 \
--query "models[].modelArn" --profile learn-sandbox --region us-east-1
# 4. Is my account entitled to the model? (needs AWS CLI 2.27.42 or later)
aws bedrock get-foundation-model-availability --model-id anthropic.claude-haiku-5-5 \
--profile learn-sandbox --region us-east-1
# 5. One tiny Converse call. maxTokens caps the answer and therefore the cost.
aws bedrock-runtime converse --model-id us.anthropic.claude-haiku-5-5 \
--messages '[{"role":"user","content":[{"text":"Reply with the single word: ready"}]}]' \
--inference-config '{"maxTokens":20,"temperature":0}' \
--profile learn-sandbox --region us-east-1Model IDs above come from the model cards of 2026-11-18 (⚠ VERIFY: IDs and profile availability change). If a command fails with a validation error about on-demand throughput, you used a bare model ID where only a profile works.
Infrastructure as Code
Invocation logging should be turned on deliberately, with encryption and retention, never left to chance. The examples create an encrypted log group with a retention period; wiring the logging configuration itself is shown with the Terraform resource.
using Amazon.CDK;
using Amazon.CDK.AWS.KMS;
using Amazon.CDK.AWS.Logs;
using Constructs;
namespace Harbourline.GenAi.Infra;
public sealed class BedrockLoggingStack : Stack
{
public BedrockLoggingStack(Construct scope, string id, IStackProps? props = null) : base(scope, id, props)
{
// A customer-managed key so the bank controls who can read prompt logs.
var key = new Key(this, "LogKey", new KeyProps
{
EnableKeyRotation = true,
Description = "Encrypts Bedrock invocation logs (Lab m16)",
});
// Short retention: prompts are sensitive, so keep them only as long as the investigation need.
_ = new LogGroup(this, "InvocationLogs", new LogGroupProps
{
LogGroupName = "/harbourline/m16/bedrock-invocations",
Retention = RetentionDays.ONE_MONTH,
EncryptionKey = key,
RemovalPolicy = RemovalPolicy.DESTROY, // lab only
});
// Amazon.CDK.Tags avoids the clash with Stack.Tags.
Amazon.CDK.Tags.Of(this).Add("Project", "cea-lab");
Amazon.CDK.Tags.Of(this).Add("Lab", "m16-l1");
Amazon.CDK.Tags.Of(this).Add("Environment", "learn");
Amazon.CDK.Tags.Of(this).Add("Owner", "your-name");
}
}The log group's resource policy and the Bedrock logging role must also allow Bedrock to write; the L1 construct for the logging configuration is CfnModelInvocationLoggingConfiguration ⚠ VERIFY property names in your CDK version.
Complete code
This lesson is mostly reading and CLI work. The first full C# example that calls a model is in Calling Bedrock from C#, and the complete tested code is in Lab 16.1.
Code explained line by line
For the CDK example:
new Key(...)withEnableKeyRotation = truemakes a customer-managed KMS key that rotates, so key policy, not AWS-managed defaults, decides who can decrypt logs.new LogGroup(...)withONE_MONTHsets retention. Without it, CloudWatch keeps logs forever, which the conventions for these labs forbid.RemovalPolicy.DESTROYlets the lab delete the group on teardown. A production stack would retain it.- The four
Amazon.CDK.Tags.Of(this).Add(...)calls apply the mandatory lab tags. Inside aStack, writingAmazon.CDK.Tags.Of(this)fails to compile becauseTagsalso names a property of the stack, so the full namespace is required.
Security considerations
⚠ Learning shortcut — not for production
The lab uses us-east-1 and a US inference profile with fictional data, so nobody has to answer a data-residency question. A real UK bank decides the processing Regions with legal and compliance first (for example an eu. profile called from London), checks every destination Region with GetInferenceProfile, restricts Regions with Service Control Policies, and records the decision in its AI register.
- Least privilege per model. Allow
bedrock:InvokeModelon named model or inference-profile ARNs, notbedrock:*on*. - Block what you have not reviewed. Because access is automatic on first use, use SCPs to deny invocation of unreviewed models.
- Private network path. Use a VPC interface endpoint for
bedrock-runtimeso traffic stays on the AWS network ⚠ VERIFY the endpoint service name in your Region. - Logs are data. Invocation logs hold prompts. Encrypt, shorten retention and restrict reads.
- Third-party terms. For third-party models, first use means accepting the provider's End User License Agreement. A bank's procurement and legal teams may need to review it first.
Banking use case
Harbourline's architecture board sets three rules for the GenAI platform. (1) Only a short list of model IDs may be invoked, enforced by an SCP. (2) Production uses eu. profiles called from London and the destination Regions are recorded in the AI register after a GetInferenceProfile check. (3) Invocation logging is on only in the non-production account, with fictional data, and off in production until the privacy team has approved the retention and masking design. A developer who tries a new model gets a clear access-denied message, files a request, and the model enters the register after review.
Common mistakes
- Using a bare model ID where only a profile works. The error mentions on-demand throughput. Use the profile ID from the model card.
- Following an old tutorial that says "enable model access". In commercial Regions, access is enabled on first use; the missing piece is usually IAM or the Marketplace permission.
- Assuming the profile prefix equals the data boundary. Verify destinations with
GetInferenceProfile. - Forgetting that logs duplicate prompts. Turn logging on without a retention and encryption plan and you have a second copy of personal data.
- Budgeting only the model. The guardrail, knowledge base and logs often cost as much as the tokens.
Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
AccessDeniedException on the first call | Missing aws-marketplace:Subscribe permissions, no payment method, or the Anthropic use-case form not done (older Anthropic models) | Fix the prerequisite, wait a few minutes, call get-foundation-model-availability |
AccessDeniedException persists although prerequisites are done | Account-level access not granted | AWS documents contacting AWS Sales for additional access options |
ValidationException mentioning on-demand throughput | Bare model ID for a model that needs an inference profile | Use a geo or global profile ID |
| Works in one Region, fails in another | Model or profile not available there, or an SCP blocks a destination Region | Check the model card's regional table and your SCPs |
ThrottlingException | Account quota for that model reached | Request a quota increase or lower concurrency |
| Cost Explorer shows no "Bedrock" line | Third-party model charges appear under the provider | Filter by the provider's service name |
Cost and cleanup
Reading the catalogue and running the CLI commands in this lesson cost nothing except the final converse call, which is a handful of tokens (a fraction of a cent). The CDK and Terraform examples create a KMS key (about 1 USD per month while it exists ⚠ VERIFY) and a log group, so delete them after the exercise.
# Delete the lab stack (CDK) or run terraform destroy
cdk destroy BedrockLoggingStack --profile learn-sandbox
# or
terraform destroy
# Confirm nothing tagged Project=cea-lab remains in the Region
aws resourcegroupstaggingapi get-resources --tag-filters Key=Project,Values=cea-lab \
--profile learn-sandbox --region us-east-1A KMS key enters a waiting period of 7 to 30 days before deletion; it stops billing once deleted, not once scheduled for deletion ⚠ VERIFY.
Exercises
- 🟢 Guided: run the five CLI commands. Record the model ID, the inference profile ID and every destination Region of the profile from
us-east-1. - 🟡 Challenge: repeat the profile check from
eu-west-2using aneu.profile. List the destination Regions and write one sentence on whether each is acceptable for UK customer data, and who must decide. - 🔴 Live problem: a developer reports "Bedrock says AccessDenied but the model access page does not exist". Write the checklist you would send back, in the order you would test it.
Assignment
Produce a one-page Model Intake Record template for Harbourline's AI register with these fields: model ID, provider, inference profile and verified destination Regions, launch date and end-of-life date from the model card, features used (Guardrails, Knowledge Bases), price basis, data classification allowed, approver, review date. Fill it in for one model.
Solutions
Expect a table of Anthropic model IDs, a profile such as us.anthropic.claude-haiku-5-5, and destination ARNs showing us-east-1, us-east-2 and us-west-2 (verify live, the list can change). The reason you read every modelArn is that the ARN's Region is a processing location.
From eu-west-2 an eu. profile for the Claude 5.5 models listed Frankfurt, Stockholm, Milan, Spain, Ireland, London and Paris on 2026-11-18. Whether processing in those Regions is acceptable for UK customer data is a legal and compliance decision about transfers and the bank's own policy; engineering supplies the facts and enforces the choice with SCPs. Record the decision, the date and who made it.
- Is the identity allowed
bedrock:InvokeModelon this model or profile ARN? 2. Is the ID right: profile where required, correct Region? 3. For a first call, does the role have the three Marketplace permissions and does the account have a payment method? 4. For Anthropic models earlier than Opus 4.7, was the use-case form submitted? 5. Doesget-foundation-model-availabilityshowAVAILABLE? 6. Does an SCP or permissions boundary deny the call or a destination Region? 7. If all pass, wait a few minutes, then raise it with AWS Support.
Knowledge check
Answer: bedrock-runtime runs models; the bedrock control plane lists them. A common error is calling the control-plane client to run a model.
Answer: Their cards show no In-Region support there; they are served through inference profiles (geo or global). A bare ID gives a validation error.
Answer: IAM and Service Control Policies. Access is enabled on first use, so you deny bedrock:InvokeModel for unreviewed models and allow reviewed ones.
Answer: InvokeModel with amazon.titan-embed-text-v2:0. Converse is for conversational text models; the Titan embeddings card does not list Converse support.
Answer: No. AWS documents that invocation logs hold the original, unmodified request. Protect the logs with encryption, retention and CloudWatch Logs data protection.
Interview questions
- How would you decide between on-demand and provisioned throughput? On-demand for pilots and variable traffic; provisioned only when volume is steady and high enough that reserved capacity beats per-token pricing, remembering you pay while idle.
- A model call fails with an access error only the first time. Why? The first invocation of a third-party model starts a background Marketplace subscription that needs permissions and a payment method; after it completes, calls succeed.
- What is cross-Region inference and what is its compliance risk? It routes requests across Regions to improve availability and throughput. The risk is processing in Regions you did not intend, so verify destinations and restrict with SCPs.
- What belongs in a GenAI platform's logging design? CloudTrail for API calls always; invocation logging only with a reviewed retention, encryption and masking design, because it stores prompts.
Certification practice
A team needs to call several different foundation models from one application, with the ability to swap models by changing configuration. Which AWS service and API are the BEST fit?
A. Amazon SageMaker real-time endpoints, with a separate client per model B. Amazon Bedrock with the Converse API C. AWS Lambda with each provider's public API D. Amazon Comprehend
Answer: B. Bedrock offers many providers behind one API and Converse gives a consistent request shape. A requires you to host each model; C bypasses AWS controls and billing; D is a different, task-specific service.
A bank must keep inference within a specific geography. A developer uses an inference profile with a geographic prefix. What should the architect do to confirm the data boundary?
A. Rely on the prefix in the inference profile ID
B. Call GetInferenceProfile from each source Region and review every destination Region, and restrict Regions with SCPs
C. Enable model invocation logging
D. Use the bedrock-mantle endpoint
Answer: B. The documentation advises verifying destinations rather than trusting the prefix, and SCPs enforce the limit. A is not sufficient; C records prompts but does not control routing; D is an alternative endpoint and does not answer the residency question.
A workload sends the same 6,000-token instruction block with every request. Which TWO actions reduce cost most directly?
A. Use prompt caching for the repeated prefix
B. Move to a model with a smaller context window regardless of quality
C. Shorten the prompts and cap maxTokens to what the answer needs
D. Turn on model invocation logging
E. Buy provisioned throughput for an unpredictable pilot
Answer: A and C. Caching makes repeated prefix reads cheaper and capping and trimming reduces billed tokens. B can break quality; D adds cost and risk; E commits spend for traffic you cannot predict.
Completion checklist
- I can say which Bedrock endpoint a runtime call, an admin call and a knowledge-base query use
- I read the Haiku 5.5 or Sonnet 5.5 card and found its model ID, profile IDs and service tiers
- I explained how model access works now and what replaced the tick-box control
- I produced a cost estimate that includes more than model tokens
- I ran the cleanup steps and confirmed nothing tagged
Project=cea-labis still billing
Key takeaways
- Use
bedrock-runtimeand Converse by default; use InvokeModel for embeddings and model-specific bodies. - The Claude 5.5 models are called through inference profiles in
us-east-1; verify where each profile routes before you decide a data boundary. - Model access is automatic on first use, so enforce your model allow-list with IAM and SCPs and plan for the Marketplace permissions.
- Third-party model charges appear under the provider, and the bill is more than tokens.
- Invocation logs hold the original prompts: design them like personal data.
Further reading
- Models at a glance: current models, IDs, Regions and features.
- Request access to models: the current access process and permissions.
- Supported Regions and models for inference profiles: how profiles route.
- Amazon Bedrock pricing: current prices.
- Next: Calling Bedrock from C#.
Independent learning resource — not affiliated with, endorsed or sponsored by Amazon Web Services. AWS and related marks are trademarks of Amazon.com, Inc. or its affiliates. All banking data in examples is fictional. Sample architectures are for learning and are not automatically compliant with GDPR, PCI DSS or any banking regulation.
GenAI in plain language
Explain foundation models, tokens, context windows, embeddings, RAG and agents in plain words, and say why a model's answer can be confidently wrong.
Calling Bedrock from C#
Call a Bedrock model from .NET 10 with the Converse API, stream the answer, handle throttling and guardrail outcomes, and grant a role only the model permissions it needs.