/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

days · browse · Enter similar · o open

Under regulatory pressure around vendor lock-in, AWS follows Google in dropping egress fees for moving data out of its cloud; Microsoft Azure's fees remain

Amazon's cloud computing subsidiary AWS has revealed that it will allow customers to transfer their data out of its ecosystem with no so-called “egress fees” attached.

TechCrunch Paul Sawers

Context & Ripple Effects

Google Cloud had already removed charges for customers leaving for rival services in January, creating a clear competitive benchmark for AWS. AWS's move narrows the pricing distinction created by Google Cloud's earlier exit-fee removal amid scrutiny of cloud switching barriers.

The decision also fits a broader pattern of providers adjusting terms that can make workloads harder to move: Microsoft had previously relaxed European cloud licensing restrictions after complaints from rivals. Egress pricing is now another visible test of portability.

First-order effects

  • AWS customers can move data out of AWS without egress charges, removing a direct cost from an exit or migration decision.
  • AWS now matches Google on this specific portability measure, while Azure remains the major named provider still charging for outbound data transfers.

Second-order effects

  • Azure faces greater pressure to justify or revise its egress pricing, since customers can more readily compare the cost of leaving across the three large clouds.
  • For cloud buyers, migration and multi-cloud planning can put more weight on application, support, and operational costs rather than a data-transfer exit charge at AWS or Google.

Third-order effects

  • If providers continue removing exit fees under competitive and regulatory pressure, cloud competition may shift from monetizing switching friction toward retaining customers through integrated services and workload economics.
  • The change strengthens portability as a policy and procurement issue, though eliminating one transfer charge does not by itself remove the technical and contractual barriers to changing clouds.

The trend: Hyperscale cloud providers are being pushed to make customer portability more credible as lock-in becomes a sharper competitive and regulatory concern.

Discussion

  • @iaasgeek Guillermo Ruiz on x
    We believe in customer choice, including the choice to move your data out of #AWS 👇🏻
  • @quinnypig Corey Quinn on x
    Wait, that's what the blog post says, but the FAQ says: “After your move away from AWS services, within the 60-day period, you must delete all remaining data and workloads from your AWS account, or you can close your AWS account.” Okay, so which is it? One of those is great.
  • @quinnypig Corey Quinn on x
    Okay, the “we don't require you to close your account or change your relationship with AWS in any way” means this is potentially meaningful to customers in ways that Google's equivalent isn't. This is a solid change. https://aws.amazon.com/...
  • r/technews r on reddit
    AWS follows Google in announcing unrestricted free data transfers to other cloud providers
  • r/aws r on reddit
    Free data transfer out to internet when moving out of AWS