S3 Replication#

Once you have finished Deploying to Backup Account, you can set up replication in the source bucket.

Create a replication rule#

  1. Open your source S3 bucket in the AWS console

  2. Under the “Management” tab, find the “Replication Rules” section

  3. Click “Create replication rule” to create a new rule

  4. Enter an ID. If this is a developer bucket, include your initials. Preferably, it should be clear this is a backup rule.

  5. Under “Source Bucket”, select “Apply to all objects in this bucket”

  6. Under “Destination” select “Specify a bucket in another account” and enter the account number and bucket name

  7. Under “IAM role”, select the “SdsDataManager-{account_name}-BackupRole”

  8. Then, save the rule, and select “Do not replicate existing objects” in the popup

Now, items placed in the source bucket will be automatically replicated to the backup bucket!

Copying items back into source account bucket#

To restore files from the backup bucket into the main account bucket, we are going to assume the role created by SdsDataManager stack in the source account. Here, “source account” refers to the account with SdsDataManager deployed into it (i.e. dev or prod).

  1. Update ~/.aws/config to include a new profile for this role. Here, source_profile should be the source account profile

    [profile backup-role]
role_arn = arn:aws:iam::<source account number>:role/<role name>
source_profile = imap

  2. Update the role in the dev account to include a new principal:

    • Under the “Trust relationships” tab, edit the trust policy

    • add a new principal to the trust policy with your username. You can do this via the GUI or just add under “principal”: "AWS": "arn:aws:iam::<source account>>:user/hartnett" (update with your username)

    • We can then assume this role in the AWS CLI with --profile

  3. Check your credentials: aws s3 ls --profile backup-role s3://sds-data-dev

  4. To transfer all files from the backup bucket to the main bucket: aws s3 sync --profile backup-role s3://sds-data-backup s3://sds-data-dev

  5. If you have any issues, you can check permissions by downloading and uploading locally (replace one of the bucket names with a local file path)