Signal President Meredith Whittaker Says They Had No Choice but to Use AWS
Posted2 months agoActive2 months ago
theregister.comTechstory
heatedmixed
Debate
70/100
SignalAWSCloud InfrastructurePrivacySecurity
Key topics
Signal
AWS
Cloud Infrastructure
Privacy
Security
Signal's president explains why they had to use AWS despite initial reservations, sparking debate about the trade-offs between security, cost, and practicality.
Snapshot generated from the HN discussion
Discussion Activity
Very active discussionFirst comment
27m
Peak period
24
0-12h
Avg / period
5.6
Comment distribution39 data points
Loading chart...
Based on 39 loaded comments
Key moments
- 01Story posted
Oct 27, 2025 at 11:20 PM EDT
2 months ago
Step 01 - 02First comment
Oct 27, 2025 at 11:48 PM EDT
27m after posting
Step 02 - 03Peak activity
24 comments in 0-12h
Hottest window of the conversation
Step 03 - 04Latest activity
Nov 2, 2025 at 1:15 AM EDT
2 months ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
ID: 45728920Type: storyLast synced: 11/20/2025, 7:35:46 PM
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
The advantage of bundling your service in a hyper scaler is in persuading censors that they’d rather tolerate Signal than lose AWS. This doesn’t work in China which has sophisticated alternatives, but it can help Signal hold on in other countries.
It’s ok, the world won’t end.
You might get systems that are reliable and cost a great deal less if you exit AWS.
Lose your fear, have courage, find a better cheaper faster more reliable alternative…. well pretty much anywhere.
They have convinced you this is your only choice. It is not.
You are making the claim you see a clear massive global untapped market, for lower price and higher quality cloud/global compute, that you know how to provision and serve.
Apparently Signal will be happy to hear from you.
Well then. I believe you.
There are some rare exceptions who have their own large scale infrastructure and don't depend on AWS like Hetzner in EU, Alibaba Cloud in China or Ananta Cloud in India, but this market is still emerging.
Telegram was not disrupted during the AWS crash, so they probably were not using it (or had a decent fail-over mechanism to a backup system). Telegram's user-base is two orders of magnitude larger than Signal, so 'we use AWS because we have to' argument clearly is bogus and nonsense.
It is more of a question, who would you rather read your messages ? USA or Russia ?
Because even if there is E2E encryption and an open source client, unless you review it and compile it yourself, there is nothing to say that your messages are relayed to some agency's datacenter after decryption. The USA has all the legal framework necessary to achieve that with the tremendous power of the "intelligence" agencies, and Russia.. well.. doesn't even need that.
The public-facing story around Telegram is performative PR, which could be explained by the exact reasons listed in the parent comments: association with the Russian state had hindered VK growth besides the CIS region.
Despite there founder crying on twitter[1] how horrible and distopian chat control client side scanning to bypass E2EE would be, telegram is still only offering hidden and limited opt-in E2EE instead of making it global default like signal.
[1] https://twitter.com/durov/status/1976420399970701543
How would you know this? If they access the data from the platforms server you would never know unlike with obvious forceful physical seazure. The point of E2EE is that the weakest link, the server, is removed. It increases the required threat model from simple dragnet surveillance to high effort targeted attacks. If the client is insecure nothing can protect your data and signal has said that many times.
I don't see how the debate about requiring a phone number is relevant to this discussion since telegram does too.
The weakest link is not the server. The weakest link is the user device. There is no security without anonymity.
>There is no security without anonymity.
You don't understand what these words mean. You can be surveilled 100% by bodyguards and cameras to be secure but have 0% anonymity (or privacy).
WhatsApp grew to much larger scale than Signal: self hosted, not on cloud. Running Erlang and FreeBSD.
Telegram grew to much larger scale than Signal: self hosted, not on cloud (dc IPs here: https://docs.pyrogram.org/faq/what-are-the-ip-addresses-of-t...). They set up their datacenters carefully to make it hard for governments to access data via legal mechanisms, something Signal didn't bother with.
Threema, similar concept to Signal: self hosted, not on cloud.
Every other messaging app before these bunch? AIM, ICQ, MSN Messenger, iMessage... self hosted, not on cloud.
The idea there is no choice should be hyperbole but it seems she might really believe that. It says a lot that Signal is run by such a person.
But you're kidding yourself and everyone else to state an answer. It's amazing how HN commenters love to use leading FOSS projects, like Signal and Mozilla, as targets for their performative takedowns - it causes real harm to the most important projects around. Taken seriously, the parent comment's arguments contain no engineering, and their foundation is a lot of assumptions and arrogance:
No engineering is required to understand those arguments. No competent practicing engineer would offer a serious opinion about an organization and technical issue that they haven't directly examined.
The assumptions are a long list: The totality of reasons that Signal has, as an organization, to choose AWS. The people who made the decision:likely others at Signal were heavily involved, and the CEO's role is unknown to us - maybe just approval - and possibly it was before Whittaker was there. Signal having unlimited flexibiliy in requirements and resources to optimize for this issue.
The arrogance is that we know better than Signal's CEO and team members, who are intimately familiar with the project, the organization, its requirements, its resources. The parent doesn't address most of those essentials.
But maybe the parent is performative - that's not illegal, but ugh, pick on the big guys; punch up, not down.
> The question isn’t "why does Signal use AWS?" It’s 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’s no realistic alternative to AWS and the other hyperscalers
> Which is why nearly everyone that manages a real-time service–from Signal, to X, to Palantir, to Mastodon–rely at least in part on services provisioned by these companies
Which is both dishonest and stupid. She's claiming it's impossible to run an app like Signal outside of public cloud despite all her main competitors doing so. That's why she lists a bunch of non-competitors to try and support her argument.
So it's ironic you say it's arrogant for us to judge their requirements, because we know their requirements. Signal's design is fully open and the requirements of such platforms are well known. It's rather Whittaker's thread which is the height of arrogance. Her response to criticism of downtime is to be "concerned" at the ignorant users who don't "understand" the "concentration of power" and to "explain" to people why it's impossible to do better even as her competitors all do it. It's practically gaslighting.
> we know their requirements. Signal's design is fully open and the requirements of such platforms are well known.
You're kidding yourself. 'Open' doesn't mean you understand them on a level to draw real engineering conclusions. Smart people would wonder at the questions you raise, and ask people who do know. Maybe someone from Signal is around here - but who would respond to someone that calls them stupid?
The Mozilla/Mitchell Baker vibes are strong here. It indicates a lot about Signal that its leadership doesn't understand who their competitors are (she thinks its Palantir?!), nor the basics of running a messaging service, nor even what her imagined competitors really do. X runs its own datacenters, Palantir is running in every cloud. They don't support her argument.
And I've worked on two web scale products with billions of users, both of them had 5 9's uptime. HN is full of people who have. This stuff isn't rocket science. The first reply on Mastodon points out that even Tor has better uptime than Signal.
She's saying this stuff because of her social background, not technical reality. It's just AWFL activist buzzphrases strung together, the sort of rhetoric that served her well in the past to climb the ladder. She's "concerned" and "surprised" that angry users don't understand the "power" of Amazon which "bodes poorly for our ability to craft reality-based strategies capable of contesting this concentration". She acknowledges "the high stakes use cases of many who rely on Signal" but has no interest in meeting those high stakes by driving the execution of an ordinary HA/multi-cloud/multi-region project, of the type that happens all the time in any bank. That's impossible, literally "there isn't really another choice", and also unnecessary because Signal is a mobile app so it depends on Android and that's the same thing as a depending on a cloud (what?). Her conclusion: "my silver lining hope is that AWS going down can be a learning moment", by which she means a learning moment FOR OTHER PEOPLE.
Can you imagine Mark Zuckerberg or Pavel Durov crying about Amazon and demanding that their outage be lesson to their users? It's unthinkable. They'd be in the conference rooms with the engineers figuring out how to ensure it never happens again. They might publish a public post mortem to build confidence. That's because they are engineers. Whittaker isn't so she publishes heart emojis and expresses concern at how little sympathy she's getting. No, this is 100% bad news for Signal. It's got totally feminized leadership that responds to the orgs own mistakes with demands for empathy, not fast paced engineering.
> She's saying this stuff because of her social background, not technical reality.
> Can you imagine Mark Zuckerberg or Pavel Durov crying
> Whittaker ... publishes heart emojis and expresses concern
The gamergate vibes are strong here.
> She's saying this stuff because of her social background, not technical reality.
Always look first in the mirror.
No legal mechanism can access proper encyrpted data, something Telgram has to bother
2. My donations to Signal apparently also go to Bezos
They had choices beyond just other hyperscalers. Rolling their own probably would have meant both capex and opex, which reduced to opex in AWS and so made both logical and financial sense. In risk terms you might have said (before the incident) it was also the best way to lay off risk, but it turns out "too big to fail" actually doesn't mean what it says on the label.
I still back signal over all the other choices. I wasn't looking for an excuse to leave, and as a strawman if you leave signal because chosing AWS as a backend "was unwise" or "was the wrong choice" I think you're reading the signal wrong (sorry)
I would add that "the register" has a house style, and it's not tending to damp down. It likes to be inflammatory, it's tagline "biting the hand which feeds IT" rings true. I enjoy reading it, and I've had work repeated in it, but I also read it with a jaundiced eye. I don't like the comments section it's a minefield of in-group language, memes, bad behaviour.