cloudtechnician
asked on
How to use S3 or Glacier to support WORM?
Could someone please explain What exactly is WORM(Write Once Read Many) and how can I make S3 WORM bucket.
My basic understanding of WORM compliance is that you need to be able to write to disk, and then prevent the disk/drive/service from erasing or rewriting the data afterwards for a set period of time. This can be done easily with Glacier now, you reference a good link with. You could also probably do it in a marginal fashion with S3 - though someone will always have root/master creds.
My basic understanding of WORM compliance is that you need to be able to write to disk, and then prevent the disk/drive/service from erasing or rewriting the data afterwards for a set period of time. This can be done easily with Glacier now, you reference a good link with. You could also probably do it in a marginal fashion with S3 - though someone will always have root/master creds.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
But, it still wouldn't meet our compliance requirement which I want to achieve using AWS services.
We've a compliance requirement where we require to figure out a way to make the disk that contains the highly confidential client data Non-rewritable and Non-erasable. if I'm not wrong is not possible with S3?
I came across a post which says that using AWS Glacier we can apply the Lock down policies on the bucket and make it Non-rewritable and Non-erasable and even Root user wouldn't be able to make any changes after the Lock Down policy is applied. Though I couldn't understand properly how does it work because if I apply the Lock Down policy and lock it then what if I want to give access to some business partners.