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
- AXI to UCIe FDI Interface IP
- 45SPCLO UCIe-Class 1-32Gbps Low Power Receiver IP (NRZ)
- 45SPCLO UCIe-Class 1-32Gbps Low Power Transmitter IP (NRZ)
- Peripheral Sensor Interface (PSI5) Host Controller
- Link Acceleration Unit
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
- What the Cyber Resilience Act means for the future of chip design
- When Your IP Vendor Has Operated 150,000 Base Stations: Introducing Viettel Semiconductor
- Relationship between architecture and validation in system design
- The Post-Quantum Cryptography Mandate: Building Cryptographically Agile Systems for the Quantum Era
- Demystify Address Translation Services (ATS) in PCIe 6.0