Data protection

Object Storage provides several features that can be used to help prevent unwanted deletion of data. From simplest to strictest, they are:

• Object Lock is a method of defining time-based restrictions on how old an object version has to be before it can be explicitly deleted.
  • In GOVERNANCE mode, explicit deletion of past versions is still possible before the retention period expires, but requires special permission (an unlimited access key) as well as an explicit "bypass governance retention" flag in the deletion request. This provides further safeguards against accidental deletion.
  • In COMPLIANCE mode, it is not possible for any user to delete object versions before the retention period expires. This provides the highest level of protection against accidental and even malicious deletion (such as from ransomware).
• Versioning is a method of retaining historical versions of files (objects). While it is still possible to explicitly delete a past version of an object (by passing the appropriate versionID to the DeleteObjects S3 operation, for example), doing so requires extra steps, which may make it less likely to happen accidentally.
• Design your deployments for high-availability and disaster recovery. Consider how to best set up your data's availability for requests, for high-availability and disaster recovery.
• Object encryption. We offer two forms:
  • Default encryption at rest (SSE S3). Whenever you upload content to an E2 or E3 endpoint, your objects will be automatically encrypted at rest using AES256 encryption.
  • Server-side encryption with customer-provided keys (SSE-C). This encryption secures your data on Object Storage using an encryption key pair that you create. the encryption is applied your data is stored to disk. Once encrypted, ​Akamai​ only decrypts the object if that same encryption key is provided with the retrieval request.