Skip to main content

Preparing AWS S3 bucket before installing the app

Steps to prepare the AWS S3 bucket before using it in Revyz Data Manager for Confluence (BYOS) app.

Creating a S3 bucket

Follow the steps as mentioned in → https://docs.aws.amazon.com/AmazonS3/latest/userguide/create-bucket-overview.html

Important notes:

Selecting encryption option
Updating Bucket's Access Policy

Sample Policy
  • Note: The Policy, specific to your environment will be shown to you on the Revyz app’s Welcome wizard. Below is the sample policy for reference.

CODE
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "AllowS3ActionsInCustomerBucket",
            "Effect": "Allow",
            "Principal": {
                "AWS": "<revyz-iam-user-arn>"
            },
            "Action": [
                "s3:ListBucket",
                "s3:PutObject",
                "s3:GetObject",
                "s3:PutObjectTagging"
            ],
            "Resource": [
                "arn:aws:s3:::<your-bucket-name>",
                "arn:aws:s3:::<your-bucket-name>/*"
            ]
        }
    ]
}
Breakdown of the S3 Access Policy contents
  • Principal

    • It is the Revyz IAM User from Revyz’s AWS account, which will be used by Revyz app to perform the Read-Write operations during backup, restore and other tasks that the app supports.

  • Action

    • Revyz app will need 4 permissions for your S3 bucket

      • ListBucket

        • To list and access the bucket

      • PutObjects

        • To write the objects during backup job

      • GetObject

        • To retrieve the objects during restore / clone job

      • PutObjectTagging

        • To add the Tag to the objects which can later be used for lifecycle management of the objects

    • Note: Revyz user will not have any delete permission for the given S3 bucket

  • Resource

    • Your S3 bucket on which the permissions are to be implemented

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.