Setting up FileCloud Managed S3 Storage

In this step you will need to access WWWROOT. It is typically located at: 

To enable Amazon s3 storage as the backend:

1.  To make sure that your server does not have any time variations, set up the time on your server to be synchronized.
   
   1. Configure an authoritative time server in Windows Server
   2. Synchronize Time with NTP in Linux

2. Open the following file for editing:

   WWWROOT/config/cloudconfig.php

3. Find the following line:

   define("TONIDOCLOUD_STORAGE_IMPLEMENTATION", "local");

4. Change it to this line:

   define("TONIDOCLOUD_STORAGE_IMPLEMENTATION", "amazons3");

5. Save and close the file.

6. Find the following file: 

   WWWROOT/config/amazons3storageconfig-sample.php
   

7. Rename it to:

   WWWROOT/config/amazons3storageconfig.php

 Nothing needs to be added or edited in amazons3storageconfig.php

When you are using Amazon S3 storage, certain default procedures may cause uploads to be slower and less efficient than necessary. For this reason, FileCloud 23.241 includes an Optimized Upload feature which can be enabled in your  system by following the instructions below to configure a CORS policy with the required settings, and to confirm that your service address is in the .htaccess file.

Required CORS policy for Optimized Upload

To use the Optimized Upload feature, configure a CORS policy for your S3 bucket. The CORS policy enables you to access resources from other domains while you are using the optimized upload settings. 
For more information about CORS, see:
https://docs.aws.amazon.com/AmazonS3/latest/userguide/enabling-cors-examples.html
https://docs.aws.amazon.com/AmazonS3/latest/userguide/ManageCorsUsing.html

To configure the CORS policy:

1. Sign in to the AWS Management Console and open the Amazon S3 console at https://console.aws.amazon.com/s3/.
2. In the Bucket name list, choose the name of the bucket that you want to create a bucket policy for.
3. Choose Permissions, and then choose CORS configuration.
4. In the CORS configuration editor text box, type or copy and paste the following CORS configuration:
   

   [
       {
           "AllowedHeaders": [
               "X-Amz-Checksum-Sha256",
               "content-type"
           ],
           "AllowedMethods": [
               "PUT",
               "POST",
               "DELETE"
           ],
           "AllowedOrigins": [
               "http://my-fc-instance.com"
           ],
           "ExposeHeaders": [
               "ETag"
           ]
       }
   ]

5. Click Save.

To confirm that the service address is configured in the .htaccess file:

1. Open the .htaccess file.
   Windows: C:\xampp\htdocs\.htaccess
   Linux: /var/www/.htaccess
2. Check if the following line exists, and if it does not, add it:
   If you use an external compatible S3 service, add the address to the service instead.
   

   connect-src 'self' *.amazonaws.com

3. Restart the FileCloud server.

In Step 3, below, set Use Optimized Upload to Yes, and customize any of the settings that affect upload efficiency.

Now configure your S3 credentials and storage settings.

To configure S3 storage credentials and settings:

1. In the admin portal, go to Settings > Storage.
2. Type in or select the S3 settings for your environment (the settings that appear above the Save S3 Settings button).
   Definitions of the settings appear in the table below.
3. Click Save S3 Settings.
4. Enter values for the settings below it or leave the default settings.
   Definitions of the settings appear in the table below.
5. Click Save in the upper-right corner of the screen.

To protect data at rest in FileCloud Server, you can use S3 Managed Storage Encryption.

• The communication from FileCloud to AWS will use SSL encryption resulting in complete protection for data in transit.
• Once encryption is set up correctly, the field S3 Encryption appears.

FileCloud supports the following server side encryption types:

To enable S3 encryption:

The following keys are not typically used, however they may be needed in specific circumstances. 

If you are having problems in previewing images, you should add a line to the .htaccess file.

To add a line to the .htaccess file:

1. Open the following file:

   1. Windows:  C:\xampp\htdocs\.htaccess

   2. Linux: /var/www/html/.htaccess

2. Add the following line:

   Header set Content-Security-Policy: "default-src 'self' *.live.com; style-src 'unsafe-inline' 'self';script-src 'unsafe-inline' 'unsafe-eval' 'self';font-src 'self' data:;img-src 'self' *.amazonaws.com *.live.com  data: *.duosecurity.com"

   
   

If you encounter issues where documents stored in AmazonS3 share object storage cannot be edited using a text editor, you can use a workaround to correct this.

Workaround:

1.  Change the Header set in the Content-Security-Policy
2. Use the Amazon S3 console to add a cross-origin resource sharing (CORS) configuration to an S3 bucket.

Change the Content-Security-Policy

Content Security Policy (CSP) is an HTTP header that allows site operators control over where resources can be loaded from on their site.

• The use of this header is the best method to prevent cross-site scripting (XSS) vulnerabilities. 

To change the Header set in CSP:

1. Open a command-line prompt.

2. Type in the following code (or copy and paste):

   Content-Security-Policy: "default-src 'self' *.live.com *.amazonaws.com; style-src 'unsafe-inline' 'self';script-src 'unsafe-inline' 'unsafe-eval' 'self';font-src 'self' data:;img-src 'self' data

Add a CORS Policy

To configure your bucket to allow cross-origin requests, you add CORS configuration to the bucket. A CORS configuration is an XML document that defines rules that identify the origins that you will allow to access your bucket, the operations (HTTP methods) supported for each origin, and other operation-specific information.

For more information about CORS, see Cross-Origin Resource Sharing (CORS) in the Amazon Simple Storage Service Developer Guide.

To allow the use of a text editor:

 The CORS configuration is an XML file. The text that you type in the editor must be valid XML.

1. Sign in to the AWS Management Console and open the Amazon S3 console at https://console.aws.amazon.com/s3/.
2. In the Bucket name list, choose the name of the bucket that you want to create a bucket policy for.
3. Choose Permissions, and then choose CORS configuration.

4. In the CORS configuration editor text box, type or copy and paste the following CORS configuration:

   
   

   <CORSConfiguration>          
       <CORSRule>            
       <AllowedOrigin>*</AllowedOrigin>            
       <AllowedMethod>GET</AllowedMethod>            
       <AllowedHeader>*</AllowedHeader>        
       <MaxAgeSeconds>3000</MaxAgeSeconds>          
       </CORSRule>
   </CORSConfiguration>

5. Click Save.

If you are having problems in playing  mp4 videos, you should add a line to the .htaccess file.

To add a line to the .htaccess file:

1. Open the following file:

   1. Windows:  C:\xampp\htdocs\.htaccess

   2. Linux: /var/www/html/.htaccess

2. Add the following line:

   
   

   Header set Content-Security-Policy: "default-src 'self' *.live.com *.amazonaws.com; style-src 'unsafe-inline' 'self';script-src 'unsafe-inline' 'unsafe-eval' 'self';font-src 'self' data:;img-src 'self' *.live.com  data: *.duosecurity.com *.amazonaws.com"

Add a CORS Policy

To configure your bucket to allow cross-origin requests, you add CORS configuration to the bucket. A CORS configuration is an XML document that defines rules that identify the origins that you will allow to access your bucket, the operations (HTTP methods) supported for each origin, and other operation-specific information.

For more information about CORS, see Cross-Origin Resource Sharing (CORS) in the Amazon Simple Storage Service Developer Guide.

To allow the use of a text editor:

 The CORS configuration is an XML file. The text that you type in the editor must be valid XML.

1. Sign in to the AWS Management Console and open the Amazon S3 console at https://console.aws.amazon.com/s3/.
2. In the Bucket name list, choose the name of the bucket that you want to create a bucket policy for.
3. Choose Permissions, and then choose CORS configuration.

4. In the CORS configuration editor text box, type or copy and paste the following CORS configuration:

   
   

   <CORSConfiguration>          
       <CORSRule>            
       <AllowedOrigin>*</AllowedOrigin>            
       <AllowedMethod>GET</AllowedMethod>            
       <AllowedHeader>*</AllowedHeader>        
       <MaxAgeSeconds>3000</MaxAgeSeconds>          
       </CORSRule>
   </CORSConfiguration>

5. Click Save.