sqs-dg-2009-02-01

More documents

Recommendations

Info

Amazon Simple Queue Service Developer GuideBasic Use Cases for Access Control{}"Version":"2008-10-17","Id":"UseCase4","Statement" : [{"Sid":"1","Effect":"Deny","Principal" : {"AWS": "123456789012"},"Action":["sqs:SendMessage","sqs:ReceiveMessage"],"Resource": "/987654321000/queue2",}]From these use cases, you can see that if you want to restrict access based on special conditions ordeny someone access entirely, you need to read this appendix and learn how to write your own policies.You can also see that the policies themselves are not that complex and the access policy language isstraightforward.API Version 2009-02-0145
Amazon Simple Queue Service Developer GuideHow to Write a PolicyHow to Write a PolicyTopics• Basic Policy Structure (p. 46)• Element Descriptions (p. 47)• Supported Data Types (p. 55)This section describes how to write policies and gives reference information about each policy element.Basic Policy StructureEach policy is a JSON document. As illustrated in the following figure, a policy includes:• Optional policy-wide information (at the top of the document)• One or more individual statementsEach statement includes the core information about a single permission. If a policy includes multiplestatements, we apply a logical OR across the statements at evaluation time. If multiple policies areapplicable to a request, we apply a logical OR across the policies at evaluation time.The information in a statement is contained within a series of elements. For information about theseelements, see Element Descriptions (p. 47).API Version 2009-02-0146
Page 1 and 2: Amazon Simple Queue ServiceDevelope
Page 3 and 4: Amazon Simple Queue Service Develop
Page 47: Amazon Simple Queue Service Develop

sqs-dg-2009-02-01

Create successful ePaper yourself

Delete template?

Save as template?