-
-
Notifications
You must be signed in to change notification settings - Fork 99
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support encryption on object storage #919
Comments
Can you elaborate a bit.
What do we have to expose here? |
Basically all you need to do is introduce the extra env-vars and push that down to your S3 code so the correct HTTP headers are set. For example, enabling SSE-C is as simple as sending the following headers when interacting with S3:
S3 then does the crypto transparently in-line. |
I see, this is useful @udf2457 . We'll take a look soon. |
No problem. People who use the AWS native S3 might point out they can (also) configure encryption via AWS S3 management (e.g. if you are 100% AWS-ecosystem you can configure so a bucket uses AWS KMS hosted keys). So this feature is perhaps of most significant interest to those (like me 😉 ) who use S3-compatible services from other non-AWS providers or software (e.g. |
/bounty 100 |
💎 $100 bounty • ParseableSteps to solve:
Thank you for contributing to parseablehq/parseable! Add a bounty • Share on socials
|
I want to work on this. Can I be assigned ? @nitisht |
/attempt #919
|
Sure @lazyfuhrer please go ahead. |
any updates @lazyfuhrer ? |
Is there a technical reason for the omission of encryption on object storage (S3) ?
This could be done even without introducing any extra code to
parseable
if you exposed support for S3-side features such as SSE-C.The text was updated successfully, but these errors were encountered: