Skip to main content

Troubleshooting Amazon S3

Most issues are caused by an incorrectly entered configuration item. Check for typos and confirm that you specified the correct bucket name, region, and keys.

If you specify a region that does not match where the bucket or keys exist, you may see an error such as:

The bucket you are attempting to access must be addressed using the specified endpoint.

Choose the AWS region that corresponds to the location of the bucket and keys.

Account for case sensitivity differences when copying, moving, or syncing files and folders between Amazon S3 and other storage locations. Amazon S3 is case sensitive, while other systems are not. Files can be overwritten and folder contents merged when their case-insensitive names match.

Subfolder-Only Permission

If your S3 user policy does not have access to the entire bucket, or is restricted to specific subfolders, verification of access to the bucket may fail when testing credentials.

Use the advanced setting for Can these credentials access the root of this remote or are they restricted to a subfolder? to specify a subfolder for verifying access when testing your credentials.

S3 Bucket Access Permission Issues

Access to your S3 bucket is determined by the policies and permissions in Amazon S3External LinkThis link leads to an external website and will open in a new tab. If your IAM policy is too restrictive, or contains errors in the details about the IAM user or Actions, your Files.com site may not be able to interact correctly with your S3 bucket.

To troubleshoot, configure your IAM policy with the least restrictive options available and re-test. Apply changes to the IAM policy incrementally to determine which change or option is causing the access issue.

Below is an example S3 user policy that provides full access permissions to your Files.com site (replace <bucketname> with your bucket name):

{
   "Version":"2012-10-17",
   "Statement":[
      {
         "Effect":"Allow",
         "Action": "s3:*",
         "Resource": [
           "arn:aws:s3:::<bucketname>",
           "arn:aws:s3:::<bucketname>/*"
         ]
      }
   ]
}

InvalidObjectState Error When Accessing Files

If Files.com returns an InvalidObjectState error when reading or transferring a file, the object is stored in a Glacier storage class that requires a separate AWS restore request before any service can read it. Files.com supports Glacier Instant Retrieval, which returns data immediately, and does not support Glacier Flexible Retrieval or Glacier Deep Archive.

You have two options. You can manually restore the specific object from Glacier in the AWS Console and retry the operation once the restore completes. For automated and unattended workflows, the better option is to update your S3 Remote Server to use only a supported storage class: Standard, Standard-IA, One Zone-IA, Intelligent-Tiering, or Glacier Instant Retrieval. This avoids manual effort and the delays it introduces in automated workflows.