Cross-Account S3 Access Still Fails. Just Open It Up?
A partner account still gets AccessDenied on your encrypted S3 objects after you added a bucket policy. A teammate wants to make the bucket and key public. Defend the right fix.
Answer key reviewed by Branko Petric
Read first: AWS IAM: Users, Roles, and Policies
Your decision
You granted a partner account access to your S3 bucket with a bucket policy, but their role still gets AccessDenied reading the objects, which are encrypted with a customer-managed KMS key. A teammate says just make the bucket public and let the key allow everyone. What do you do?
The situation
A partner in another AWS account needs to read objects from one of your S3 buckets. You added a bucket policy that allows their role, but their requests still come back as AccessDenied.
Context
The objects are encrypted with a customer-managed KMS key in your account. The partner role has IAM permissions on their side to call S3. Nobody has touched the KMS key policy. A teammate, frustrated after trying bucket policy tweaks, suggests turning off Block Public Access, making the bucket public, and setting the KMS key policy to allow all principals so the partner can finally read the data.
Related challenges
- Your S3 Website Returns 403. Make the Bucket Public?
Objects in S3 return 403 and a teammate wants to turn off Block Public Access to fix it fast. Defend the right way to grant access.
- Access Keys Are Hardcoded on the EC2 Box. Just Rotate Them?
An app on EC2 authenticates to AWS with long-lived IAM user keys in a config file. One leaked. Defend the real fix.
- The t3 Instance Got Slow. Just Size It Up?
An app on a t3 instance crawls under steady load and a teammate wants a bigger instance. Defend what is actually throttling it.
- Lambda Is Exhausting Your RDS Connections. Raise the Limit?
Under load, Lambda functions fail with too many connections to RDS. A teammate wants to bump max_connections. Defend the real fix.