Il y a eu des probl\u00e8mes techniques chez AWS, la solution cloud de Amazon, qui est utilis\u00e9e par beaucoup de sites et services web, notamment Signal, l’excellente messagerie instantan\u00e9e.<\/p>\n\n\n\n
Meredith Whittaker, CEO de Signal et pr\u00e9sidente de la Fondation associ\u00e9e, a fait un thread sur Mastodon pour traiter le sujet des gens (dont je faisais partie) qui d\u00e9barquent sur le fait que Signal utilisent AWS, et une partie de ces gens sont tr\u00e8s critiques qu’une application comme Signal utilise ce service appartenant \u00e0 Amazon.<\/p>\n\n\n\n
Voici le texte int\u00e9gral du thread<\/a>, d\u00e9sol\u00e9 c’est en anglais. <\/p>\n\n\n\n THREAD: It\u2019s surprising to me that so many people were surprised to learn that Signal runs partly on AWS (something we can do because we use encryption to make sure no one but you\u2013not AWS, not Signal, not anyone\u2013can access your comms).<\/p>\n\n\n\n It\u2019s also concerning. 1\/<\/p>\n\n\n\n Concerning, bc it indicates that the extent of the concentration of power in the hands of a few hyperscalers is way less widely understood than I\u2019d assumed. Which bodes poorly for our ability to craft reality-based strategies capable of contesting this concentration & solving the real problem. 2\/<\/p>\n\n\n\n The question isn\u2019t \u00ab\u00a0why does Signal use AWS?\u00a0\u00bb It\u2019s to look at the infrastructural requirements of any global, real-time, mass comms platform and ask how it is that we got to a place where there\u2019s no realistic alternative to AWS and the other hyperscalers. 3\/<\/p>\n\n\n\n Running a low-latency platform for instant comms capable of carrying millions of concurrent audio\/video calls requires a pre-built, planet-spanning network of compute, storage and edge presence that requires constant maintenance, significant electricity and persistent attention and monitoring. 4\/<\/p>\n\n\n\n Instant messaging demands near-zero latency. Voice and video in particular require complex global signaling & regional relays to manage jitter and packet loss. These are things that AWS, Azure, and GCP provide at global scale that, practically speaking, others (in the western context) don\u2019t. 5\/<\/p>\n\n\n\n This isn’t \u2018’renting a server.’ It’s leasing access to a whole sprawling, capital-intensive, technically-capable system that must be just as available in Cairo as in Capetown, just as functional in Bangkok as Berlin. Particularly given the high stakes use cases of many who rely on Signal. 6\/<\/p>\n\n\n\n Such infrastructure costs billions and billions of dollars to provision and maintain, and it\u2019s highly depreciable. In the case of the hyperscalers, the staggering cost is cross-subsidized by other businesses\u2013themselves also massive platforms with significant lockin. 7\/<\/p>\n\n\n\n Meaning that infrastructure like AWS is not something that Signal, or almost anyone else, could afford to just \u201cspin up.\u201d Which is why nearly everyone that manages a real-time service\u2013from Signal, to X, to Palantir, to Mastodon\u2013rely at least in part on services provisioned by these companies. 8\/<\/p>\n\n\n\n But even if Signal had the billions needed to recreate AWS, it\u2019s not just about money. The talent to run these systems is rare & concentrated. The expertise, the tooling, the playbooks, the very language of modern SRE came out of these hyperscalers, and is now synonymous with ‘the cloud.’ 9\/<\/p>\n\n\n\n o, yes, Signal runs on AWS. It also runs on your phone, which runs on iOS (Apple) or Android (Google). And on Dekstop, via Windows (Microsoft). Each of these presents similar dependencies on large entrenched tech companies, and concomitant barriers and risks. 10\/<\/p>\n\n\n\n In short, the problem here is not that Signal \u2018chose\u2019 to run on AWS. The problem is the concentration of power in the infrastructure space that means there isn\u2019t really another choice: the entire stack, practically speaking, is owned by 3-4 players. 11\/<\/p>\n\n\n\n So, Signal does what we can to provide a service w integrity in the concentrated ecosystem we’re working in. We protect your comms w end-to-end encryption, so that we can use AWS and others as a highway across which to send Signal data in ways that don\u2019t let AWS, or anyone else, gain access. 12\/<\/p>\n\n\n\n To conclude: my silver lining hope is that AWS going down can be a learning moment, in which the risks of concentrating the nervous system of our world in the hands of a few players become very clear. And that this can help us craft ways of undoing this concentration and creating real choice ❤️ 13\/<\/p>\n\n\n\n En gros, elle explique que permettre \u00e0 une application de messagerie de fonctionner dans le monde entier, demande \u00e0 la fois une infrastructure ultra performante, et l’expertise pour la mettre en place et la faire fonctionner. Et \u00e7a, ben \u00e7a co\u00fbte des milliards. Voil\u00e0. Donc ce qu’il faut remettre en cause, c’est pas seulement que Signal utilise AWS, c’est que beaucoup de fonctions des aspects d’Internet et du web sont aujourd’hui hyperconcentr\u00e9es dans les mains de quelques acteurs.<\/p>\n\n\n\n Bref. Je suis fan de Meredith, elle est brillante. Et \u00e9videmment le premier toot en r\u00e9ponse \u00e0 son thread, c’est un mec qui vient la mansplain… <\/p>\n","protected":false},"excerpt":{"rendered":" Il y a eu des probl\u00e8mes techniques chez AWS, la solution cloud de Amazon, qui est utilis\u00e9e par beaucoup de sites et services web, notamment Signal, l’excellente messagerie instantan\u00e9e. Meredith Whittaker, CEO de Signal et pr\u00e9sidente de la Fondation associ\u00e9e, … Continuer la lecture