What feature in Amazon S3 allows you to use a write-once-read-many model for stored objects?

The feature in Amazon S3 that enables a write-once-read-many model for stored objects is S3 Object Lock. This feature allows you to place an object in a mode where it cannot be overwritten or deleted for a specified retention period. The write-once-read-many model fits well with scenarios where data integrity and retention are critical, such as compliance and archival.

When you enable Object Lock for an S3 bucket, it can be configured in either Governance or Compliance mode. Governance mode allows you to restrict deletion and modification actions but permits certain users to alter this setting, while Compliance mode is more stringent and prevents any changes, ensuring that once data is written, it remains intact and accessible until the specified retention period expires.

This characteristic of Object Lock is essential for applications requiring data immutability, such as financial records, healthcare information, or any other data governed by regulatory requirements. By ensuring that objects cannot be deleted or altered after they have been committed, organizations can protect themselves against accidental or malicious changes.

In contrast, other options such as S3 Object Versioning allow multiple versions of an object to coexist, but they do not enforce the write-once aspect. AWS Glacier is primarily for archiving data with a different access pattern and does not specifically