SECURITY Signal 459
S3-compatible storage at six neoclouds lacks AWS security protections, Wiz finds
↗
Wiz researchers found that S3-compatible object storage services across six neoclouds lack significant security protections that Amazon S3 provides, including varying public-access controls, weaker access-key formats, and divergent IAM semantics.
Teams migrating workloads to S3-compatible providers cannot assume AWS security behaviors carry over, and some API differences are dangerous, one provider's delete-bucket-policy deleted the entire bucket. Credential detection tools like GitHub's secret scanner also miss non-AWS access keys, increasing exposure to leaked credentials.
Written by elseif from the cluster below · every claim links back to a sourceThe three things worth knowing
S3-compatible services across six neoclouds handle public buckets, access keys, and IAM differently from Amazon S3, creating security gaps.
Vulnerabilities in S3-compatible implementations have included unauthorized privilege escalation in MinIO and broken tenant isolation in RustFS.
Credentials for S3-compatible services lack structured patterns, making them invisible to secret scanners like GitHub's.
THE CLUSTER