> Anyone else find it disturbing that they are able to restore data that they deleted permanently for "compliance" reasons? An overarching theme with these thi

> Anyone else find it disturbing that they are able to restore data that they deleted permanently for "compliance" reasons? An overarching theme with these things is “legitimate business need” and “no indefinitely retained customer data. Having backups, system event logs, etc are all legitimate business needs. Based on the data type that business need may be days or years with things like financial and legal requirements. Youre conflating permanent, immediate, and irrevocable. These are usually handled in different aspects. Think of accounts having multiple states like active, suspended, closed, terminated, purged. Some examples; suspended: credentials/authnz immediately disabled, all data online, charges continue to accrue, can be restored in minutes. Closed: credentials disabled, data online, processing stopped, charges stopped, may take manual intervention (hours) to return to active. Terminated: creds & account irrevocably unavailable, online data deleted, offline data (backups) remains available. Purged: all online and offline customer data irrevocably unavailable. This generally happens after a defined retention period for things like logs, backups, etc. You can apply similar concepts to individual resources more granularly than the account. Disclaimer: principal at AWS but the above is my own opinion/observation and does not represent my employer.