         | Did this page help you? Yes No Tell us about it... |
Errors
The following table lists the errors that all CloudFront actions return. Errors specific to a particular action are listed in the topic for that action. For information about the format of error responses, go to REST Responses in the Amazon CloudFront Developer Guide.
| Error | Description | HTTP Status Code |
|---|---|---|
|
|
Access denied. |
403 |
|
|
The XML document you provided was well-formed and valid, but not appropriate for this operation. |
400 |
|
|
We encountered an internal error. Please try again. |
500 |
|
|
The action specified is not valid. |
400 |
|
|
<Parameter name and problem> |
400 |
|
|
The AWS Access Key ID you provided does not exist in our records. |
403 |
|
|
The HTTP authorization header is bad, use format: |
400 |
|
|
There was an error in the body of your HTTP request. |
400 |
|
|
Could not parse the specified URI. |
400 |
|
|
The XML you provided was not well-formed or did not validate against our published schema. |
400 |
|
|
Request must contain AWSAccessKeyId. |
403 |
|
|
Authorized request must have a "date" or "x-amz-date" header. |
400 |
|
|
The API version specified does not exist. |
404 |
|
|
Not implemented. |
501 |
|
|
The AWS Access Key ID needs a subscription for the service. |
403 |
|
|
Request has expired. Timestamp date is <the value of the Date or x-amz-date header you submitted in the request>. |
400 |
|
|
The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details. |
403 |
