brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrea Turli <>
Subject Re: Brooklyn YAML for RabbitMQ cluster
Date Fri, 14 Aug 2015 19:56:29 GMT
Hi Anamika,

It is already possible to store persistence data on all the blobstore
supported by jclouds.

There is not direct support for encryption (either client or server side)
in the jclouds portable abstraction. Something around s3 has been discussed

It should be easy to implement blobstore encryption for some providers in
jclouds so that Brooklyn can benefit of it.
Note that MS Azure has a codified client-side encryption, Openstack Swift
has blueprints but no code for several proposals, and Google cloud storage
defaults to encryption with no user configuration, so an abstraction won't
be easy but makes sense as provider-specific feature.

Sorry for the belated answer,

Il giorno ven 7 ago 2015 10:37 Anamika Roychowdhury <>
ha scritto:

> Hello Brooklyn Team,
> We have a Brooklyn HA setup which stores the data on an AWS S3 bucket. We
> would like to store the data in an encrypted format using AWS’s server side
> encryption.
> I’m able to use AWS CLI command to store my file Hello.txt in an AES-256
> encrypted format on my S3 bucket mybucket using the command:
> aws s3 cp "hello.txt" "s3://mybucket/" –sse
> I could not find any information about sending the encryption details
> through Brooklyn.
>  Can you please  provide details on how we can go about implementing this
> functionality or any alternatives for the implementation ?
> Thanks,

Cloudsoft Corporation Limited, Registered in Scotland No: SC349230. 
 Registered Office: 13 Dryden Place, Edinburgh, EH9 1RP
This e-mail message is confidential and for use by the addressee only. If 
the message is received by anyone other than the addressee, please return 
the message to the sender by replying to it and then delete the message 
from your computer. Internet e-mails are not necessarily secure. Cloudsoft 
Corporation Limited does not accept responsibility for changes made to this 
message after it was sent.

Whilst all reasonable care has been taken to avoid the transmission of 
viruses, it is the responsibility of the recipient to ensure that the 
onward transmission, opening or use of this message and any attachments 
will not adversely affect its systems or data. No responsibility is 
accepted by Cloudsoft Corporation Limited in this regard and the recipient 
should carry out such virus and other checks as it considers appropriate.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message