SECURITY WARNING: Never run commands you don't understand. Always review code before execution. Use at your own risk.
FixMyError.net
Storage 13 errors

Object & Block Storage Errors

S3 permissions, NFS mounts, quotas, signed URLs and volume attachment.

Understanding Storage errors

Storage errors are dominated by permissions and locality. S3 access denials can come from an IAM policy, a bucket policy, a Block Public Access setting, an ACL or a KMS key policy: five independent layers, all of which must allow the call. Block storage errors are usually about availability zones: a volume can only attach to an instance in the same AZ.

How to debug Storage errors

  1. For S3 denials, check all five layers: IAM policy, bucket policy, Block Public Access, object ACL and the KMS key policy if the object is encrypted with a customer-managed key.
  2. Confirm the region and the exact bucket name. A bucket in another region returns a redirect or a permanent error that reads like a permission problem.
  3. For signed URLs, check the expiry and that the clock on the signing machine is correct. A skewed clock produces URLs that are already expired.
  4. For NFS stale file handles, remount rather than retrying; the file the handle referred to no longer exists on the server.
  5. For volume attachment failures, verify the availability zone matches and that the volume is in the available state, not still attached elsewhere.

Tools worth reaching for

  • aws s3api get-bucket-policy
  • IAM Policy Simulator
  • mount -v / showmount -e
  • df -h / du -sh
  • aws ec2 describe-volumes

All 13 Storage errors

Other categories