Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Version published after converting to the new editor

Table of Contents
maxLevel3

...

These instructions are for RStor cloud storage, but any Internet-based S3 service will have similar functionality:

  1. Service — If needed, sign up for RStor: rstor.io
  2. Bucket — Create a bucket that will be dedicated to backing up your Swarm cluster.
    1. Sign in to the RStor console: rstorcloud.io.
    2. Choose Add new bucket.
    3. For Bucket name, enter a DNS-compliant name for your new bucket. You will not be able to change it later, so choose well:
      • The name must be unique across all existing bucket names in RStor S3.
      • The name must be a valid DNS name, containing only lowercase letters and numbers (and internal periods, hyphens, underscores), between 3 and 64 characters.
        (See S3 documentation: Rules for Bucket Naming.)
        Tip: For easier identification, incorporate the name of the Swarm cluster that this bucket will be dedicated to backing up.

    4. For Region, choose the one that is appropriate for your business needs.
    5. Best practice: Do not enable versioning or any other optional features unless it is required for your organization.
    6. Record these values for configuring your S3 Backup feed in Swarm:
      • Bucket Name
      • Region
    7. Click Submit.
  3. S3 Key Pair — Create an S3 key pair that will be dedicated to Swarm access.
    1. Under your email address, click My account.
    2. Down below click Generate Key
    3. An S3 key pair will be automatically created. Download and secure the access key:
    4. Record these values for configuring your S3 Backup feed in Swarm:
      • Access Key ID
      • Secret Access Key
  4. RProtect — Complete any subnet whitelisting needed.

    1. In the global menu bar, click on RProtect.

    2. Verify that the IP address of the Swarm cluster that will be contacting the RStor S3 cloud service is allowed.

    3. If that was not the case, request a new rule.

...