Does S3 Strong Consistency mean disabling EMRFS Consistent Views?

Question

Customer is using EMR FS consistent view because S3 was eventually consistent. Post-Re:Invent 2020, with Amazon S3 Strong Consistency, they no longer need EMR FS Consistent View. Can customer start disabling EMR FS consistent view for their clusters? Any other changes/settings we can share with customers to be aware of?

Accepted Answer

As [Jeff Barr mentions in his blog post][1] that EMRFS Consistent Views is not longer needed , and so I think it is safe to advise the customer they can disable it.

No other changes/setting would be impacted. EMRFS it is obviously still needed.

Here's the [documentation on S3 consistency][2], which includes reads after deletes ( a delete is a type of write)

> Amazon S3 data consistency model Amazon S3 provides strong
> read-after-write consistency for PUTs and DELETEs of objects in your
> Amazon S3 bucket in all AWS Regions. This applies to both writes to
> new objects as well as PUTs that overwrite existing objects and
> DELETEs.

[1]: https://aws.amazon.com/blogs/aws/amazon-s3-update-strong-read-after-write-consistency/
  [2]: https://docs.aws.amazon.com/AmazonS3/latest/dev/Introduction.html

Does S3 Strong Consistency mean disabling EMRFS Consistent Views?

Relevant content