Setting up an Amazon S3 target

R‑Cloud supports using an Amazon S3 target to store data in the Amazon S3 cloud storage.

Prerequisites

  • An AWS IAM role that is used for performing all operations on the target must be added to R‑Cloud. You can add this IAM role as part of setting up your Amazon S3 target, or use the one that you already added as part of doing one of the following:

  • Only if you plan to enable the customer-managed target encryption without a key management service. The length of your AES-256 key must be 32 bytes.

  • Only if you plan to enable the customer-managed target encryption with a key management service. The cloud account that you want R‑Cloud to use to access the encryption key must have the required permissions assigned. The cloud account that you want R‑Cloud to use to access the encryption key must have the required permissions assigned:

    Cloud account Required permissions
    AWS IAM role

    A custom managed or inline policy with the kms:Encrypt and kms:Decrypt permissions.

    Example   

    {
      Version": "2012-10-17",
      "Statement": [
       {
        "Effect": "Allow",
        "Action": [
         "kms:Encrypt",
         "kms:Decrypt"
        ],
        "Resource": "arn:aws:kms:<Region>:
        <AccountID>:key/<KeyID>"
       }
      ]
    }
    Azure service principal (including the HMSP) The Key Vault Crypto User role assigned at the Key Vault Key level.
    Google Cloud service account (including the HMSA) The Cloud KMS CryptoKey Encrypter/Decrypter role (roles/cloudkms.cryptoKeyEncrypterDecrypter) assigned at the KMS crypto key level.

Limitations

  • Storing data to a publicly available target is not supported.

  • Storing data to a target on which a lifecycle configuration is set is not supported and may result in data loss.

  • Only copies of backup data can be stored to a target with the S3 Glacier Flexible Retrieval or S3 Glacier Deep Archive storage tier. Keep in mind that AWS can charge you additionally for premature removal of data if the retention period specified in your policy is shorter than the recommended (minimum) retention period in AWS.

  • Only if you plan to enable target encryption. The following limitations apply:

    • Target encryption is supported for SaaS applications.

    • R‑Cloud cannot encrypt data of the SaaS applications that use only snapshots for storing the data. For details, see the relevant topics for your SaaS application in Protecting SaaS applications.

    • For customer-managed target encryption with a key management service: The following keys are supported:

      • For AWS Key Management Service (KMS): Symmetric encryption KMS keys

      • For Azure Key Vault: RSA keys

      • For Google Cloud Key Management Service (KMS): Symmetric encryption keys

Considerations

  • You can set up the same target in multiple protection sets.

  • Storing data to a target that has Object Lock (WORM) enabled is supported.

  • Only if you plan to enable target encryption. Consider the following:

    • The R‑Cloud encryption is applied on top of the native cloud platform data encryption to provide an additional layer of security.

    • After you enable target encryption, the previously stored backup data remains unencrypted.

    • If you decide to disable target encryption, the backup data that was stored on the target while the target encryption was enabled remains encrypted.

    • The SaaS applications metadata is not encrypted.

  • Only if you plan to enable the customer-managed target encryption with a key management service. Consider the following:

    • If you disable your encryption key in cloud or unassign the required permissions from the cloud account, you will not be able to restore the data that is stored on the target or store new data on the target until you re-enable the encryption key or reassign the permissions.

    • If you delete your encryption key from cloud, you will not be able to restore the data that is stored on the target. To store new data on the target, you must reconfigure the target encryption and perform a manual full backup.

Recommendation

The exclude policy is automatically assigned to the bucket that is added to R‑Cloud as a target. It is highly recommended that you do not change this default configuration.

To access the Targets panel, in the navigation pane, click Targets Targets. Alternatively, in the Dashboard panel, click the Targets widget title.

Procedure

  1. In the Targets panel, click Add Add.

  2. Select Amazon S3, and then click Next.

  3. Depending on the type of your bucket, click one of the following:

    • General purpose bucket

    • Directory bucket

  4. In the Bucket Name, enter the name of an existing bucket that will store protected data.

  5. In the Size Quota field, specify the amount of storage space that should be used for storing data (in MiB, GiB, or TiB).

    Important  The specified amount represents a soft limit, therefore actual usage may exceed it.

  6. Use the Enforce quota switch to stop running backups if this target reaches its size quota. The backups will start running again after you increase the size quota of this target or assign a different policy to the entities. Such a policy must use a target with the sufficient size quota.

  7. From the Storage Class drop-down, select the storage class that you want to use for storing the data.

  8. From the IAM Role drop-down menu, select the AWS IAM role that you want to be used for performing all operations on the target. If such an IAM role is not already added to R‑Cloud, you can add it as follows:

    1. In the drop-down menu, click Add Add New.

    2. Enter a display name for the IAM role that you want to add to R‑Cloud.

    3. In the Account ID field, enter the ID of the that contains the target that you are setting up.

    4. Click Create IAM Role to be automatically redirected to the AWS Management Console where you can create the IAM role. The required permissions are assigned to the IAM role during the creation procedure. For a list of the permissions, see AWS permissions.

      Important  You must be signed in to the AWS Management Console with the that contains the target that you are setting up. If you are already signed in to the AWS Management Console with a different when you create the IAM role, the creation fails.

    5. Click Add.

  9. Only if you are adding a directory bucket. In the Region field, enter the region of your bucket (for example, us-east-1).

  10. Only if you want the SaaS application data that is stored on this target to be encrypted. Under Encryption Settings, enable the Target encryption switch, and then do the following:

    1. From the Key Management Type drop-down menu, select one of the following options:

      • Select HYCU managed if you want the encryption key to be provided and managed by HYCU.

      • Select Customer managed if you want to provide and manage the encryption key by yourself.

    2. Only if you selected the Customer managed option. From the Customer Key Provider drop-down menu, select your encryption key provider:

      Encryption key provider Instructions
      AWS Key Management Service

      Select this option, and then do the following:

      1. From the Encryption Cloud Account drop-down menu, select the cloud account that you want R‑Cloud to use to access the encryption key.

        By clicking Add Add New, you are automatically redirected to the dialog box that enables you to add the preferred cloud account to R‑Cloud, if not already added.

      2. In the Key ARN field, enter the AWS KMS Amazon Resource Name (ARN) of the encryption key in the following format:

        arn:aws:kms:<Region>:<AccountID>:key/<KeyID>

      Azure Key Vault

      Select this option, and then do the following:

      1. From the Encryption Cloud Account drop-down menu, select the cloud account that you want R‑Cloud to use to access the encryption key.

        By clicking Add Add New, you are automatically redirected to the dialog box that enables you to add the preferred cloud account to R‑Cloud, if not already added.

      2. In the Key Identifier field, enter the Azure Key Vault key identifier in the following format:

        https://<VaultName>.vault.azure.net/keys/<KeyName>

      Google Cloud Key Management Service

      Select this option, and then do the following:

      1. From the Encryption Cloud Account drop-down menu, select the cloud account that you want R‑Cloud to use to access the encryption key.

        By clicking Add Add New, you are automatically redirected to the dialog box that enables you to add the preferred cloud account to R‑Cloud, if not already added.

      2. In the Crypto Key Resource Name field, enter the resource name of the Google Cloud KMS cryptographic key in the following format:

        projects/<ProjectID>/locations/<LocationName>
        /keyRings/<KeyRingName>/cryptoKeys/<CryptoKeyName>

      Custom key file

      Select this option, and then, in the AES-256 Encryption Key field, browse for and select your AES-256 binary key.
  11. Click Save.

The target is added to the list of targets in the Targets panel. For details on managing targets, see Managing targets.