On Tue, Jul 24, 2012 at 3:54 PM, Dr Nic Williams wrote:Bump.
I'd like to share some boshreleases but I'm not sure how to do so without
including read/write AWS credentials.
Dr Nic Williams - VP Developer Evangelism
Engine Yard
The Leading Platform as a Service
Mobile: +1 415 860 2185
Skype: nicwilliams
Twitter: @drnic
On Sunday, July 22, 2012 at 10:00 AM, Dr Nic Williams wrote:
Also, are encryption_key and blobstore_secret just any random string? Or
a meaningful string that has been encrypted?
Cheers
Nic
Dr Nic Williams - VP Developer Evangelism
Engine Yard
The Leading Platform as a Service
Mobile: +1 415 860 2185
Skype: nicwilliams
Twitter: @drnic
On Saturday, July 21, 2012 at 8:06 PM, skaar wrote:
Nic,
check the BOSH manual:
https://github.com/cloudfoundry/oss-docs/blob/master/bosh/documentation/documentation.md#s3you can keep secrets in config/private.yml - and exclude that from your
repository - we typically just symlink it into our working copies.
/skaar
On Sat, Jul 21, 2012 at 7:24 PM, Dr Nic Williams <nwilliams@engineyard.com
wrote:
How would I open source a bosh release that uses blobs and an AWS S3
blobstore?
My config/final.yml needs credentials for AWS S3 for both reading (the
open source part) and writing (the developers' part). The credentials can
be created with AWS IAM to only read/write S3, but still, I don't want to
have to check with S3 to ensure that people aren't storing their own stuff
in my personal S3 buckets.
Suggestions?
How does the EMC ATMOS storage system & credentials work? Could I use the
bosh-sample-release ATMOS credentials and write files to it?
Nic
------------------------------
Dr Nic Williams - VP Developer Evangelism
[image: Engine Yard]
The Leading Platform as a Service
Mobile: 415 860 2185
Skype: nicwilliams
Twitter: @drnic
------------------------------