Configuring your own S3 Bucket for use with SendSafely

SendSafely enterprise customers have the option to provide their own S3 bucket for storing encrypted content related to their SendSafely enterprise portal. By using your own S3 Bucket for storage, you will also be eligible to enable the following features within your SendSafely portal:

• Disabling Package Expiration
• Disabling File Deletion

This article will walk you through the necessary steps to create and configure the S3 bucket. 

1. Create a new S3 bucket

The bucket can be loaded in any AWS region, however for optimal performance we recommend creating the bucket in the same region where your portal servers are located.

• For US customers, the portal servers are located in the US-EAST-1 (N. Virginia).
• For EU customers, the portal servers are located in EU-WEST-1 (Dublin)
• For AU customers, the portal servers are located in AP-SOUTHEAST-2 (Sydney)

The name of the bucket should start with "sendsafely-" and should allow you to easily identify it later. 

The name of the bucket must start with "sendsafely-" in order to use Cross-account Role Access. If you do not name your bucket correctly you will need to provide an API Key and API Secret for access.

2. Enable "Transfer Acceleration"

The Transfer Acceleration option is located under the Bucket Properties section of the S3 console. 

3. Add a custom CORS policy 

The CORS policy can be added under the bucket permissions screen.The policy should include the following: 

[
  {
    "AllowedHeaders": [
      "*"
    ],
    "AllowedMethods": [
      "GET",
      "PUT"
    ],
    "AllowedOrigins": [
      "*"
    ],
    "ExposeHeaders": [
      "ETag"
    ],
    "MaxAgeSeconds": 3000
  }
]

4. Create an Amazon S3 Bucket Policy for Cross-account Role Access 

Use this bucket policy to grant our service role access to your custom S3 bucket. 

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "SendSafelyRule1",
            "Effect": "Allow",
            "Principal": {
                "AWS": "arn:aws:iam::371444783282:role/SendSafely-EFE-EC2-Server-Role"
            },
            "Action": [
                "s3:GetObject",
                "s3:PutObject",
                "s3:DeleteObject",
                "s3:ListBucket"
            ],
            "Resource": [
                "arn:aws:s3:::sendsafely-customer-bucket-name",
                "arn:aws:s3:::sendsafely-customer-bucket-name/*"
            ]
        }
    ]
}

5. Submit a Migration Request to SendSafely Support 

The final step is to submit the request to the SendSafely Help Desk to have your custom S3 bucket enabled for your SendSafely enterprise portal. For security and identity verification purposes, the request must be made by your organization’s SendSafely administrator and submitted as a SendSafely secure message from the administrator’s SendSafely account. Please follow these steps:

• Log into SendSafely with an Enterprise Administrator account
• Click the "Send" link, then "Add Message", and type a secure message that includes the name of the S3 bucket
• Add [e-mail] as a recipient
• Click the green Submit button, copy the secure link into an email with the subject "Request to enable custom S3 bucket", and send to [e-mail] 

6. Request optional Data Retention Features

After your S3 bucket has been enabled, you can then choose to have our support team enable the following features within your SendSafely portal:

• Disabling Package Expiration
• Disabling File Deletion

Please review each of these features, and if required submit a ticket to the SendSafely support team following the process outlined in each linked article.