# The Bedrock AccessDenied banner is not the verdict

A model can answer in Bedrock while the red Marketplace AccessDenied banner is on screen. That
answer is not proof the model is enabled, and the banner is not proof it is blocked.

A colleague could not use Claude models in a Sandbox account. His playground showed the banner about
missing aws-marketplace permissions, and in the same screenshot the model had answered. Someone else
said the error was not linked to Marketplace access. I had to find out who was right.

CloudTrail fooled me first. A ConverseStream event with no errorCode looks like success. It only
means the request was routed. A model that was never enabled logged no error, then AccessDenied three
seconds later. Errors during a stream are not logged. I also quoted event times as UTC when they were
local time, one hour off.

One real prompt settled it. I sent "hello" through the runtime API with a us. inference profile.
Haiku 5.5 answered at once. Haiku 4.5 showed the same banner on its first call, from an SCP-exempt
admin role, then answered on retry a few minutes later.

The AWS doc on automatic model access explains the pattern. The first call to a paid third-party
model starts the Marketplace subscription in the background, up to 15 minutes. During that window a
call can succeed and still show the banner. If the caller is denied aws-marketplace:Subscribe, the
subscription fails and later calls return AccessDenied.

The fix is to enable each model once per account with a principal that may subscribe. After that,
normal roles invoke without Marketplace permissions. Use the us. or global. profile, because a plain
model ID fails with "on-demand throughput isn't supported".

Prove a model works with one real prompt. Keep CloudTrail for finding denials, and check the timezone
before you quote times to someone reading the same logs.
