AWS Security ChangesHomeSearch

AWS bedrock documentation change

Service: bedrock · 2026-03-28 · Documentation medium

File: bedrock/latest/userguide/managed-entitlements-faq.md

Summary

Clarified that deactivating or deleting grants doesn't block model access but changes billing from private offer pricing to public rates, and updated behavior when parent subscription expires

Security assessment

This change clarifies important security and billing implications of grant management. It documents that access control through grants affects billing but not actual model access, which is a security-relevant clarification about how entitlements work. However, there's no evidence this addresses a specific security vulnerability.

Diff

diff --git a/bedrock/latest/userguide/managed-entitlements-faq.md b/bedrock/latest/userguide/managed-entitlements-faq.md
index 5bb716dfa..aa06eebc2 100644
--- a//bedrock/latest/userguide/managed-entitlements-faq.md
+++ b//bedrock/latest/userguide/managed-entitlements-faq.md
@@ -67 +67 @@ A: When member accounts have active Bedrock models and their payer account distr
-A: Yes. Deactivate the grant to move it to a Disabled state. This temporarily revokes access while preserving the grant configuration. You can reactivate it later without recreating the grant.
+A: Yes. You can deactivate the grant to move it to a Disabled state. However, deactivating a grant does not block model access — the member account can still invoke the model. What changes is the billing: while the grant is disabled, the member account will be billed at public rates instead of your negotiated private offer pricing. You can reactivate the grant later to restore private offer terms without needing to recreate it.
@@ -71 +71 @@ A: Yes. Deactivate the grant to move it to a Disabled state. This temporarily re
-A: Active inference requests continue to run and complete normally. However, new requests are denied immediately once the grant is deactivated or deleted. Charges for completed work still apply to the subscribing account.
+A: The member account will continue to have model access — deleting or deactivating a grant does not interrupt the ability to invoke the model. However, without an active grant, the member account will be billed at public rates instead of any negotiated private offer pricing.
@@ -79 +79 @@ A: In AWS License Manager, you can view which accounts have grants and their act
-A: No. Deleting a grant is permanent and cannot be undone. However, you can create a new grant to the same account with the same configuration. The new grant will be independent of the deleted grant.
+A: No. Deleting a grant is permanent and cannot be undone. However, you can create a new grant to the same account with the same configuration. Model access will not be disrupted — the member account can continue invoking the model during the gap. The key impact is billing: for the duration between the grant deletion and the new grant activation, the member account will be billed at public rates rather than any negotiated private offer pricing.
@@ -83 +83 @@ A: No. Deleting a grant is permanent and cannot be undone. However, you can crea
-A: The linked accounts will lose access to the model when parent subscription expires in the management account.
+A: The linked accounts will continue to have model access when parent subscription expires in the management account. However, they will be billed at public rates rather than any negotiated private offer pricing.