You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2017/08/16 09:36:00 UTC
[jira] [Commented] (GEODE-3446) Add cloud store option for export /
import
[ https://issues.apache.org/jira/browse/GEODE-3446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16128556#comment-16128556 ]
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: https://issues.apache.org/jira/browse/GEODE-3446
> 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
(v6.4.14#64029)