S3 RESTエラーレスポンス

RESTエラーレスポンス

エラーが発生した場合、ヘッダ情報は、以下のものが含まれています。

  • コンテンツタイプ:アプリケーション/ xmlの

  • 適切な3XX、4XX、または5xxのHTTPステータスコード

ボディまたは応答は、エラーに関する情報が含まれています。次のサンプルエラー応答は、すべてのRESTのエラー応答に共通の応答エレメントの構造を示します。

 

エラーコード 説明 HTTPステータスコード SOAPフォルトコードプレフィックス
AccessDenied アクセスが拒否されました 403 Forbidden クライアント
AccountProblem 正常に完了操作を防止AWSアカウントに問題があります。参照、さらに支援のためにAWSサポートに連絡してください  お問い合わせ 403 Forbidden クライアント
AllAccessDisabled このAmazon S3のリソースへのアクセスはすべて無効になっています。参照、さらに支援のためにAWSサポートに連絡してください  お問い合わせ 403 Forbidden クライアント

AmbiguousGrantByEmailAddress

あなたが提供したメールアドレスは、複数のアカウントに関連付けられています。 400 Bad Request クライアント

AuthorizationHeaderMalformed

あなたが提供する認証ヘッダーが無効です。 400 Bad Request N / A
BadDigest 指定のContent-MD5は、私たちが受け取ったものと一致しませんでした。 400 Bad Request クライアント
BucketAlreadyExists 要求されたバケット名は使用できません。バケットの名前空間は、システムのすべてのユーザーによって共有されています。別の名前を選択して、もう一度お試しください。 409 Conflict クライアント
BucketAlreadyOwnedByYou あなたが作成しようとしたバケットは既に存在している、とあなたはそれを所有しています。Amazon S3は、私たち東-1(N.バージニア州)を除くすべてのAWSの地域でこのエラーを返します。レガシー互換性のために、あなたがあれば、あなたはすでに私たち-東-1で所有して既存のバケットを再作成し、Amazon S3の戻り  200 OK とバケットのアクセス制御リスト(ACL)をリセットします。

409 Conflict(除くすべての地域で私たち-東-1)

クライアント
BucketNotEmpty 削除しようとしたバケットは空ではありません。 409 Conflict クライアント
CredentialsNotSupported この要求は、資格証明書をサポートしていません。 400 Bad Request クライアント
CrossLocationLoggingProhibited Cross-location logging not allowed. Buckets in one geographic location cannot log information to a bucket in another location. 403 Forbidden Client
EntityTooSmall Your proposed upload is smaller than the minimum allowed object size. 400 Bad Request Client
EntityTooLarge Your proposed upload exceeds the maximum allowed object size. 400 Bad Request Client
ExpiredToken The provided token has expired. 400 Bad Request Client
IllegalVersioningConfigurationException Indicates that the versioning configuration specified in the request is invalid. 400 Bad Request Client
IncompleteBody You did not provide the number of bytes specified by the Content-Length HTTP header 400 Bad Request Client
IncorrectNumberOfFilesInPostRequest POST requires exactly one file upload per request. 400 Bad Request Client
InlineDataTooLarge Inline data exceeds the maximum allowed size. 400 Bad Request Client
InternalError We encountered an internal error. Please try again. 500 Internal Server Error Server
InvalidAccessKeyId The AWS access key ID you provided does not exist in our records. 403 Forbidden Client
InvalidAddressingHeader You must specify the Anonymous role. N/A Client
InvalidArgument Invalid Argument 400 Bad Request Client
InvalidBucketName The specified bucket is not valid. 400 Bad Request Client
InvalidBucketState The request is not valid with the current state of the bucket. 409 Conflict Client
InvalidDigest The Content-MD5 you specified is not valid. 400 Bad Request Client
InvalidEncryptionAlgorithmError The encryption request you specified is not valid. The valid value is AES256. 400 Bad Request Client
InvalidLocationConstraint The specified location constraint is not valid. For more information about Regions, see How to Select a Region for Your Buckets. 400 Bad Request Client
InvalidObjectState The operation is not valid for the current state of the object. 403 Forbidden Client
InvalidPart One or more of the specified parts could not be found. The part might not have been uploaded, or the specified entity tag might not have matched the part's entity tag. 400 Bad Request Client
InvalidPartOrder The list of parts was not in ascending order. Parts list must be specified in order by part number. 400 Bad Request Client
InvalidPayer All access to this object has been disabled. Please contact AWS Support for further assistance, see Contact Us. 403 Forbidden Client
InvalidPolicyDocument The content of the form does not meet the conditions specified in the policy document. 400 Bad Request Client
InvalidRange The requested range cannot be satisfied. 416 Requested Range Not Satisfiable Client
InvalidRequest Please use AWS4-HMAC-SHA256. 400 Bad Request N/A
InvalidRequest SOAP requests must be made over an HTTPS connection. 400 Bad Request Client
InvalidRequest Amazon S3 Transfer Acceleration is not supported for buckets with non-DNS compliant names. 400 Bad Request N/A
InvalidRequest Amazon S3 Transfer Acceleration is not supported for buckets with periods (.) in their names. 400 Bad Request N/A
InvalidRequest Amazon S3 Transfer Accelerate endpoint only supports virtual style requests. 400 Bad Request N/A
InvalidRequest Amazon S3 Transfer Accelerate is not configured on this bucket. 400 Bad Request N/A
InvalidRequest Amazon S3 Transfer Accelerate is disabled on this bucket. 400 Bad Request N/A
InvalidRequest Amazon S3 Transfer Acceleration is not supported on this bucket. Contact AWS Support for more information. 400 Bad Request N/A
InvalidRequest Amazon S3 Transfer Acceleration cannot be enabled on this bucket. Contact AWS Support for more information. 400 Bad Request N/A
InvalidSecurity The provided security credentials are not valid. 403 Forbidden Client
InvalidSOAPRequest The SOAP request body is invalid. 400 Bad Request Client
InvalidStorageClass The storage class you specified is not valid. 400 Bad Request Client
InvalidTargetBucketForLogging 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. 400 Bad Request Client
InvalidToken The provided token is malformed or otherwise invalid. 400 Bad Request Client
InvalidURI Couldn't parse the specified URI. 400 Bad Request Client
KeyTooLongError Your key is too long. 400 Bad Request Client
MalformedACLError The XML you provided was not well-formed or did not validate against our published schema. 400 Bad Request Client
MalformedPOSTRequest The body of your POST request is not well-formed multipart/form-data. 400 Bad Request Client
MalformedXML This happens when the user sends 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." 400 Bad Request Client
MaxMessageLengthExceeded Your request was too big. 400 Bad Request Client
MaxPostPreDataLengthExceededError Your POST request fields preceding the upload file were too large. 400 Bad Request Client
MetadataTooLarge Your metadata headers exceed the maximum allowed metadata size. 400 Bad Request Client
MethodNotAllowed The specified method is not allowed against this resource. 405 Method Not Allowed Client
MissingAttachment A SOAP attachment was expected, but none were found. N/A Client
MissingContentLength You must provide the Content-Length HTTP header. 411 Length Required Client
MissingRequestBodyError This happens when the user sends an empty XML document as a request. The error message is, "Request body is empty." 400 Bad Request Client
MissingSecurityElement The SOAP 1.1 request is missing a security element. 400 Bad Request Client
MissingSecurityHeader Your request is missing a required header. 400 Bad Request Client
NoLoggingStatusForKey There is no such thing as a logging status subresource for a key. 400 Bad Request Client
NoSuchBucket The specified bucket does not exist. 404 Not Found Client
NoSuchBucketPolicy The specified bucket does not have a bucket policy. 404 Not Found Client
NoSuchKey The specified key does not exist. 404 Not Found Client
NoSuchLifecycleConfiguration The lifecycle configuration does not exist. 404 Not Found Client
NoSuchUpload The specified multipart upload does not exist. The upload ID might be invalid, or the multipart upload might have been aborted or completed. 404 Not Found Client
NoSuchVersion Indicates that the version ID specified in the request does not match an existing version. 404 Not Found Client
NotImplemented A header you provided implies functionality that is not implemented. 501 Not Implemented Server
NotSignedUp Your account is not signed up for the Amazon S3 service. You must sign up before you can use Amazon S3. You can sign up at the following URL: https://aws.amazon.com/s3 403 Forbidden Client
OperationAborted A conflicting conditional operation is currently in progress against this resource. Try again. 409 Conflict Client
PermanentRedirect The bucket you are attempting to access must be addressed using the specified endpoint. Send all future requests to this endpoint. 301 Moved Permanently Client
PreconditionFailed At least one of the preconditions you specified did not hold. 412 Precondition Failed Client
Redirect Temporary redirect. 307 Moved Temporarily Client
RestoreAlreadyInProgress Object restore is already in progress. 409 Conflict Client
RequestIsNotMultiPartContent Bucket POST must be of the enclosure-type multipart/form-data. 400 Bad Request Client
RequestTimeout Your socket connection to the server was not read from or written to within the timeout period. 400 Bad Request Client
RequestTimeTooSkewed The difference between the request time and the server's time is too large. 403 Forbidden Client
RequestTorrentOfBucketError Requesting the torrent file of a bucket is not permitted. 400 Bad Request Client
ServerSideEncryptionConfigurationNotFoundError The server side encryption configuration was not found. 400 Bad Request Client
ServiceUnavailable Reduce your request rate. 503 Service Unavailable Server
SignatureDoesNotMatch The request signature we calculated does not match the signature you provided. Check your AWS secret access key and signing method. For more information, see REST Authentication and SOAP Authentication for details. 403 Forbidden Client
SlowDown Reduce your request rate. 503 Slow Down Server
TemporaryRedirect You are being redirected to the bucket while DNS updates. 307 Moved Temporarily Client
TokenRefreshRequired The provided token must be refreshed. 400 Bad Request Client
TooManyBuckets You have attempted to create more buckets than allowed. 400 Bad Request Client
UnexpectedContent This request does not support content. 400 Bad Request Client
UnresolvableGrantByEmailAddress The email address you provided does not match any account on record. 400 Bad Request Client
UserKeyMustBeSpecified The bucket POST must contain the specified field name. If it is specified, check the order of the fields. 400 Bad Request Client

おすすめ

転載: www.cnblogs.com/cloudrivers/p/11422653.html