This is version 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 . It is not the current version, and thus it cannot be edited.
[Back to current version]   [Restore this version]

S3 Integration Overview:
#

The Amazon S3 REST API provides a comprehensive set of HTTP operations for managing and interacting with objects and buckets in Amazon S3. Amazon S3 API Reference Link
Authentication: Supports AWS Signature Version 4 for secure request authentication.

---

⚠️ General restrictions: This integration allows you to use an Amazon S3 bucket as the backend virtual file system (VFS) in CrushFTP. However, since S3 is not a true hierarchical file system, folder structures are simulated using object key prefixes. As a result, renaming folders is not supported. These are not limitations imposed by CrushFTP, but inherent to S3’s object storage architecture, which is optimized for static content access, not for dynamic file manipulation.

---

⚠️ Proxy Configuration: If your server accesses the internet through a proxy, ensure that the necessary S3 domains are whitelisted to allow successful communication with the S3 REST API.

---

1. Amazon S3 Configuration.
#

The URL should be structured as follows (replace placeholders with your actual values):

General S3 : s3://ACCESS_KEY_ID:SEECRET_ACCESS_KEY@SERVER/BUCKET/

Amazon S3 Example: s3://AKIAEXAMPLE:abcd1234example@s3.amazonaws.com/my-bucket/

1.1 Access Key Authentication
#

To authenticate using standard Amazon S3 credentials:
• Access Key ID – Your AWS access key.
• Secret Access Key – The corresponding secret key.

The Access Key ID and Secret Access Key are generated and offered for download when creating an S3 user (IAM user) in the AWS Management Console (More info: Manage access keys for IAM users Link). ⚠️ Make sure to save them securely, as the secret key will not be shown again.

The S3 Server Endpoint and Bucket Name can be found in the AWS Console under: S3 -> Buckets. This information is required to correctly configure your S3 integration.

1.2 Amazon EC2 IAM Authentication Support
#

CrushFTP supports S3 authentication using IAM roles assigned to EC2 instances. This allows secure access without embedding static credentials.
To use this mode:
• Set the S3 Username to: iam_lookup
• Set the S3 Password to: lookup

This instructs CrushFTP to automatically retrieve temporary credentials from the EC2 instance’s IAM role via the instance metadata service. Use this approach to securely avoid hardcoding static credentials in environments where IAM roles are configured properly.

General EC2-Related Settings (Admin -> Preferences -> Misc -> S3 Configuration):

• Enable IMDSv2: IMDS (Instance Metadata Service) v2 is the more secure version of the metadata endpoint used by EC2 instances to retrieve IAM role credentials. Enabling this option ensures that CrushFTP uses token-based access to the metadata service, protecting against SSRF attacks and adhering to AWS security best practices. ⚠️ Always enable IMDSv2 unless your instance or security policies require legacy IMDSv1.

• EC2 Use relative URL: When enabled, CrushFTP uses a relative URI path instead of an absolute path when communicating with the EC2 metadata service (http://169.254.169.254). This setting may be required in hardened environments or with certain proxy configurations that restrict full URL usage for local metadata requests. ⚠️ Note: Only enable this setting if you are encountering metadata access issues or are instructed to do so by AWS or your network/security administrator.

1.3 Required S3 IAM Policy Permissions
#

To allow proper integration with Amazon S3, ensure that your IAM user or role has the following permissions assigned:

"s3:GetBucketLocation",
"s3:ListAllMyBuckets",
"s3:ListBucket",
"s3:ListBucketMultipartUploads",
"s3:PutObject",
"s3:AbortMultipartUpload",
"s3:ListMultipartUploadParts",
"s3:DeleteObject",
"s3:GetObject",
"s3:GetObjectAttributes"

Permission	Description	Why It’s Needed
s3:GetBucketLocation	Retrieves the AWS region of a specified bucket.	Required to validate bucket location and endpoint.
s3:ListAllMyBuckets	Lists all buckets owned by the requester.	Needed if the application dynamically lists available buckets.
s3:ListBucket	Lists objects within a specific bucket.	Allows viewing file/folder listings in a bucket.
s3:ListBucketMultipartUploads	Lists ongoing multipart uploads in a bucket.	Enables resuming or cleaning up incomplete multipart uploads.
s3:PutObject	Uploads an object to a bucket.	Required for writing (uploading) files.
s3:AbortMultipartUpload	Cancels an in-progress multipart upload.	Used to clean up failed or cancelled large file uploads.
s3:ListMultipartUploadParts	Lists parts of a multipart upload.	Required when managing multipart uploads for large files.
s3:DeleteObject	Deletes an object from a bucket.	Allows file deletion capabilities.
s3:GetObject	Downloads or retrieves an object.	Required to read or download files.
s3:GetObjectAttributes	Retrieves metadata and properties of an object (e.g., size, last-modified).	Useful for showing detailed file info without downloading the entire object.

You may scope the "Resource" field to specific buckets or prefixes for more secure and limited access (e.g., "arn:aws:s3:::your-bucket-name/*").
⚠️ Important: In the CrushFTP S3 Remote item configuration, be sure to check the Don’t check the Bucket at login flag if the user does not have permission to list or access the bucket root directly.

1.4 S3 Remote VFS settings
#

Select the S3 remote item type.

Server: The base domain of the S3-compatible server (s3.us-east-1.amazonaws.com for Amazon S3). This can be replaced with endpoints for non-Amazon providers.
Bucket: The S3 bucket name where files will be stored.
Path: Optional folder path within the bucket to restrict or set as the default working directory.

Accelerate: (For AWS only) Enables S3 Transfer Acceleration — faster uploads/downloads using AWS edge locations.
Fast S3 item lookup: Enables a faster way to resolve S3 items. ⚠️ Must be enabled! Without this option, CrushFTP may perform slower lookups, especially on buckets with a large number of objects.
SHA256 enabled on signing (Signing Version 4): ⚠️ Uses AWS Signature Version 4 for authentication (required in most regions now).
Show Partial Uploads: When enabled, incomplete (multipart) uploads will appear in the file listing. Useful for debugging or managing failed uploads. Usually disabled to avoid cluttering the file list.
Use Bucket in Path: Includes the bucket name as part of the S3 object key/path. This is typically not required unless working with a non-standard or custom S3-compatible backend that expects this behavior.// Don’t check bucket at login: Skips checking if the bucket exists on login. Useful if your credentials lack s3:ListBucket permissions or the bucket is very large. Useful for non-Amazon providers too.
List Version 2: Enables S3 ListObjectsV2 API, which is more efficient and recommended over the legacy ListObjects (v1). Supports better pagination and consistent performance.Should be enabled for all modern S3 services unless the backend only supports the older version.

User Name: Your S3 Access Key ID
Password: Your Secret Access Key

Server Side Encrypt?: When checked, files uploaded to S3 will use Amazon S3 Server-Side Encryption (SSE-S3). This tells S3 to encrypt objects at rest using AWS-managed keys. If you want to use KMS keys instead, leave this unchecked and provide a key in the KMS Key Id field.

Canned ACL: Sets default Access Control for uploaded files: private, public-read, authenticated-read
Storage Class: S3 storage tier. Like: STANDARD, GLACIER, INTELLIGENT_TIERING
KMS Key Id: Optional: If using AWS KMS encryption, provide the full ARN of the key here.
Assume Role ARN: Optional. For cross-account access using IAM Role with sts:AssumeRole.
Assume Role Region: AWS region where the IAM role resides (needed with Assume Role ARN).

---

2. Access other cloud storage through S3 REST API
#

Google Cloud - Google Cloud Storage Access Through S3 REST API
BackBlaze(b2) - BackBlaze(b2) Access Through S3 REST API

---

3. Assume Role access
#

You can use IAM roles to delegate access to your AWS resources. With IAM roles, you can establish trust relationships between your trusting account and other AWS trusted accounts. (for more info see: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-user.html, and https://docs.aws.amazon.com/STS/latest/APIReference/API_AssumeRole.html)

Create the assume role at Identity and Access Management (IAM):









Add permission policy to the specified user. This policy will use the above-created assume role.

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "Statement1",
            "Effect": "Allow",
            "Action": "sts:AssumeRole",
            "Resource": "arn:aws:iam::XXXXX:role/AssumeRoleS3"
        }
    ]
}

Use the specified user's Access key and Secret along with the Assume Role ARN to obtain S3 access.