S3 errors

Note: The command prompts were omitted. These log excerpts appear during operations such as connect move, connect copy, or connect list when working with S3 endpoints.

Connection errors

Dial tcp - i/o timeout

2024/12/20 14:34:41 INFO License valid to: 2026-04-13 18:06:28
2024/12/20 14:34:41 INFO Licensed for: Ultimate
2024/12/20 14:34:41 INFO Testing connection to s3://mybucket
2024/12/20 14:34:41 ERROR Error while testing connection: dial tcp s3.amazonaws.com:443: i/o timeout

S3 client was unable to establish a TCP connection to the S3 endpoint within the allowed timeout period.

Possible causes:

S3 endpoint is down or unreachable
network issues (different subnets, no route, or disconnected network)
a firewall (on the client, target, or intermediate network) is blocking connections
timeout is too short
DNS resolution issues preventing connection to the S3 endpoint

Dial tcp - connection refused

2024/12/31 09:15:26 INFO License valid to: 2026-04-13 18:06:28
2024/12/31 09:15:26 INFO Licensed for: Ultimate
2024/12/31 09:15:26 INFO Testing connection to s3://mybucket
2024/12/31 09:15:26 ERROR Error while testing connection: dial tcp s3.amazonaws.com:443: connect: connection refused

S3 client was unable to establish a TCP connection to the S3 endpoint as the connection was actively refused by the target machine.

Possible causes:

S3 endpoint is not running or is misconfigured
firewall is blocking the target port (typically 443 for HTTPS)
proxy configuration issues
custom S3 endpoint is not accessible

File transfer interrupted due to no network activity

2024/12/31 13:26:52 INFO License valid to: 2026-04-13 18:06:28
2024/12/31 13:26:52 INFO Licensed for: Ultimate
2024/12/31 13:26:52 INFO Sending files to s3://mybucket/
2024/12/31 13:26:54 INFO Transferring file=test-file.zip
2024/12/31 13:27:02 ERROR Failed to transfer file error=file transfer interrupted due to no network activity for 30s file=test-file.zip

This error occurs when an S3 transfer is interrupted due to network inactivity exceeding the configured timeout.

Possible causes:

intermittent or unstable network connection between the client and S3
high latency or packet loss causing connection stalls
firewall or NAT timeout closing the connection prematurely
network bandwidth issues causing slow transfers
transferring large files over unstable connections

Authentication errors

Error getting s3 connection - Access Denied

2024/12/31 10:42:16 INFO License valid to: 2026-04-13 18:06:28
2024/12/31 10:42:16 INFO Licensed for: Ultimate
2024/12/31 10:42:16 INFO Testing connection to s3://access:secret:us-east-1@mybucket
2024/12/31 10:42:18 ERROR Error getting s3 connection: Access Denied

S3 client attempted to connect to the remote server but was unable to authenticate successfully with the provided credentials.

Possible causes:

access key or secret key provided for the S3 user is incorrect
credentials have expired or been revoked
IAM user does not have sufficient permissions for the requested operation
credentials are being used with the wrong region or bucket
MFA (Multi-Factor Authentication) is required but not configured

Failed to decode base64 secret key

2024/12/31 08:47:51 INFO License valid to: 2026-04-13 18:06:28
2024/12/31 08:47:51 INFO Licensed for: Ultimate
2024/12/31 08:47:51 INFO Testing connection to s3://mybucket
2024/12/31 08:47:51 ERROR failed to decode base64 secret key: illegal base64 data at input byte 0

S3 client is trying to use a base64-encoded secret key but the encoding is invalid.

Possible causes:

secret key is not properly base64 encoded
secret key contains invalid characters or formatting
secret key was truncated or corrupted

Unrecognized S3 authentication type

2024/12/31 10:47:02 INFO License valid to: 2026-04-13 18:06:28
2024/12/31 10:47:02 INFO Licensed for: Ultimate
2024/12/31 10:47:02 INFO Testing connection to s3://mybucket
2024/12/31 10:47:02 ERROR failed to get S3 client: unrecognized S3 authentication type: invalid

S3 client is configured with an unsupported authentication type.

Possible causes:

alias configuration has an invalid authentication type
authentication type in credentials is not one of: static, base64, profile
credentials file is corrupted or has invalid format

Bucket errors

Bucket does not exist

2024/12/31 13:15:57 INFO License valid to: 2026-04-13 18:06:28
2024/12/31 13:15:57 INFO Licensed for: Ultimate
2024/12/31 13:15:57 INFO Testing connection to s3://mybucket
2024/12/31 13:15:58 ERROR Bucket does not exist

S3 client attempted to access a bucket that does not exist in the specified region.

Possible causes:

bucket name is misspelled or incorrect
bucket exists in a different region than specified
bucket was deleted or renamed
incorrect AWS region specified in the connection string
using custom S3 endpoint with incorrect bucket name

No such bucket

2024/12/31 13:15:57 INFO License valid to: 2026-04-13 18:06:28
2024/12/31 13:15:57 INFO Licensed for: Ultimate
2024/12/31 13:15:57 INFO Listing s3://mybucket/
2024/12/31 13:15:58 ERROR not found: no such bucket: mybucket

S3 client attempted to access a bucket that does not exist.

Possible causes:

bucket name is incorrect or does not exist
bucket exists in a different AWS region
bucket was recently deleted and DNS has not propagated
using the wrong AWS credentials or account

Bucket already exists

2024/12/31 13:15:57 INFO License valid to: 2026-04-13 18:06:28
2024/12/31 13:15:57 INFO Licensed for: Ultimate
2024/12/31 13:15:57 ERROR bucket already exists: mybucket

S3 client attempted to create a bucket that already exists.

Possible causes:

bucket name is already in use by another AWS account
bucket already exists and you are trying to recreate it
bucket name is globally unique and already taken

Bucket already owned by you

2024/12/31 13:15:57 INFO License valid to: 2026-04-13 18:06:28
2024/12/31 13:15:57 ERROR bucket already owned by you: mybucket

S3 client attempted to create a bucket that you already own.

Possible causes:

bucket already exists in your AWS account
you are trying to recreate an existing bucket

Object/Key errors

No such key

2024/12/31 13:15:57 INFO License valid to: 2026-04-13 18:06:28
2024/12/31 13:15:57 INFO Getting files from s3://mybucket/path/
2024/12/31 13:15:58 ERROR no such key: path/file.txt

S3 client attempted to access an object that does not exist in the specified bucket.

Possible causes:

object key (file path) is incorrect or does not exist
object was deleted or moved
object path has incorrect case (S3 keys are case-sensitive)
prefix/path separator issues (e.g., missing or extra /)

No such upload

2024/12/31 13:15:57 INFO License valid to: 2026-04-13 18:06:28
2024/12/31 13:15:57 INFO Uploading to s3://mybucket/
2024/12/31 13:15:58 ERROR no such upload: uploadId

S3 client attempted to resume or complete a multipart upload that does not exist.

Possible causes:

multipart upload ID is invalid or expired
upload was aborted or completed previously
upload was interrupted and not properly resumed

Not found

2024/12/31 13:15:57 INFO License valid to: 2026-04-13 18:06:28
2024/12/31 13:15:57 INFO Getting file from s3://mybucket/file.txt
2024/12/31 13:15:58 ERROR not found: The specified key does not exist

S3 client attempted to access a resource that does not exist.

Possible causes:

object or bucket does not exist
incorrect path or key specified
object was deleted or moved
permission issues preventing access (may appear as “not found”)

Request errors

Invalid request

2024/12/31 13:15:57 INFO License valid to: 2026-04-13 18:06:28
2024/12/31 13:15:57 INFO Uploading to s3://mybucket/
2024/12/31 13:15:58 ERROR invalid request: The request signature we calculated does not match the signature you provided

S3 client sent a request that was rejected by the S3 service.

Possible causes:

incorrect AWS credentials (access key or secret key)
request was modified in transit (possible security issue)
system clock is out of sync with S3 servers
invalid request parameters or headers

Invalid write offset

2024/12/31 13:15:57 INFO License valid to: 2026-04-13 18:06:28
2024/12/31 13:15:57 INFO Uploading to s3://mybucket/
2024/12/31 13:15:58 ERROR invalid write offset: The specified offset is invalid

S3 client attempted to write to an invalid offset in a multipart upload.

Possible causes:

concurrent write attempt (S3 does not support concurrent copy)
offset is negative or exceeds file size
multipart upload state is corrupted

Invalid object state

2024/12/31 13:15:57 INFO License valid to: 2026-04-13 18:06:28
2024/12/31 13:15:57 INFO Copying s3://mybucket/file.txt
2024/12/31 13:15:58 ERROR invalid object state: The operation is not valid for the current state of the object

S3 client attempted an operation on an object that is not in the correct state.

Possible causes:

object is being modified by another process
object is in a different storage tier (e.g., Glacier)
object is locked or has a legal hold
multipart upload is in progress

Encryption type mismatch

2024/12/31 13:15:57 INFO License valid to: 2026-04-13 18:06:28
2024/12/31 13:15:57 INFO Copying s3://mybucket/file.txt
2024/12/31 13:15:58 ERROR encryption type mismatch: The encryption request was not properly configured

S3 client attempted an operation with mismatched encryption settings.

Possible causes:

source and destination have different encryption configurations
encryption key or KMS settings are incorrect
SSE (Server-Side Encryption) configuration mismatch

Object already in active tier

2024/12/31 13:15:57 INFO License valid to: 2026-04-13 18:06:28
2024/12/31 13:15:57 INFO Copying s3://mybucket/file.txt
2024/12/31 13:15:58 ERROR object already in active tier: The object is already in the active tier

S3 client attempted to change the storage tier of an object that is already in the target tier.

Possible causes:

object is already in the requested storage tier
duplicate tier change request

Object not in active tier

2024/12/31 13:15:57 INFO License valid to: 2026-04-13 18:06:28
2024/12/31 13:15:57 INFO Copying s3://mybucket/file.txt
2024/12/31 13:15:58 ERROR object not in active tier: The object is not in the active tier

S3 client attempted to access an object that is not in an accessible storage tier.

Possible causes:

object is in archival storage (e.g., Glacier)
object is being restored from archival storage
object is in a transition state

Too many parts

2024/12/31 13:15:57 INFO License valid to: 2026-04-13 18:06:28
2024/12/31 13:15:57 INFO Uploading large file to s3://mybucket/
2024/12/31 13:15:58 ERROR too many parts: The multipart upload has too many parts

S3 client attempted to create a multipart upload with too many parts.

Possible causes:

file is too large for the configured part size
multipart upload exceeded the maximum number of parts (10,000)
incorrect part size configuration

URI format errors

Invalid S3 URI format for custom installation

2024/12/31 08:54:52 INFO License valid to: 2026-04-13 18:06:28
2024/12/31 08:54:52 ERROR invalid S3 URI format for custom installation: s3://key:secret:region@host:port@bucket/path

S3 client encountered an invalid URI format for a custom S3 installation.

Possible causes:

URI format is incorrect for custom S3/MinIO endpoints
missing host:port or bucket components
incorrect number of @ separators (should be 2 for custom endpoints)

Correct format: s3://access:secret:region@host:port@bucket/path

Invalid S3 URI format for AWS

2024/12/31 08:54:52 INFO License valid to: 2026-04-13 18:06:28
2024/12/31 08:54:52 ERROR invalid S3 URI format for AWS: s3://key:secret:region@bucket/path

S3 client encountered an invalid URI format for AWS S3.

Possible causes:

URI format is incorrect for AWS S3
missing credentials or region components
incorrect number of @ separators (should be 1 for AWS)

Correct format: s3://access:secret:region@bucket/path

Invalid credentials format

2024/12/31 08:54:52 INFO License valid to: 2026-04-13 18:06:28
2024/12/31 08:54:52 ERROR invalid credentials format, expected Access_Key:Secret_Key:REGION before @bucket/path

S3 client encountered an invalid credentials format in the URI.

Possible causes:

credentials are not in the correct format (Access_Key:Secret_Key:REGION)
missing or extra colons in credentials
region is missing or incorrectly specified

Other errors

S3 does not support concurrent copy

2024/12/31 13:15:57 INFO License valid to: 2026-04-13 18:06:28
2024/12/31 13:15:57 INFO Copying s3://src-bucket/file.txt s3://dst-bucket/file.txt
2024/12/31 13:15:58 ERROR S3 does not support concurrent copy

S3 client attempted a concurrent copy operation which is not supported by S3.

Possible causes:

attempting to copy between two S3 endpoints using concurrent mode
S3 does not support random access writes required for concurrent copying

Solution: The tool will automatically fall back to sequential copying for S3-to-S3 transfers.

Failed to create destination folder

2024/12/31 13:15:57 INFO License valid to: 2026-04-13 18:06:28
2024/12/31 13:15:57 INFO Getting files from s3://mybucket/file.txt
2024/12/31 13:15:58 ERROR failed to create destination folder: no such file or directory

S3 client attempted to download a file but the local destination directory does not exist.

Possible causes:

local destination directory does not exist
path to destination directory does not exist
insufficient permissions to create the directory

Failed to open source file

2024/12/31 13:15:57 INFO License valid to: 2026-04-13 18:06:28
2024/12/31 13:15:57 INFO Sending files to s3://mybucket/
2024/12/31 13:15:58 ERROR failed to open source file: no such file or directory

S3 client attempted to upload a file but the local source file does not exist.

Possible causes:

local source file does not exist
file path is incorrect
insufficient permissions to read the file