Amazon's cloud service crash permanently lost data. Think this has implications for EDA?
Today, MSNBC’s Technolog carries an article by Henry Blodget that discusses another aftermath of the Amazon EC2 (Elastic Compute Cloud) services failure: lost data. The article quotes a letter from Amazon stating:
“A few days ago we sent you an email letting you know that we were working on recovering an inconsistent data snapshot of one or more of your Amazon EBS volumes. We are very sorry, but ultimately our efforts to manually recover your volume were unsuccessful. The hardware failed in such a way that we could not forensically restore the data.”
As a result, one client of Amazon’s EC2 services, Chartbeat, sent this note to its customers:
“Approximately 11 hours of historical data wasn’t recoverable and will appear as small gaps in the timeline. Our development team is also hard at work to limit the impact of any future AWS interruptions.”
Now consider how the letter might have been worded if Chartbeat were an SoC design house:
Related Semiconductor IP
- MIPI SoundWire I3S Peripheral IP
- Post-Quantum ML-KEM IP Core
- MIPI SoundWire I3S Manager IP
- eDP 2.0 Verification IP
- Gen#2 of 64-bit RISC-V core with out-of-order pipeline based complex
Related Blogs
- What does Amazon's multiday cloud outage mean for EDA cloud services?
- EDA 'co-opertition' - a new era or more lip service?
- EDA in the Cloud: OneSpin says your design is secure
- Scaling EDA in the Cloud
Latest Blogs
- ML-KEM explained: Quantum-safe Key Exchange for secure embedded Hardware
- Rivos Collaborates to Complete Secure Provisioning of Integrated OpenTitan Root of Trust During SoC Production
- From GPUs to Memory Pools: Why AI Needs Compute Express Link (CXL)
- Verification of UALink (UAL) and Ultra Ethernet (UEC) Protocols for Scalable HPC/AI Networks using Synopsys VIP
- Enhancing PCIe6.0 Performance: Flit Sequence Numbers and Selective NAK Explained