Amazon S3 is a generic cloud data storage system offered by Amazon Web Services (AWS). S3 storage containers are called 'buckets'. Buckets may be mounted in the virtual file-system of CompleteFTP Enterprise MFT. Once a bucket has been mounted as a folder in CompleteFTP, it may be accessed seamlessly by users in the same way that any other folder is accessed.
CompleteFTP also supports non-AWS S3-compatible storage providers. These services implement the S3 API but are not hosted by Amazon. Examples include Wasabi, MinIO, and others.
Access to a bucket may be granted via either role-based access control or a secret access key.
Role-based access control may be used if CompleteFTP is installed on an AWS EC2 virtual machine instance. An IAM role may be assigned to an instance and this role may be granted access to a bucket. If this has been done then a secret access key is not required.
A secret access key is required in cases where role-based access control is not being used. Each AWS account can have many secret access keys. They may be created and destroyed in the Security Credentials panel of the AWS console. Each secret access key has an 'access key ID'.
Buckets are added to CompleteFTP's virtual file-system in the same way as other folders in the filesystem — via the Folders tab, by choosing New root folder or New sub-folder. In CompleteFTP Enterprise MFT, there is an Amazon S3 Folder menu item.
This brings up the Configure Amazon S3 Folder dialog box.
In the dialog box, select whether you're using Amazon S3 or a Non-AWS S3-compatible service using the radio buttons at the top.
If Amazon S3 is selected, enter: (1) the name of the AWS region in which the bucket exists, (2) the access key ID, (3) the secret access key, (4) the bucket name, and optionally (5) the path of the directory to be mounted. The access key ID and secret access key should be left blank if role-based access control is used. If the directory is left blank then the root of the bucket will be mounted.
If Non-AWS S3-compatible is selected, enter: (1) the service URL of the S3-compatible storage, (2) the access key ID, (3) the secret access key, (4) the bucket name, and optionally (5) the directory path. As with Amazon S3, leaving the directory field blank will mount the root of the bucket.
Once the changes have been applied, the folder should be accessible to connecting clients.