...
Browse to the AWS console: https://console.aws.amazon.com
Log in with valid credentials.
Select the S3 service from Services.
From there, create a new S3 bucket.
Name and region — Name the bucket as you like, but it must be a DNS-compliant name that is unique across all AWS regions.
Use lower-case letters, numbers, and hyphens, with no special characters.
Configure options — Accept the defaults here:
Set permissions — Accept the defaults here, too:
Review and create the bucket, which will appear appears in your the S3 Buckets listing:
Creating an AWS user for FileFly
To avoid using the root credentials for FileFly access (which is bad practice), create an IAM user which only has with access to S3.
In the AWS console, select the Services menu.
From Security, Identity, & Compliance (bottom right), select IAM.
From the left menu, select Users:
Select Add user:
A wizard takes you walks through creating a user for IAM. On the first page, name the user to indicate it is dedicated to FileFly access, and be sure to select Programmatic access:
Next, assign the permissions for the FileFly user. Start by creating a group to add the user to; select Create group:
Name the group and filter for applicable prebuilt policies that you can apply by searching on "
s3":
Select AmazonS3FullAccess, which allows your the FileFly user to create buckets and read/write/delete content.
Select the policy and attach it to the group, then click Create group.
Next, any tags you may want Add tags to apply to your the user, to help identify the purpose of the account:
Next, Review the summary and complete.
Next, you will be prompted 
A prompt appears to download a CSV file that records with the access key ID/secret access key pair.
This is the only sole opportunity, so download this file to a secure location. These are used in the next setup step.
...
With the S3 bucket and dedicated IAM user created, configure FileFly to access the AWS S3 account.
Go Navigate to the FileFly Migration agent that you will be using used to write data to AWS.
Install both the "Caringo FileFly Amazon S3 Config" and "Caringo FileFly Amazon S3 Plugin".
Note: When you install a new plugin for FileFly, any migration Migration jobs are paused until that a plugin is configured when a new plugin for FileFly is installed.After the FileFly S3 Config tool is installed on the migration agent, open it via the Start menu.
You can search Search for "s3" if not listed:
When you are 
Select Amazon AWS S3 when prompted for the type, select Amazon AWS S3, which is the option for direct connectivity to Amazon:
The second, Generic S3 Endpoint, is for connecting to any other S3-compatible target (such as Content Gateway access to Swarm object storage, or another external provider).On the main configuration screen, enter the Enter the Amazon account credentials, the Access Key ID and Secret Access Key from the CSV file you saved above on the main configuration screen:
Next, select Manage Buckets...
Select your the S3 bucket from the list:
Although you could select
Note: Writes to a bucket created from selecting New... and create a bucket from here, note that writes to that bucket would not be possible immediately are not immediately possible: it can take 15-25 minutes for Amazon to propagate DNS across regions.Highlight the bucket that you want to use be used and then select the Get Migration URI button:
When prompted to Select a partition, accept the Default partition.
Creating a partition here would create creates a prefix or pseudo folder, for separating content in a mixed-use bucket. Best practice is to dedicate this bucket wholly to FileFly, which prevents accidental deletion of FileFly files by other sources.Click OK, and copy the URI that is placed on your from the clipboard:
Finally, save Save the config file so that the target will still work works if the server reboots.
Click OK, then Close, then select Save at to the bottom of the screen.The place to save the configuration by default should be "C:\Program Files\” is the default location to save the configuration.
Per the instructions on the dialog:
Copy the config file to any additional FileFly Gateway machines, in this location:
Code Block c:\Program files\Caringo Filefly\data\FileFly Agent\s3.cfg
Restart the FileFly Agent service to apply the changes.
Configuring
...
the Destination
The next step is to configure the new Destination (target for migration) in FileFly.
Browse to your the FileFly Admin Portal.
Select Destinations and then Create Destination:
On Paste the destination URI from the clipboard on the Create Destination page, paste the destination URI that was placed on your clipboard:
Ensure that Verify the Name you choose makes clear what the target is , and add any useful details in the Comments field.
Update the URI you pasted with the correct value for the placeholder, YOUR_GATEWAY_HERE, which is the FQDN of your the migration agent.
In this example, the FQDN is
ffservertonyl.saleslab01.dom, so the complete URI is as follows:Code Block s3://ffservertonyl.saleslab01.dom/example-bucket-for-filefly
Select Save, and then the destination is ready for use with a migration policy.
Configuring
...
the Task
As with all destinations in FileFly, the last step is to create Create a task chain that will to make use of the new destination you configured.
To move data to AWS, set Set up these components as usual (refer to FileFly Documentation for details) to move data to AWS.
Source
Rule
Policy
Task
When these are configured, run the Task to test it:
