Amazon Elastic Compute Cloud Developer Guide Additional Web Services References <code>0</code> <name>pending</name> <instanceId>i-2bc64242</instanceId> <imageId>ami-60a54009</imageId> <code>0</code> <name>pending</name> <dnsName>domU-13-35-33-00-00-5C.dc2.compute.amazonaws.com</dnsName> <instanceId>i-2be64332</instanceId> <imageId>ami-60a54009</imageId> <code>0</code> <name>pending</name> <dnsName>domU-12-34-28-00-00-5C.dc2.compute.amazonaws.com</dnsName> Additional Web Services References • Web Service Description Language (WSDL) • WS-Security BinarySecurityToken Profile Using the Query API Making Requests HTTP Query-based requests are defined as any HTTP requests using the HTTP verb GET or POST and a Query parameter named either Action or Operation. Action is used throughout this documentation, although Operation is supported for backward compatibility with other AWS Query APIs. Query Parameters Each Query request must include some common parameters to handle authentication and selection of an action. These parameters are documented in the section called “Common Query Parameters”. Some operations take lists of parameters. These lists are specified using the param.n notation. Values of n should be integers starting from 1. Query API Authentication Every request to Amazon EC2 must contain a request signature. A request signature is calculated by constructing a string and then calculating an RFC 2104-compliant HMAC-SHA1 hash, using the Secret AWS Access Key as the key. For more information, see http://-www.faqs.org/-rfcs/-rfc2104.html. The following are the basic steps used in authenticating requests to AWS. It is assumed that the developer has already registered with AWS and received an Access Key ID and Secret Access Key. 1. The sender constructs a request to AWS. API Version 2007-03-01 40
The new reader is still in beta!