 | Documentation Feedback |  |
This section describes errors, job and device status codes, as well as status codes you might find in AWS Import/Export log files.
There are a number of errors that can occur when sending an e-mail command. The following table describes e-mail error codes.
|
Code |
Description |
|---|---|
|
AccessDenied |
Access Denied. You don’t have write permissions to the specified Amazon S3 bucket. Change the manifest's bucket field to a bucket that the account, specified by the manifest's Access Key ID, has write permissions for. |
|
AccountProblem |
There is a problem with your AWS account that prevents the operation from completing successfully. Please contact customer service at webservices@amazon.com. Fix the account problem or change the manifest's Access Key ID to a different account |
|
CanceledJobId |
The specified job ID has been canceled and is no longer valid. |
|
ExpiredJobId |
The specified job ID has expired and is no longer valid. |
|
InvalidAccess Key ID |
The AWS Access Key ID you provided does not exist in our records. Correct the manifest’s Access Key ID field and resend the CREATE JOB e-mail. |
|
InvalidManifestField |
The manifest file contained one or more invalid fields: Update the manifest file and resubmit. |
|
InvalidJobId |
The specified job ID is not valid. Correct the job ID and resend the e-mail. |
|
InvalidSender |
Your e-mail address is not signed up for this service. Please resend the command from a registered account. |
|
MissingManifestAttachment |
A manifest file attachment was expected, but none was found. Resend a CREATE JOB e-mail with the manifest file attached. |
|
MissingManifestField |
The manifest file was missing one or more required fields:
Update the manifest file and resubmit. |
|
NoSuchBucket |
The specified bucket does not exist. Create the specified bucket or change the manifest's bucket field to a bucket that the account, specified by the manifest's Access Key ID, has write permissions to. |
|
NotSignedUp |
Your AWS account is not signed up for AWS Import/Export. You must sign up before you can use the service. Either sign up the specified account for AWS Import/Export or change the manifest’s Access Key ID to a valid account. |
|
UnableToCancelJobId |
AWS Import/Export cannot cancel a completed job. |
Each AWS Import/Export job has both a device status and job status. The device status is the status of your storage device you mail to us. The job status reflects whether we have loaded your data onto Amazon S3.
The following table describes device status codes.
| Code | Description |
|---|---|
| AtAWS | Your device is at AWS. |
| NotReceived | AWS has not received your device. |
| Returned | Your device has been returned. The SHIPPER
tracking number is TRACKING_NUMBER. |
The following table describes job status codes.
| Code | Description |
|---|---|
| DeviceError | The job was aborted. Your device would not function properly. |
| Expired | The job expired. |
| InProgress | The data on your device is currently being loaded. |
| InvalidSignature | The job was aborted. The SIGNATURE file was invalid. |
| MissingDevice | The job was aborted. Your device, power supply, or device connectors were missing. |
| MissingSignature | The job was aborted. The SIGNATURE file was missing. |
| Pending | The specified job has not started. |
| Success | The data loaded successfully. The import log was saved here:
Import_LOG_URL |
| SuccessWithErrors | The data load completed with NUMBER of
errors.See the import log for more details. |
| UnsupportedDeviceType | The job was aborted. AWS Import/Export requires a USB2 connector types. |
| UnsupportedFileFormat | The job was aborted. AWS Import/Export requires a A FAT32, ext2, ext3, or NTFS file format. |
| UnsupportedPowerSupply | The job was aborted. AWS Import/Export requires a 120 Volt 60Hz compatible power supply. |
This section describes the return codes and status messages that you might find in AWS Import/Export log files.
The following table describes AWS Import/Export status codes.
| Code | Status | Description |
|---|---|---|
| Ignored | 103 | File passed the manifest ignored filter. |
| OK | 200 | Success. |
| ReadError | 508 | Unable to read the specified file from disk. |
The following table describes Amazon S3 status codes.
| Code | Status | Description |
|---|---|---|
| AccessDenied | 403 Forbidden | Access denied |
| AccountProblem | 403 Forbidden | There is a problem with your AWS account that prevents the
operation from completing successfully. Please contact customer
service at webservices@amazon.com. |
| AllAccessDisabled | 401 Unauthorized | All access to this object has been disabled. |
| AmbiguousGrantByEmailAddress | 400 Bad Request | The e-mail address you provided is associated with more than one account. |
| BadDigest | 400 Bad Request | The Content-MD5 you specified did not match what we received. |
| BucketAlreadyExists | 409 Conflict | The requested bucket name is not available. The bucket namespace is shared by all users of the system. Please select a different name and try again. |
| BucketAlreadyOwnedByYou | 409 Conflict | Your previous request to create the named bucket succeeded and you already own it. |
| BucketNotEmpty | 409 Conflict | The bucket you tried to delete is not empty. |
| CredentialsNotSupported | 400 Bad Request | This request does not support credentials. |
| CrossLocationLoggingProhibited | 403 Forbidden | Cross location logging not allowed. Buckets in one geographic location cannot log information to a bucket in another location. |
| EntityTooSmall | 400 Bad Request | Your proposed load is smaller than the minimum allowed object size. |
| EntityTooLarge | 400 Bad Request | Your proposed load exceeds the maximum allowed object size. |
| ExpiredToken | 400 Bad Request | The provided token has expired. |
| IncompleteBody | 400 Bad Request | You did not provide the number of bytes specified by the Content-Length HTTP header. |
| IncorrectNumberOfFilesInPostRequest | 400 Bad Request | POST requires exactly one file load per request. |
| InlineDataTooLarge | 400 Bad Request | Inline data exceeds the maximum allowed size. |
| InternalError | 500 Internal Server Error | We encountered an internal error. Please try again. |
| InvalidAccess Key ID | 403 Forbidden | The AWS Access Key Id you provided does not exist in our records. |
| InvalidAddressingHeader | 400 Bad Request | You must specify the Anonymous role. |
| InvalidArgument | 400 Bad Request | Invalid Argument. |
| InvalidBucketName | 400 Bad Request | The specified bucket is not valid. |
| InvalidDigest | 400 Bad Request | The Content-MD5 you specified was an invalid. |
| InvalidLocationConstraint | 400 Bad Request | The specified location constraint is not valid. |
| InvalidPayer | 403 Forbidden | All access to this object has been disabled. |
| InvalidPolicyDocument | 400 Bad Request | The content of the form does not meet the conditions specified in the policy document. |
| InvalidRange | 416 Requested Range Not Satisfiable | The requested range cannot be satisfied. |
| InvalidSecurity | 403 Forbidden | The provided security credentials are not valid. |
| InvalidSOAPRequest | 400 Bad Request | The SOAP request body is invalid. |
| InvalidStorageClass | 400 Bad Request | The storage class you specified is not valid. |
| InvalidTargetBucketForLogging | 400 Bad Request | The target bucket for logging does not exist, is not owned by you, or does not have the appropriate grants for the log-delivery group. |
| InvalidToken | 400 Bad Request | The provided token is malformed or otherwise invalid. |
| InvalidURI | 400 Bad Request | Couldn't parse the specified URI. |
| KeyTooLong | 400 Bad Request | Your key pair is too long. |
| MalformedACLError | 400 Bad Request | The XML you provided was not well-formed or did not validate against our published schema. |
| MalformedACLError | 400 Bad Request | The XML you provided was not well-formed or did not validate against our published schema. |
| MalformedPOSTRequest | 400 Bad Request | The body of your POST request is not well-formed multipart/form-data. |
| MalformedXML | 400 Bad Request | This happens when the user sends a malformed xml (xml that doesn't conform to the published xsd) for the configuration. The error message is, "The XML you provided was not well-formed or did not validate against our published schema." |
| MaxMessageLengthExceeded | 400 Bad Request | Your request was too big. |
| MaxPostPreDataLengthExceededError | 400 Bad Request | Your POST request fields preceding the load file were too large. |
| MetadataTooLarge | 400 Bad Request | Your metadata headers exceed the maximum allowed metadata size. |
| MethodNotAllowed | 405 Method Not Allowed | The specified method is not allowed against this resource. |
| MissingAttachment | 400 Bad Request | A SOAP attachment was expected, but none were found. |
| MissingContentLength | 411 Length Required | You must provide the Content-Length HTTP header. |
| MissingRequestBodyError | 400 Bad Request | This happens when the user sends an empty xml document as a request. The error message is, "Request body is empty." |
| MissingSecurityElement | 400 Bad Request | The SOAP 1.1 request is missing a security element. |
| MissingSecurityHeader | 400 Bad Request | Your request was missing a required header. |
| NoLoggingStatusForKey | 400 Bad Request | There is no such thing as a logging status for a key pair. |
| NoSuchBucket | 404 Not Found | The specified bucket does not exist. |
| NoSuchKey | 404 Not Found | The specified key does not exist. |
| NotImplemented | 501 Not Implemented | A header you provided implies functionality that is not implemented. |
| NotSignedUp | 403 Forbidden | Your account is not signed up for the Amazon S3 service. You must sign up before you can use Amazon S3. |
| OperationAborted | 409 Conflict | A conflicting conditional operation is currently in progress against this resource. Please try again. |
| PermanentRedirect | 301 Moved Permanently | The bucket you are attempting to access must be addressed using the specified endpoint. Please send all future requests to this endpoint. |
| PreconditionFailed | 412 Precondition Failed | At least one of the preconditions you specified did not hold. |
| Redirect | 307 Moved Temporarily | Temporary redirect. |
| RequestIsNotMultiPartContent | 400 Bad Request | Bucket POST must be of the enclosure-type multipart/form-data. |
| RequestTimeout | 400 Bad Request | Your socket connection to the server was not read from or written to within the timeout period. |
| RequestTimeTooSkewed | 403 Forbidden | The difference between the request time and the server's time is too large. |
| RequestTorrentOfBucketError | 400 Bad Request | Requesting the torrent file of a bucket is not permitted. |
| SignatureDoesNotMatch | 403 Forbidden | The request signature we calculated does not match the signature you provided. Check your Secret Access Key and signing method. |
| SlowDown | 503 Service Unavailable | Please reduce your request rate. |
| TemporaryRedirect | 307 Moved Temporarily | You are being redirected to the bucket while DNS updates. |
| TokenRefreshRequired | 400 Bad Request | The provided token must be refreshed. |
| TooManyBuckets | 400 Bad Request | You have attempted to create more buckets than allowed. |
| UnexpectedContent | 400 Bad Request | This request does not support content. |
| UnresolvableGrantByEmailAddress | 400 Bad Request | The e-mail address you provided does not match any account on record. |
| UserKeyMustBeSpecified | 400 Bad Request | The bucket POST must contain the specified field name. If it is specified, please check the order of the fields. |
