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.
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 institutional analysis
Regulatory exposure, obligation analysis, escalation trigger, board language, and recommended action.
Analyst $49/moConductAtlas 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.
AWS 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.