geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <>
Subject [jira] [Commented] (GEODE-3446) Add cloud store option for export / import
Date Wed, 16 Aug 2017 09:36:00 GMT


Steve Loughran commented on GEODE-3446:

make sure you handle encryption policy/keys too; common requirement is for SSE-S3 and SSE-KMS
encryption; both take an option declaring encryption policy, and the latter needs the name
of a KMS-managed key for writing new files. Avoid SSE-C if you can.

> Add cloud store option for export / import
> ------------------------------------------
>                 Key: GEODE-3446
>                 URL:
>             Project: Geode
>          Issue Type: Sub-task
>          Components: snapshot
>            Reporter: Fred Krone
> Users would like the ability to export a region to an external cloudstore like S3, Azure,
or GoogleCloud.  
> A few things to think about is how to handle the credentials.  
> Should we create a new gfsh command to configure an S3 connection which can be used anytime?
 Or should that be handled inline with the export command?

This message was sent by Atlassian JIRA

View raw message