AWS architecture · Build
AWS architecture for the load you have and the next step
For products on AWS that outgrew their setup, we size from measured load and design for the bill. One identity system went from $24,000 to $2,000 a month.
EngagementHourly · remote
Hours9–18 CET · 4 h overlap
StackAWS · EC2 · S3
Proof3 case studies
The service in 4 parts
01 · Who it’s for
A product that is already on AWS or moving there, and needs someone to decide what runs where and what it will cost. Most often it is a system that grew faster than anyone revisited its setup.
02 · What we’ve built
- A West African national identity system whose bill for the same workload came down from $24,000 to $2,000 a month, with nothing switched off.Case study 14 →
- Passport applications captured offline on company phones that can be wiped remotely. The national registry can only be reached with keys, single-use tokens and IP allow-listing.Case study 09 →
- A US marketplace moved from shared hosting onto AWS in two months, and later onto containers with autoscaling, without a single outage.Case study 04 →
- Serverless WebSockets on API Gateway, Lambda and Redis, priced in eighteen scenarios. Below about a thousand users, traffic hardly registers on the bill, which is almost all Redis and the VPC endpoint.Blog post →
03 · How we work
01 · SIZINGInstances and databases are sized from observed use, so a generous guess made at launch doesn’t stay on the bill once the real load is known.
02 · COSTSWe set up a budget alarm in the first week. It costs nothing, and it catches overspending that never shows up as an error. On the identity system, an alarm would have caught the infinite loops in their first week instead of their fiftieth.
04 · Stack
AWSEC2S3LambdaAPI GatewaySQSElastiCacheRedshiftCloudWatch
Proof
Where we’ve done this before
Case study 14 · Data$24k → $2kA West African national identity system whose bill for the same workload came down from $24,000 to $2,000 a month, with nothing switched off.Read the case study →Case study 09 · Identity1 working dayPassport applications captured offline on company phones that can be wiped remotely. The national registry can only be reached with keys, single-use tokens and IP allow-listing.Read the case study →Case study 04 · MarketplaceZero outagesA US marketplace moved from shared hosting onto AWS in two months, and later onto containers with autoscaling, without a single outage.Read the case study →WritingServerless WebSocket costs: connection minutes rarely dominateServerless WebSockets on API Gateway, Lambda and Redis, priced in eighteen scenarios. Below about a thousand users, traffic hardly registers on the bill, which is almost all Redis and the VPC endpoint.Read the post →
FAQ
Questions about this service
Only up to a point, and we work out where that point is for your traffic. When we modeled WebSockets, serverless already cost more than one server at a thousand users, and more than a redundant pair by five thousand.
Yes. The West African identity system stayed live throughout and kept serving the same users while its bill came down.
Yes. We moved the marketplace’s PHP application onto AWS as it was and stabilized it there. The rewrite came after that.
Yes. The cloud cost review is a two-week written assessment at a fixed price. Architecture work after it is billed by the hour.
Next step
Describe the problem and we’ll come back with three options.
The first call takes 30 minutes, and you’re under no obligation.