|
NOTE: For cloud tier to work correctly, first create a default project in the Google cloud platform for interoperable access. For more information, see Migrating from Amazon S3 to Cloud Storage | Google Cloud. |
To add a cloud storage group, complete the following steps
- In the navigation menu, click Cloud Storage to expand the menu, then click Cloud Tier.
- In the Cloud pane, click Configure to add a cloud tier.
- In the Cloud Provider drop-down, select AWS S3.
- Provide the name for your S3 bucket.
- Enter your Connection String using one of the two methods below:
- Default - this option will compile your connection string into the correct format using the inputs below.
- Access key - The access key is typically 20 upper-case English characters
- Secret key - The secret key is generated automatically by AWS. It is typically 40 characters, including mixed upper and lower-case and special symbols.
- Region - The region specifies the Amazon-specific region in which you want to deploy your backup solution. You can obtain your region code from https://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region.
- Custom - this option allows you to enter your connection string with additional parameters.
- Your connection string uses the following syntax:
"accesskey=<ABDCEWERS>;secretkey=< >; loglevel=warn; region=<aws-region>;"
Please note the following:
- The access key is typically 20 upper-case English characters
- The secret key is generated automatically by AWS. It is typically 40 characters, including mixed upper and lower-case and special symbols.
- The region specifies the Amazon-specific region in which you want to deploy your backup solution. You can obtain your region code from https://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region.
An example of a connection string with this syntax follows. Logically, each connection string is unique.
accesskey=AKIARERFUCFODHFJUCWK;secretkey=p+8/T+o5WeZkX11QbuPazHX1IdWbwgFplxuVlO8J;loglevel=warn;region=eu-central-1;
- Your connection string uses the following syntax:
- Default - this option will compile your connection string into the correct format using the inputs below.
- Enable Cloud Locking: Select this option to achieve immutability of data tiered to the cloud.
NOTE:Cloud Locking works with RDA and Object containers only. Data that is set as immutable on the local storage is also set as immutable when tiered to the cloud.
Enabling locking at the Cloud Tier is required so the containers that are tiering data to this Cloud Tier can choose to enable locking as part of their cloud tiering policy.
AWS storage classes can be chosen from the following:
- S3 Standard
- S3 Intelligent-Tiering
- S3 Standard-Infrequent Access
- S3 One Zone-Infrequent Access
- S3 Glacier Instant Retrieval
Please note, apart from S3 Standard, other storage classes provide further cost savings for data that is infrequently accessed. - To apply encryption, in the Cloud TierEncryption section enter the following:
- Passphrase — the passphrase is user-defined and is used to generate a passphrase key that encrypts the file in which the content encryption keys are kept. The passphrase is a human readable key, which can be up to 255 bytes in length. It is mandatory to define a passphrase to enable encryption.
IMPORTANT: It is mandatory to define a passphrase to enable encryption. If the passphrase is compromised or lost, the administrator should change it immediately so that the content encryption keys do not become vulnerable. If this passphrase is lost or forgotten, data in the cloud will be unrecoverable.
- Confirm Passphrase — re-enter the passphrase used above.
- Passphrase — the passphrase is user-defined and is used to generate a passphrase key that encrypts the file in which the content encryption keys are kept. The passphrase is a human readable key, which can be up to 255 bytes in length. It is mandatory to define a passphrase to enable encryption.
- Click Configure. A Cloud Storage Group will be created.
- To enable replication to the cloud, you must link a local container to the cloud using the procedures in Adding a cloud tiering policy.