


 Resolution
-----------



1.    Update your resource's AWS Identity and Access Management (IAM) [resource-based policy](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html#policies_resource-based) to allow Amazon SNS access to the resource. For more information, see [Editing IAM policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_manage-edit.html) in the AWS IAM user guide. 


2.    Verify that your resource's IAM resource-based policy doesn’t include any **Deny** statements that [explicitly deny](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_evaluation-logic.html#AccessPolicyLanguage_Interplay) your Amazon SNS topic access to the resource.  
**Note:** AWS Lambda function IAM resource-based policies don't include the option to add an explicit deny statement.





---




 Related information
--------------------



[Access management for AWS resources](https://docs.aws.amazon.com/IAM/latest/UserGuide/access.html)


[Amazon SNS event destinations](https://docs.aws.amazon.com/sns/latest/dg/sns-event-destinations.html)







When my Amazon Simple Notification Service (Amazon SNS) topic tries to publish messages to another AWS resource, I get an HTTP 400 "AccessDeniedException" error. How do I resolve the error?

Resolve “AccessDeniedException” errors from Amazon SNS

How do I resolve HTTP 400 “AccessDeniedException” errors from Amazon SNS?

How do I resolve HTTP 400 “AccessDeniedException” errors from Amazon SNS?

Resolution

Related information

Contenido relevante