SOAP without WS-Security

	Important
	If you do not intend to use WS-Security, you must be using SOAP 1.1. SOAP 1.2 is not supported in this situation.

Authentication of SOAP requests without WS-Security uses your AWS credentials and an HMAC-SHA1 signature. You include the authentication information in the following required elements of the SOAP request:

AWSAccessKeyId: Your AWS Access Key ID

Timestamp: This must be a dateTime ( http://www.w3.org/TR/xmlschema-2/#dateTime) in the Coordinated Universal Time (Greenwich Mean Time) time zone, such as 2005-01-31T23:59:59:183Z. The request expires 15 minutes after the time stamp.

	Note
	Due to different interpretations regarding how extra time precision should be dropped, .NET users should take care not to send overly specific time stamps. This can be accomplished by manually constructing `dateTime` objects with no more than millisecond precision.

Signature: The HMAC-SHA1 signature (http://www.ietf.org/rfc/rfc2104.txt) calculated from the concatenation of Action+Timestamp, using your AWS Secret Access Key as the key. For example, in the sample request below, the value of the Signature element is the HMAC-SHA1 digest of this string: CreateQueue2005-01-31T23:59:59.183Z
The following example shows a snippet from a SOAP request that creates a queue called "MyQueue".
```
<CreateQueue xmlns="http://queue.amazonaws.com/doc/2007-05-01/">
  <AWSAccessKeyID>1D9FVRAYCP1VJS767E02EXAMPLE</AWSAccessKeyID>
  <Timestamp>2007-05-01T23:59:59.183Z</Timestamp>
  <Signature>SZf1CHmQ/nrZbsrC13hCZS061yws</Signature>
  <QueueName>MyQueue</QueueName>
</CreateQueue>
```

To calculate the signature

Concatenate the values of the Action and Timestamp request parameters, in that order.

Calculate an HMAC-SHA1 signature, using your Secret Access Key as the key.
Convert the resulting value to base64.
Pass the final value in the Signature parameter of the SOAP request.

Important

The SQS schema currently does not include the AWSAccessKeyID, Timestamp, and Signature parameters. Even though you're not using WS-Security for authentication, you must still place them inside the root element of the request. If you're using a toolkit that generates stubs from the WSDL, the code generated by the toolkit won't include the three parameters. You still have to insert them into the root element.