AWS Security ChangesHomeSearch

AWS AmazonS3: Add MISCONFIGURED status troubleshooting for S3 Files

Service: AmazonS3 · 2026-10-21 · Documentation medium

File: AmazonS3/latest/userguide/s3-files-troubleshooting.md · Type: iam

Summary

Adds a new troubleshooting section explaining the MISCONFIGURED file system status, covering IAM role trust policy, bucket policy/SCP denials, per-prefix permissions, and KMS key policy requirements, plus a warning about data becoming permanently out of sync after 60 days.

Security assessment

The new section documents IAM role assumption, bucket policy/SCP authorization, and KMS key policy requirements needed for S3 Files to import/export data. It is security best-practice/hardening guidance (permissions and encryption key access) rather than a fix for a specific vulnerability or incident.

Evidence

+  * S3 Files can't use the KMS keys that encrypt your objects. If your bucket uses AWS Key Management Service (AWS KMS) encryption, or if some objects use a different encryption key than the bucket default, make sure that the key policy of each key allows the IAM role of your file system to use the key. For more information, see [S3 Files key policies for AWS KMS](./s3-files-encryption.html#s3-files-encryption-key-policies).

Diff

diff --git a/AmazonS3/latest/userguide/s3-files-troubleshooting.md b/AmazonS3/latest/userguide/s3-files-troubleshooting.md
index 6ae2436..14692df 100644
--- a//AmazonS3/latest/userguide/s3-files-troubleshooting.md
+++ b//AmazonS3/latest/userguide/s3-files-troubleshooting.md
@@ -7 +7 @@
-Mount command failsPermission denied on file operationsIntelligent read routing is not workingFile system consistently returns NFS server errorMissing object in S3 bucket after file system writeS3 object not visible in the file systemFiles appearing in the lost and found directorySynchronization falling behindEnabling client debug logsError messages
+Mount command failsPermission denied on file operationsIntelligent read routing is not workingFile system consistently returns NFS server errorMissing object in S3 bucket after file system writeS3 object not visible in the file systemFiles appearing in the lost and found directorySynchronization falling behindFile system status is MISCONFIGUREDEnabling client debug logsError messages
@@ -28,0 +29,2 @@ This page helps you diagnose and resolve common issues with S3 Files.
+  * File system status is MISCONFIGURED
+
@@ -190,0 +193,27 @@ This means that your workload may be exceeding the synchronization rate. S3 File
+## File system status is MISCONFIGURED
+
+If your file system status is MISCONFIGURED, insufficient permissions prevent S3 Files from importing or exporting data between your file system and your S3 bucket. Changes don't synchronize until you correct the configuration.
+
+The common causes are:
+
+  * S3 Files can't assume the AWS Identity and Access Management (IAM) role. Make sure that the trust policy of the IAM role allows S3 Files to assume the role. If the role was deleted or renamed, recreate the role or update your file system to use the correct role.
+
+  * The IAM role doesn't have permission to access the S3 bucket. Make sure that the IAM role has a policy that grants access to the linked S3 bucket.
+
+  * A bucket policy or a service control policy (SCP) denies access. Make sure that your S3 bucket policy and any AWS Organizations SCPs don't deny access to the IAM role of your file system.
+
+  * S3 Files doesn't have permission for a specific key or prefix. If some of your data imports and exports successfully, S3 Files can be missing permission for only part of the bucket under the prefix of your file system. Check the IAM role of your file system, the S3 bucket policy, and the Object Ownership settings of the bucket.
+
+  * S3 Files can't use the KMS keys that encrypt your objects. If your bucket uses AWS Key Management Service (AWS KMS) encryption, or if some objects use a different encryption key than the bucket default, make sure that the key policy of each key allows the IAM role of your file system to use the key. For more information, see [S3 Files key policies for AWS KMS](./s3-files-encryption.html#s3-files-encryption-key-policies).
+
+
+
+
+For more information, see [IAM role for accessing your bucket from the file system](./s3-files-prereq-policies.html#s3-files-prereq-iam-creation-role) and [How S3 Files works with IAM](./s3-files-security-iam.html).
+
+After you correct the configuration, S3 Files automatically retries failed imports and exports. When all failed imports and exports complete, the status of your file system changes to AVAILABLE. It can take more than 24 hours for the status to change to AVAILABLE after you correct the configuration.
+
+###### Important
+
+If your file system has the MISCONFIGURED status for more than 60 days, some data can become permanently out of sync with your S3 bucket. Correct the configuration as soon as possible. If this occurs, contact AWS Support.
+