A finance company is storing financial records in an Amazon S3 bucket. The company persists a record for every financial transaction. According to regulatory requirements, the records cannot be…

While the explicit solution for immutability is S3 Object Lock, which is enabled when creating a bucket, 'Create a new S3 bucket' is the foundational step before configuring S3 Object Lock to meet the write-once-read-many (WORM) compliance requirement for immutability without impacting accessibility.

S3 Glacier storage tiers are designed for archival data with retrieval times ranging from minutes to hours, which does not meet the requirement for records to be 'immediately accessible'.

S3 Intelligent-Tiering automatically moves objects between access tiers to optimize costs but does not provide immutability or WORM capabilities for regulatory compliance.

An S3 bucket policy with a Deny action for PutObject operations would prevent any new objects from being written and does not provide time-based immutability for existing objects as required.