We are attempting to set up an S3 storage option within our OnBase test environment using AWS to help with our file storage. We're testing this in response to our storage growing exponentially on site and some of that has to do with the fact that we do conversion within the scan queue process converting PDF's to Image File Format. I have forced bitonal conversion to help with the size conversion, but it's still larger size files using vast amounts of file storage space. Could someone help explain how the encryption settings within OnBase work compared to those within the S3 provider? Does the setting within OnBase provide additional encryption on our side, or during retrieval or transit that the S3 bucket isn't providing, or are the settings other than non for an S3 provider that doesn't provide encryption? I see the settings shown in the Platter Management MRG, but I don't see an explanation of what the encryption pertains to specifically, or vs. the S3 provider settings.
In testing, we are currently using the Default (SSE-S3) S3-managed keys option for encrypting files in the S3 bucket dedicated to Onbase. Could you please clarify if we need to create a dedicated key in AWS KMS and switch the encryption to AWS Key Management Service Key (SSE-KMS) in our bucket, or is the default encryption and an encryption setting of "none" acceptable?
The goal is to verify that files are adequately encrypted at rest and while in transit. Here are the current encryption settings for the S3 bucket.
Has anyone else set this up with AWS and would be willing to share their knowledge about the configuration or encryption settings? I was also wondering about the retrieval times, although we'll see that once we have the test connection set.
Thanks!
Pam
1 ACCEPTED ANSWER
