Menu

Post image 1
Post image 2
Post image 3
1 / 3
0

The Architecture You Did Not Design: How AWS' Real Lock-In Lives in IAM, Not Egress

DEV Community·Vivian Voss·18 days ago
#wnRL8TJN
Reading 0:00
15s threshold

In the Net, Episode 03 In March 2024 AWS announced that it would waive data-egress fees for customers wishing to leave. The press release was elegant, the wording generous, the timing precise: less than two months after the EU Data Act came into force, with its Article 25 obligations on cloud switching, and rather earlier than the moment in January 2027 when the same regulation will prohibit switching charges altogether. Two years on, the egress bill is no longer the largest cost of leaving AWS. The egress bill, in fact, is not even the main reason customers do not leave. The architecture is. This is the third episode of In the Net : a series on the documented mechanics of vendor lock-in. The premise has not changed. Every platform tells you how to come in. The architecture tells you whether you can leave, what it does with what you build inside it, and how much of what you built belongs to you when you wish to walk out.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.

Read More