Moving Intuit Mint to AWS – the last mile
summary
Moves Mint from self-hosted datacenters to AWS, migrating ~70 TB of customer financial data for 22 million users and building encryption at three layers: network encryption, application-layer field encryption and DM‑Crypt for EBS. Secrets live in an internal Intuit Secret Service. AWS Import/Export failed for shards so data copies use tsunami over UDP. Latency comes from cross‑AZ hops and encryption; solved with aggressive caching, instance type tuning and an internal metadata API to avoid AWS throttling. Infrastructure is CloudFormation driven, SaltStack bootstrapping, per‑branch stack testing and automated EBS/IOPS resizing that cut costs to about one quarter.
AI-written summary · about
chapters (9)
- 0:00Introduction to Mint and AWS
- 2:39Security and encryption
- 5:38Addressing latency challenges
- 7:39Data migration strategy
- 9:14Cost optimization techniques
- 12:26AWS implementation details
- 15:18Infrastructure as code
- 19:36High availability architecture
- 21:06Q&A and closing remarks
related talks
18mIntuit's journey to the cloud: Protecting native services
01h 03mContinuous Security in the Cloud
47mCloud success unlocked: Helvetia’s journey(BIZ201)
31mBest practices to jump-start your migration to AWS
23mHow Atlassian is migrating 40PB data with 99.99% reliability
20mMigration of 300 microservices from AWS Cloud to
30mLeaping from Mainframes to AWS: Technology Time Travel in the Government
32mDive into technical decisions from successful migrations