AWS simplified its Mexico customer contracting rules on June 1, 2026. Previously, Mexico-based customers were routed to the Mexico AWS entity based on their payment method and address in two separate phases (January and February 2026). The updated terms consolidate this: as of June 1, 2026, all customers located in Mexico now contract with the Mexico-based AWS entity, eliminating the prior bifurcated approach.
The updated terms establish a single, simplified rule for Mexico-based customers: as of June 1, 2026, all customers located in Mexico contract with AWS's Mexico-based entity. This replaces the prior structure, which routed customers to the Mexico entity based on payment method and address in two separate phases (January and February 2026). The change consolidates which legal entity is party to the contract but does not state a change to service terms, availability, pricing, or obligations.
This change establishes which AWS legal entity governs the contract for Mexico-based customers, affecting invoicing, dispute resolution, and legal jurisdiction. The consolidation simplifies the prior payment-method-dependent routing but requires Mexico-located customers and their resellers to update internal vendor records and contracting systems by the June 1, 2026 effective date.
→ Review Section 12 of the updated AWS Customer Agreement to confirm the Mexico-based AWS entity name and address applicable to your account.
→ Update internal vendor records and invoicing systems to reflect the single Mexico entity assignment effective June 1, 2026.
→ Customer records and internal systems may not reflect the correct AWS contracting party as of June 1, 2026, potentially causing invoicing or contract reconciliation discrepancies.
→ Resellers or managed service providers may not have current entity information for customer communications and contract governance.
All Mexico-located customers now contract with AWS Mexico entity as of June 1, 2026, consolidating prior payment-method-dependent routing.
This change record describes what was added, removed, or modified in the document. Analysis reflects what the updated agreement states or permits. It does not constitute a legal determination about enforceability. Applicability may vary by jurisdiction. Methodology
This change simplifies AWS's contracting architecture for Mexico. Previously, payment method and address determined entity assignment across two staggered effective dates. The update unifies all Mexico-located customers under a single entity as of June 1, 2026, eliminating the prior payment-dependent routing. The change appears administrative and does not indicate modification to substantive service terms, data handling, or compliance obligations, though organizations with Mexico operations should confirm alignment between their vendor master data and the new entity assignment for invoicing and contract governance purposes.
Full compliance analysis
Obligation analysis, escalation trigger, board language, and recommended action.
Monitor: regulatory citations + obligations. Compliance: full compliance memo.
ConductAtlas provides verified policy intelligence sourced directly from platform documents. All analysis is intended to support, not replace, legal and compliance review. Record CA-C-002620.
This new provision imposes a strict monetary cap on AWS's liability, significantly limiting customer recovery to 12 months of fees paid or $25 for free services, fundamentally altering liability exposure.
This standalone provision clarifies and strengthens the exclusion of consequential damages with explicit enumeration of damage types, making the liability limitation more specific and enforceable.
This new provision imposes a strict 60-day deadline for billing disputes with automatic waiver of rights, eliminating customer ability to challenge charges beyond this window.
This new provision explicitly defines the limited scope of license rights granted to customers, restricting copying and use of AWS Content to only what is necessary for service use.
This revised provision clarifies customer ownership of content while obtaining explicit consent for collection and processing, and limits AWS's use to service provision and written agreements only.
Removal of the original limitation of liability provision was replaced with more granular provisions (Consequential Damages Exclusion and Aggregate Liability Cap), potentially shifting liability treatment.
Removal of AWS's broad content use and disclosure rights for government requests eliminates explicit legal justification for disclosing customer data without additional consent.
Removal of the explicit indemnification clause eliminates customer obligation to defend AWS against third-party claims related to customer use and content, reducing customer liability.
Removal of explicit reference to Data Processing Addendum availability and GDPR compliance specificity eliminates clear guidance on obtaining a DPA for regulatory compliance.
Removal of comprehensive fees and payment provision eliminates detail about monthly billing, fraud-based acceleration billing, payment methods, and prohibition on setoff and counterclaim.
Capitalization of 'Your' changed to match formal style conventions, but substantive meaning remains identical.
Added explicit reference to 'our affiliates' in the liability disclaimer, expanding AWS's liability shield.
Specified notification channels (Service Health Dashboard, email, Management Console) rather than general notification, providing more detailed implementation guidance.
Narrowed dispute scope from 'your use of the Service Offerings or to products or services sold or distributed by AWS or through AWS.com' to 'the Service Offerings or this Agreement' and changed 'you consent' to 'each party consents'.
Expanded to explicitly cover Your Content compliance, added requirement to comply with all policies and applicable law, and introduced sole responsibility clause for content development and operation.
Cross-platform context
See how other platforms handle similar provisions across the ConductAtlas archive.
See the full side-by-side comparison of every sentence added, removed, and modified.
🔒 Full diff — MonitorAWS updated its Customer Agreement on May 19, 2026, making 39 additions, 15 removals, and 52 modifications across 309 sentences. …
AWS updated its Privacy Notice on May 18, 2026, making four operational changes. The document added a new section titled …
Get alerted when this policy changes again — including what changed and why it matters.
Prefer a weekly summary instead?
Get the biggest policy changes across 320+ platforms every Sunday.