Details
-
Bug
-
Resolution: Fixed
-
6.6.0
-
None
-
*Location*: https://docs.couchbase.com/server/6.6/backup-restore/cbbackupmgr-cloud.html
*Referrer*: https://docs.couchbase.com/server/6.6/backup-restore/enterprise-backup-restore.html
*User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.105 Safari/537.36
*Screen Resolution*: 2048 x 1152*Location*: https://docs.couchbase.com/server/6.6/backup-restore/cbbackupmgr-cloud.html *Referrer*: https://docs.couchbase.com/server/6.6/backup-restore/enterprise-backup-restore.html *User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.105 Safari/537.36 *Screen Resolution*: 2048 x 1152
Description
In this section you learn how to bucket to and from S3.
however EC2 instance has a nice feature in which you can attach a IAM role to the instance, thus never have to provide further credentials when utilising S3 as a backup repo.
Steps:
1. Create a Role with a policy which allows S3 data manipulation (S3 Full Admin for example)
2. attach it to the instance
3. export CB_AWS_ENABLE_EC2_METADATA=true
4. use the cbbackupmgr tool
Sample run
[ec2-user@ip-172-31-91-36 bin]$ export CB_AWS_ENABLE_EC2_METADATA=true
[ec2-user@ip-172-31-91-36 bin]$ echo $CB_AWS_ENABLE_EC2_METADATA
true
[ec2-user@ip-172-31-91-36 bin]$ ./cbbackupmgr config -r testRepo --obj-region us-east-1 -a s3://bucketName/archiveFolder --obj-staging-dir /path/to/staging
Backup repository `testRepo` created successfully in archive `s3://bucketName/archiveFolder`
Roi.
Reporter: Roi Katz
E-mail: roi.katz@couchbase.com