# S3 access denied errors now name the SCP or RCP behind the deny

Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.

AWS said on 13 August 2026 that Amazon S3 HTTP 403 errors now include the ARN of the specific policy that caused an explicit deny, for same-account and same-organization requests. The covered policy types are SCPs, RCPs, identity-based policies, session policies and permissions boundaries.

Amazon S3 now includes the specific IAM and AWS Organizations policy Amazon Resource Name in HTTP 403 Access Denied error messages for same-account and same-organization requests, according to an AWS announcement posted 13 August 2026. Previously the message gave the policy type and reason, but with several policies of one type you still had to inspect each one by hand.

For explicit deny cases the message now covers Service Control Policies, Resource Control Policies, identity-based policies, session policies and permission boundaries. AWS says the capability is available in all Regions, including GovCloud and China. For teams running preventive guardrails, this shortens the step from a blocked request to the guardrail that blocked it, which helps when a new SCP or RCP causes unexpected denials.

## Related pages

- [VPC Service Controls quotas now show up in Cloud Quotas](/news/vpc-sc-quota-enforcement-cloud-quotas-ga/)
- [Resource Manager adds management boundaries in preview](/news/resource-manager-management-boundaries-preview/)
- [VPC Service Controls rules can name GKE workload identity principals](/news/vpc-sc-gke-workload-identity-ingress-egress-rules/)
- [All of them](/news/)

## Sources

- https://aws.amazon.com/about-aws/whats-new/2026/08/s3-additional-policy-details-access-denied-error-messages/ (read 10 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://cloudgovernancetools.com/news/s3-access-denied-messages-name-scp-rcp-policy/
