AWS

More documents

Recommendations

Info

Amazon Simple Queue Service Developer Guide Endpoints Endpoints For information about this product's regions and endpoints, go to Regions and Endpoints in the Amazon Web Services General Reference. Important Some older clients may not be able to access these endpoints over SSL. In that case, we recommend that you either use the alternative endpoints listed below, upgrade your client, or change your client. • queue.amazonaws.com—The endpoint for the US-East (Northern Virginia) Region • us-west-1.queue.amazonaws.com—The endpoint for the US-West (Northern California) Region • eu-west-1.queue.amazonaws.com —The endpoint for the EU (Ireland) Region • ap-southeast-1.queue.amazonaws.com —The endpoint for the Asia Pacific (Singapore) Region For example, to create a queue in Europe, you would generate a Query request similar to the following: http://sqs.eu-west-1.amazonaws.com/ ?Action=CreateQueue &DefaultVisibilityTimeout=40 &QueueName=testQueue &Version=2009-02-01 &SignatureMethod=HmacSHA256 &Expires=2009-04-18T22%3A52%3A43PST &AWSAccessKeyId=0GS7553JW74RRM612K02EXAMPLE &SignatureVersion=2 &Signature=Dqlp3Sd6ljTUA9Uf6SGtEExwUQEXAMPLE Each Amazon SQS endpoint is entirely independent. For example, if you have two queues called "MyQueue," one in sqs.us-east-1.amazonaws.com and one in sqs.eu-west-1.amazonaws.com, they are completely independent and do not share any data. API Version 2009-02-01 13
Amazon Simple Queue Service Developer Guide Making Query Requests Making Query Requests Topics • Structure of a GET Request (p. 14) • Structure of a POST Request (p. 15) • Related Topics (p. 16) Amazon SQS supports Query requests for calling service actions. Query requests are simple HTTP or HTTPS requests, using the GET or POST method. Query requests must contain an Action parameter to indicate the action to be performed. The response is an XML document that conforms to a schema. Structure of a GET Request This guide presents the Amazon SQS GET requests as URLs, which can be used directly in a browser. The URL consists of: • Endpoint—The resource the request is acting on (in the case of SQS, the endpoint is a queue) • Action—The action you want to perform on the endpoint; for example: sending a message • Parameters—Any request parameters The following is an example GET request to send a message to an SQS queue. http://sqs.us-east- 1.amazonaws.com/123456789012/queue1?Action=SendMessage&MessageBody=Your%20Message%20Text &AWSAccessKeyId=0GS7553JW74RRM612K02EXAMPLE&Version=2009-02-01&Expires=2008-02- 10T12:00:00Z&Signature=lBP67vCvGlDMBQ1do fZxg8E8SUEXAMPLE&SignatureVersion=2&SignatureMethod=HmacSHA256 Important Because the GET requests are URLs, you must URL encode the parameter values. For example, in the preceding example request, the value for the MessageBody parameter is actually Your Message Text. However, spaces are not allowed in URLs, so each space is URL encoded as "%20". The rest of the example has not been URL encoded to make it easier for you to read. To make the GET examples even easier to read, this guide presents them in the following parsed format. http://sqs.us-east-1.amazonaws.com/123456789012/queue1 ?Action=SendMessage &MessageBody=Your%20Message%20Text &AWSAccessKeyId=0GS7553JW74RRM612K02EXAMPLE &Version=2009-02-01 &Expires=2008-02-10T12:00:00Z &Signature=lBP67vCvGlDMBQ1dofZxg8E8SUEXAMPLE &SignatureVersion=2 &SignatureMethod=HmacSHA256 Note In the example Query requests we present in this guide, we use a false AWS Access Key ID and false signature, each with EXAMPLE appended. We do this to indicate that you shouldn't expect API Version 2009-02-01 14
Page 1 and 2: Amazon Simple Queue Service Develop
Page 15: Amazon Simple Queue Service Develop
Page 67 and 68:
Amazon Simple Queue Service Develop
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
show all

AWS

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?