SIGNATURE File Parameters

Topics

You use the SIGNATURE file file to identify your storage device in your shipment, the associated job sent by e-mail, and to authenticate your request. You must name this file SIGNATURE and put it in the root directory of your storage device. If this file is missing, AWS cannot process your data. We will return your storage device and you will need to create a new AWS Import/Export job.

You can use the CreateSignature tool to create a SIGNATURE file or you can write your own software to create one. Given the same input, your software must produce the same output as CreateSignature.

	Important
	The CreateSignature tool uses canonical bytes of the manifest file to generate the `SIGNATURE` file. If the manifest file changes at all, even by one byte, you must create a new AWS Import/Export job because the new `SIGNATURE` file created with the altered manifest file will not match the `SIGNATURE` file generated with the original manifest that was included in the `CREATE JOB` e-mail.

SIGNATURE Parameters

The following table describes the parameters in the SIGNATURE file.

Parameter	Description	Required
jobId	Specifies a five character alphanumeric string that uniquely identifies one storage device. AWS issues `jobId` in response to a `CREATE JOB` e-mail command. The string isn't case sensitive and can contain the digits 1 through 9 and letters A-Z, except the letter O. Type: String	Yes
`signature`	Specifies the base64, encoded RFC 2104-compliant HMAC-SHA1 encryption of the values `jobId`, “\n”, and the bytes in the manifest. `CREATE JOB` returns the `jobId`. An “\n” character separates the `jobId` and the manifest file bytes. Manifest file bytes must be put into the canonical format by replacing all instances of “\r\n” with “\n”. These bytes are then signed with your Secret Access Key using the HMAC-SHA1 algorithm. The output is then converted to the base64 format. Type: String	Yes
signingMethod	Specifies the signing method used to generate the `signature`. Type: String Valid Values: HmacSHA1	Yes
version	Identifies the version of the `SIGNATURE` specification used to write the `SIGNATURE` file. Type: String Valid Values: 1.0	Yes

Sample SIGNATURE File

The SIGNATURE file is a UTF8 encoded YAML file. (ASCII is a subset of UTF8.) The following example is a SIGNATURE file.

version: 1.0
signingMethod: HmacSHA1
jobId: 53XTY
signature: d48F0+WdXjgNyc3vOSamplee5qXarDVRs=