NOTE
If your issue is for security or deals with sensitive info please mark it as private using the checkbox below.
This is from the agreement with CDCK we just finally signed:
DATA BACKUP PLAN
CDCK uses pairs of buckets for storing customer data: one for postgresql (database) encrypted backups, one for external blobs (images, avatars, file uploads, etc.).
CDCK will configure a separate pair of buckets for Red Hat’s use for one or more hosted forums in AWS us-west-2. Example names: cdck-file-uploads-redhatus, cdck-postgres-backups-redhatus Red Hat will configure a pair of buckets, also in AWS us-west-2, to mimic CDCK’s and provide the names to CDCK.
CDCK and Red Hat will work together to configure replication from CDCK’s buckets to Red Hat’s.
CDCK will provide to Red Hat the symmetric password used to encrypt the postgresql backup.
I need this by the end of the year, please -- at least the first part. Everything is moving at holiday time already. Some in January should be good for the bucket creation, working with CDCK to configure the rest.
Are those the actual names of the buckets we should create on our side? Or should we sync with them before creating anything?
Metadata Update from @phsmoura: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: aws
Should sync with them -- but I think it doesn' t matter what they're actually called.
I have a meeting on Monday to talk to the actual people again rather than through three levels of negotiators. I'll ask about the specifics.
Any news here? If the info is sensitive or they don't want to update here, they can mail admin@fedoraproject.org and it will get to folks who can do this. :)
Yeah, they are ready to go... I've asked them if they can coordinate here....
Hi @kevin, fitzy here from CDCK.
The name of the destination buckets for replication shouldn't matter. I've set up the source buckets and will flick an email to admin@fedoraproject.org in regards to the destination bucket information. Once I have that I can configure replication and send through the bucket policy that needs to be applied on the destination bucket (required for enabling cross-account replication).
I dropped an email to you... let us know and we can finish off our side. :)
Got it, thanks. Forwarded the original email to you.
Buckets are all setup. Test file replicated just fine. :)
I think this is complete from our end.
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.