Get the weekly research letter
Companies change their terms quietly. We read every version and catch what actually changed. One email a week on the changes that matter and what they mean. No account.
Upon suspension or termination of beta service access, customer content stored in beta services may be deleted or become inaccessible, and the terms do not guarantee migration of that content to generally available service versions.
This analysis describes what AWS Bedrock's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology
This provision establishes that customer content in beta services is at risk of permanent loss upon termination of beta access, with no contractual obligation for AWS to migrate or preserve that content, creating a material data retention and business continuity risk for customers using beta services in production contexts.
The updated terms establish new restrictions on how AWS Capacity Reservations may be used. Specifically, customers purchasing On-Demand Capacity Reservations can no longer resell them to other parties, and AWS reserves the right to cancel the purchase or terminate running instances if the company suspects resale activity. For Capacity Blocks for ML, the grace period before instance termination increased from 30 minutes to 60 minutes for UltraServer instance types, allowing slightly more time to complete workloads. The Amazon Sidewalk qualification program was renamed and simplified, but the underlying security and operational requirements remain in effect.
View change record →The updated terms establish a formal framework for AWS Bedrock's free exploration services, clarifying the operational boundaries and responsibilities. AWS reserves the right to discontinue these services at any time without prior notice, meaning customers cannot rely on their continuation for production planning. Customers are solely responsible for testing, deploying, and maintaining any code, documents, or AI solutions AWS provides, including determining whether those solutions comply with applicable law. AWS retains the right to develop competing products based on content it creates during these engagements, though this does not override existing non-disclosure agreements. Customers are prohibited from requiring AWS personnel to sign additional terms as a condition of receiving free services, and any such documentation signed by AWS personnel is void.
View change record →The updated terms establish new data-sharing mechanisms for users of Anthropic models on Amazon Bedrock. Specifically, AWS now explicitly authorizes notification to Anthropic of metadata present in requests sent to certain Anthropic products (e.g., Claude Code, computer use features), enabling Anthropic to conduct product-level usage attribution. Additionally, the terms introduce AWS WAF AI traffic monetization, which permits AWS to facilitate payment transactions between content publishers and buyers by sharing pricing, payment, and configuration information with payment providers and facilitators; the updated terms clarify that AWS does not provide regulated financial services and is not a party to fund flows, and that users' interactions with payment providers are governed by separate terms between the user and those parties. Users employing these features should review what metadata may be embedded in their requests and understand their own obligations to payment providers.
View change record →Under these terms, content stored in beta services or beta regions may be deleted or become permanently inaccessible following suspension or termination of beta access, and AWS is not obligated to migrate that content to generally available versions of the service.
Cross-platform context
See how other platforms handle Beta Service Content Deletion on Termination and similar clauses.
Compare across platforms →Monitoring
AWS Bedrock has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 25 platforms.
"Unless otherwise communicated to You, any Beta Service or Beta Region made available to You is provided for evaluation purposes and should not be used for processing sensitive data. Notwithstanding anything to the contrary in the Agreement, after suspension or termination of your access to or use of any Beta Service or Beta Region for any reason, (a) you will not have any further right to access or use the applicable Beta Service or Beta Region, and (b) Your Content used in the applicable Beta Service or Beta Region may be deleted or inaccessible and Your Content may not be migrated over to a generally available version of the applicable Beta Service or Beta Region.Excerpt from AWS Bedrock's AWS Service Terms
REGULATORY LANDSCAPE: This provision does not directly implicate a specific regulatory framework but engages data retention obligations under GDPR Article 5(1)(e) (storage limitation), industry-specific record-keeping requirements, and contractual data preservation obligations that customers may owe to their own clients. Where beta services are used to process regulated data contrary to the provision's advisory against processing sensitive data, the deletion risk may engage HIPAA data retention requirements, financial services record-keeping rules, or GDPR data subject rights obligations. GOVERNANCE EXPOSURE: High for customers who have deployed beta services in production or near-production environments or who have stored business-critical or regulated data in beta services. The provision explicitly advises against processing sensitive data in beta services, meaning customers who do so assume the associated data loss risk. AWS may terminate beta access without notice as stated in Section 2.4. JURISDICTION FLAGS: Customers subject to GDPR data retention and erasure obligations should evaluate whether beta service content deletion could conflict with data subject access requests or retention schedules. Customers in regulated industries (healthcare, financial services) with mandatory data retention periods should assess whether any beta service usage implicates those requirements. CONTRACT AND VENDOR IMPLICATIONS: Customers' own data processing agreements with downstream clients may contain data preservation and return obligations that could be breached if content stored in beta services is deleted upon termination. Procurement policies should include controls to prevent production or sensitive data from being processed in beta services. Business continuity plans should account for the possibility of sudden beta service termination and content loss. COMPLIANCE CONSIDERATIONS: IT governance teams should implement policies restricting use of beta services for production workloads and sensitive data processing. Data mapping exercises should identify any customer data currently stored in beta services and assess the risk of deletion. Customers should establish independent backup procedures for any content stored in beta services, as the terms do not guarantee preservation or migration.
This provision establishes that customer content in beta services is at risk of permanent loss upon termination of beta access, with no contractual obligation for AWS to migrate or preserve that content, creating a material data retention and business continuity risk for customers using beta services in production contexts.
Under these terms, content stored in beta services or beta regions may be deleted or become permanently inaccessible following suspension or termination of beta access, and AWS is not obligated to migrate that content to generally available versions of the service.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by AWS Bedrock.