AWS AmazonS3: Remove SOAP fault code column and SOAP notes from S3 error tables
Summary
Drops the 'SOAP fault code prefix' column from all S3 error-code tables (general, SELECT Object Content, Replication, Tagging, Annotations, Outposts, Storage Lens, Storage Lens groups) and removes SOAP-related rows/notes, including the SOAP deprecation note, the 'SOAP requests must be made over an HTTPS connection' bullet, and SOAP-only error codes such as InvalidSOAPRequest and MissingSecurityElement. No error descriptions or HTTP status codes were otherwise changed.
Security assessment
The diff is a structural cleanup that deletes the SOAP fault code prefix column and SOAP-specific content from the error reference. The only security-adjacent lines removed are the SOAP deprecation note and the 'SOAP requests must be made over an HTTPS connection' bullet, but these are removed as part of retiring SOAP documentation rather than to address a vulnerability, and no new security guidance is added. No CVE, credential, encryption, or authorization content is introduced or corrected.
Evidence
-Error code | Description | HTTP status code | SOAP fault code prefix
Diff
diff --git a/AmazonS3/latest/developerguide/ErrorResponses.md b/AmazonS3/latest/developerguide/ErrorResponses.md index d65c335..a89b3e5 100644 --- a//AmazonS3/latest/developerguide/ErrorResponses.md +++ b//AmazonS3/latest/developerguide/ErrorResponses.md @@ -17,2 +16,0 @@ This section provides reference information about Amazon S3 errors. - * SOAP support over HTTP is deprecated, but SOAP is still available over HTTPS. New Amazon S3 features are not supported for SOAP. Instead of using SOAP, we recommend that you use either the REST API or the AWS SDKs. - @@ -95,26 +93,26 @@ The following table lists Amazon S3 error codes. -Error code | Description | HTTP status code | SOAP fault code prefix ----|---|---|--- -`AccessControlListNotSupported` | The bucket does not allow ACLs. | `400 Bad Request` | Client -`AccessDenied` | Access Denied | `403 Forbidden` | Client -`AccessPointAlreadyOwnedByYou` | An access point with an identical name already exists in your account. | `409 Conflict` | Client -`AccountProblem` | There is a problem with your AWS account that prevents the operation from completing successfully. For further assistance, see [Contact Us](https://aws.amazon.com/contact-us/). | `403 Forbidden` | Client -`AllAccessDisabled` | All access to this Amazon S3 resource has been disabled. For further assistance, see [Contact Us](https://aws.amazon.com/contact-us/). | `403 Forbidden` | Client -`AmbiguousGrantByEmailAddress` | The email address that you provided is associated with more than one account. | `400 Bad Request` | Client -`AuthorizationHeaderMalformed` | The authorization header that you provided is not valid. | `400 Bad Request` | N/A -`AuthorizationQueryParametersError` | The authorization query parameters that you provided are not valid. | `400 Bad Request` | N/A -`BadDigest` | The Content-MD5 or checksum value that you specified did not match what the server received. | `400 Bad Request` | Client -`BucketAlreadyExists` | The requested bucket name is not available. The bucket namespace is shared by all users of the system. Specify a different name and try again. | `409 Conflict` | Client -`BucketAlreadyOwnedByYou` | The bucket that you tried to create already exists, and you own it. Amazon S3 returns this error in all AWS Regions except in the US East (N. Virginia) Region (us-east-1). For legacy compatibility, if you re-create an existing bucket that you already own in us-east-1, Amazon S3 returns `200 OK` and resets the bucket access control lists (ACLs). For Amazon S3 on Outposts, the bucket that you tried to create already exists in your Outpost and you own it. | `409 Conflict` (in all Regions except us-east-1) | Client -`BucketHasAccessPointsAttached` | The bucket you tried to delete has access points attached. Delete your access points before deleting your bucket. | `400 Bad Request` | Client -`BucketNotEmpty` | The bucket that you tried to delete is not empty. | `409 Conflict` | Client -`ClientTokenConflict` | Your Multi-Region Access Point idempotency token was already used for a different request. | `409 Conflict` | Client -`ConnectionClosedByRequester` | Returned to the original caller when an error is encountered while reading the WriteGetObjectResponse body. | `400 Bad Request` | Client -`ConditionalRequestConflict` | A conflicting operation occurred. If using `PutObject` you can retry the request. If using multipart upload you should initiate another `CreateMultipartUpload` request and re-upload each part. | `409 Conflict` | Client -`CredentialsNotSupported` | This request does not support credentials. | `400 Bad Request` | Client -`CrossLocationLoggingProhibited` | Cross-Region logging is not allowed. Buckets in one AWS Region cannot log information to a bucket in another Region. | `403 Forbidden` | Client -`DeviceNotActiveError` | The device is not currently active. | `400 Bad Request` | Client -`EndpointNotFound` | Direct requests to the correct endpoint. | `400 Bad Request` | 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. For more information, see [Amazon Simple Storage Service endpoints and quotas](https://docs.aws.amazon.com/general/latest/gr/s3.html) in the _AWS General Reference_. | `400 Bad Request` | Client -Your proposed download exceeds the maximum allowed size. | `405 Method Not Allowed` | Client -`ExpiredToken` | The provided token has expired. | `400 Bad Request` | Client +Error code | Description | HTTP status code +---|---|--- +`AccessControlListNotSupported` | The bucket does not allow ACLs. | `400 Bad Request` +`AccessDenied` | Access Denied | `403 Forbidden` +`AccessPointAlreadyOwnedByYou` | An access point with an identical name already exists in your account. | `409 Conflict` +`AccountProblem` | There is a problem with your AWS account that prevents the operation from completing successfully. For further assistance, see [Contact Us](https://aws.amazon.com/contact-us/). | `403 Forbidden` +`AllAccessDisabled` | All access to this Amazon S3 resource has been disabled. For further assistance, see [Contact Us](https://aws.amazon.com/contact-us/). | `403 Forbidden` +`AmbiguousGrantByEmailAddress` | The email address that you provided is associated with more than one account. | `400 Bad Request` +`AuthorizationHeaderMalformed` | The authorization header that you provided is not valid. | `400 Bad Request` +`AuthorizationQueryParametersError` | The authorization query parameters that you provided are not valid. | `400 Bad Request` +`BadDigest` | The Content-MD5 or checksum value that you specified did not match what the server received. | `400 Bad Request` +`BucketAlreadyExists` | The requested bucket name is not available. The bucket namespace is shared by all users of the system. Specify a different name and try again. | `409 Conflict` +`BucketAlreadyOwnedByYou` | The bucket that you tried to create already exists, and you own it. Amazon S3 returns this error in all AWS Regions except in the US East (N. Virginia) Region (us-east-1). For legacy compatibility, if you re-create an existing bucket that you already own in us-east-1, Amazon S3 returns `200 OK` and resets the bucket access control lists (ACLs). For Amazon S3 on Outposts, the bucket that you tried to create already exists in your Outpost and you own it. | `409 Conflict` (in all Regions except us-east-1) +`BucketHasAccessPointsAttached` | The bucket you tried to delete has access points attached. Delete your access points before deleting your bucket. | `400 Bad Request` +`BucketNotEmpty` | The bucket that you tried to delete is not empty. | `409 Conflict` +`ClientTokenConflict` | Your Multi-Region Access Point idempotency token was already used for a different request. | `409 Conflict` +`ConnectionClosedByRequester` | Returned to the original caller when an error is encountered while reading the WriteGetObjectResponse body. | `400 Bad Request` +`ConditionalRequestConflict` | A conflicting operation occurred. If using `PutObject` you can retry the request. If using multipart upload you should initiate another `CreateMultipartUpload` request and re-upload each part. | `409 Conflict` +`CredentialsNotSupported` | This request does not support credentials. | `400 Bad Request` +`CrossLocationLoggingProhibited` | Cross-Region logging is not allowed. Buckets in one AWS Region cannot log information to a bucket in another Region. | `403 Forbidden` +`DeviceNotActiveError` | The device is not currently active. | `400 Bad Request` +`EndpointNotFound` | Direct requests to the correct endpoint. | `400 Bad Request` +`EntityTooSmall` | Your proposed upload is smaller than the minimum allowed object size. | `400 Bad Request` +`EntityTooLarge` | Your proposed upload exceeds the maximum allowed object size. For more information, see [Amazon Simple Storage Service endpoints and quotas](https://docs.aws.amazon.com/general/latest/gr/s3.html) in the _AWS General Reference_. | `400 Bad Request` +Your proposed download exceeds the maximum allowed size. | `405 Method Not Allowed` +`ExpiredToken` | The provided token has expired. | `400 Bad Request` @@ -126,11 +124,11 @@ Your proposed download exceeds the maximum allowed size. | `405 Method Not Allo -| `400 Bad Request` | Client -`IllegalVersioningConfigurationException` | The versioning configuration specified in the request is not valid. | `400 Bad Request` | Client -`IncompleteBody` | You did not provide the number of bytes specified by the Content-Length HTTP header. | `400 Bad Request` | Client -`IncorrectEndpoint` | The specified bucket exists in another Region. Direct requests to the correct endpoint. | `400 Bad Request` | Client -`IncorrectNumberOfFilesInPostRequest` | POST requires exactly one file upload per request. | `400 Bad Request` | Client -`InlineDataTooLarge` | The inline data exceeds the maximum allowed size. | `400 Bad Request` | Client -`InternalError` | An internal error occurred. Try again. | `500 Internal Server Error` | Server -`InvalidAccessKeyId` | The AWS access key ID that you provided does not exist in our records. | `403 Forbidden` | Client -`InvalidAccessPoint` | The specified access point name or account is not valid. | `400 Bad Request` | Client -`InvalidAccessPointAliasError` | The specified access point alias name is not valid. | `400 Bad Request` | Client -`InvalidAddressingHeader` | You must specify the Anonymous role. | N/A | Client +| `400 Bad Request` +`IllegalVersioningConfigurationException` | The versioning configuration specified in the request is not valid. | `400 Bad Request` +`IncompleteBody` | You did not provide the number of bytes specified by the Content-Length HTTP header. | `400 Bad Request` +`IncorrectEndpoint` | The specified bucket exists in another Region. Direct requests to the correct endpoint. | `400 Bad Request` +`IncorrectNumberOfFilesInPostRequest` | POST requires exactly one file upload per request. | `400 Bad Request` +`InlineDataTooLarge` | The inline data exceeds the maximum allowed size. | `400 Bad Request` +`InternalError` | An internal error occurred. Try again. | `500 Internal Server Error` +`InvalidAccessKeyId` | The AWS access key ID that you provided does not exist in our records. | `403 Forbidden` +`InvalidAccessPoint` | The specified access point name or account is not valid. | `400 Bad Request` +`InvalidAccessPointAliasError` | The specified access point alias name is not valid. | `400 Bad Request` +`InvalidAddressingHeader` | You must specify the Anonymous role. | N/A @@ -145,17 +143,17 @@ Your proposed download exceeds the maximum allowed size. | `405 Method Not Allo -| `400 Bad Request` | Client -`InvalidBucketAclWithObjectOwnership` | Bucket cannot have ACLs set with ObjectOwnership's BucketOwnerEnforced setting. | `400 Bad Request` | Client -`InvalidBucketName` | The specified bucket is not valid. | `400 Bad Request` | Client -`InvalidBucketOwnerAWSAccountID` | The value of the expected bucket owner parameter must be an AWS account ID. | `400 Bad Request` | Client -`InvalidBucketState` | The request is not valid for the current state of the bucket. | `409 Conflict` | Client -`InvalidDigest` | The Content-MD5 or checksum value that you specified is not valid. | `400 Bad Request` | Client -`InvalidEncryptionAlgorithmError` | The encryption request that you specified is not valid. The valid value is `AES256`. | `400 Bad Request` | Client -`InvalidHostHeader` | The host headers provided in the request used the incorrect style addressing. | `400 Bad Request` | Client -`InvalidHttpMethod` | The request is made using an unexpected HTTP method. | `400 Bad Request` | Client -`InvalidLocationConstraint` | The specified location (Region) constraint is not valid. For more information about selecting a Region for your buckets, see [Buckets overview](https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingBucket.html#access-bucket-intro). | `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. The parts list must be specified in order by part number. | `400 Bad Request` | Client -`InvalidPayer` | All access to this object has been disabled. For further assistance, see [Contact Us](https://aws.amazon.com/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 -InvalidRegion | You've attempted to create a Multi-Region Access Point in a Region that you haven't opted in to. | 403 Forbidden | Client +| `400 Bad Request` +`InvalidBucketAclWithObjectOwnership` | Bucket cannot have ACLs set with ObjectOwnership's BucketOwnerEnforced setting. | `400 Bad Request` +`InvalidBucketName` | The specified bucket is not valid. | `400 Bad Request` +`InvalidBucketOwnerAWSAccountID` | The value of the expected bucket owner parameter must be an AWS account ID. | `400 Bad Request` +`InvalidBucketState` | The request is not valid for the current state of the bucket. | `409 Conflict` +`InvalidDigest` | The Content-MD5 or checksum value that you specified is not valid. | `400 Bad Request` +`InvalidEncryptionAlgorithmError` | The encryption request that you specified is not valid. The valid value is `AES256`. | `400 Bad Request` +`InvalidHostHeader` | The host headers provided in the request used the incorrect style addressing. | `400 Bad Request` +`InvalidHttpMethod` | The request is made using an unexpected HTTP method. | `400 Bad Request` +`InvalidLocationConstraint` | The specified location (Region) constraint is not valid. For more information about selecting a Region for your buckets, see [Buckets overview](https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingBucket.html#access-bucket-intro). | `400 Bad Request` +`InvalidObjectState` | The operation is not valid for the current state of the object. | `403 Forbidden` +`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` +`InvalidPartOrder` | The list of parts was not in ascending order. The parts list must be specified in order by part number. | `400 Bad Request` +`InvalidPayer` | All access to this object has been disabled. For further assistance, see [Contact Us](https://aws.amazon.com/contact-us/). | `403 Forbidden` +`InvalidPolicyDocument` | The content of the form does not meet the conditions specified in the policy document. | `400 Bad Request` +InvalidRange | The requested range cannot be satisfied. | 416 Requested Range Not Satisfiable +InvalidRegion | You've attempted to create a Multi-Region Access Point in a Region that you haven't opted in to. | 403 Forbidden @@ -174 +171,0 @@ InvalidRegion | You've attempted to create a Multi-Region Access Point in a Regi - * SOAP requests must be made over an HTTPS connection. @@ -186,11 +183,10 @@ InvalidRegion | You've attempted to create a Multi-Region Access Point in a Regi -| `400 Bad Request` | Client -`InvalidSessionException` | Returned if the session doesn't exist anymore because it timed out or expired. | `400 Bad Request` | Client -`InvalidSignature` | The request signature that the server calculated does not match the signature that you provided. Check your AWS secret access key and signing method. For more information, see [Signing and authenticating REST requests](https://docs.aws.amazon.com/AmazonS3/latest/userguide/RESTAuthentication.html). | `400 Bad Request` | Client -`InvalidSecurity` | The provided security credentials are not valid. | `403 Forbidden` | Client -`InvalidSOAPRequest` | The SOAP request body is not valid. | `400 Bad Request` | Client -`InvalidStorageClass` | The storage class that you specified is not valid. | `400 Bad Request` | Client -`InvalidTargetBucketForLogging` | The target bucket for logging either 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 not valid. | `400 Bad Request` | Client -`InvalidURI` | The specified URI couldn't be parsed. | `400 Bad Request` | Client -`KeyTooLongError` | Your key is too long. | `400 Bad Request` | Client -`KMS.DisabledException` | The request was rejected because the specified KMS key is not enabled. | `400 Bad Request` | Client +| `400 Bad Request` +`InvalidSessionException` | Returned if the session doesn't exist anymore because it timed out or expired. | `400 Bad Request` +`InvalidSignature` | The request signature that the server calculated does not match the signature that you provided. Check your AWS secret access key and signing method. For more information, see [Signing and authenticating REST requests](https://docs.aws.amazon.com/AmazonS3/latest/userguide/RESTAuthentication.html). | `400 Bad Request` +`InvalidSecurity` | The provided security credentials are not valid. | `403 Forbidden` +`InvalidStorageClass` | The storage class that you specified is not valid. | `400 Bad Request` +`InvalidTargetBucketForLogging` | The target bucket for logging either does not exist, is not owned by you, or does not have the appropriate grants for the log-delivery group. | `400 Bad Request` +`InvalidToken` | The provided token is malformed or otherwise not valid. | `400 Bad Request` +`InvalidURI` | The specified URI couldn't be parsed. | `400 Bad Request` +`KeyTooLongError` | Your key is too long. | `400 Bad Request` +`KMS.DisabledException` | The request was rejected because the specified KMS key is not enabled. | `400 Bad Request` @@ -202 +198 @@ InvalidRegion | You've attempted to create a Multi-Region Access Point in a Regi -For encrypting, decrypting, re-encrypting, and generating data keys, the KeyUsage must be ENCRYPT_DECRYPT. For signing and verifying messages, the KeyUsage must be SIGN_VERIFY. For generating and verifying message authentication codes (MACs), the KeyUsage must be GENERATE_VERIFY_MAC. For deriving key agreement secrets, the KeyUsage must be KEY_AGREEMENT. To find the KeyUsage of a KMS key, use the DescribeKey operation. To find the encryption or signing algorithms supported for a particular KMS key, use the DescribeKey operation. | `400 Bad Request` | Client +For encrypting, decrypting, re-encrypting, and generating data keys, the KeyUsage must be ENCRYPT_DECRYPT. For signing and verifying messages, the KeyUsage must be SIGN_VERIFY. For generating and verifying message authentication codes (MACs), the KeyUsage must be GENERATE_VERIFY_MAC. For deriving key agreement secrets, the KeyUsage must be KEY_AGREEMENT. To find the KeyUsage of a KMS key, use the DescribeKey operation. To find the encryption or signing algorithms supported for a particular KMS key, use the DescribeKey operation. | `400 Bad Request` @@ -208,70 +204,68 @@ For encrypting, decrypting, re-encrypting, and generating data keys, the KeyUsag -| `400 Bad Request` | Client -`KMS.NotFoundException` | The request was rejected because the specified entity or resource could not be found. | `400 Bad Request` | Client -`MalformedACLError` | The ACL that 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` | The XML that you provided was not well formed or did not validate against our published schema. | `400 Bad Request` | Client -`MaxMessageLengthExceeded` | Your request was too large. | `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 was found. | 400 Bad Request | Client -`MissingAuthenticationToken` | The request was not signed. | 403 Forbidden | Client -`MissingContentLength` | You must provide the Content-Length HTTP header. | `411 Length Required` | Client -`MissingRequestBodyError` | You sent an empty XML document as a request. | `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 -`NoSuchAsyncRequest` | The specified request was not found. | `404 Not Found` | 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 -`NoSuchCORSConfiguration` | The specified bucket does not have a CORS configuration. | `404 Not Found` | Client -`NoSuchKey` | The specified key does not exist. | `404 Not Found` | Client -`NoSuchLifecycleConfiguration` | The specified lifecycle configuration does not exist. | `404 Not Found` | Client -`NoSuchMultiRegionAccessPoint` | The specified Multi-Region Access Point does not exist. | `404 Not Found` | Client -`NoSuchObjectLockConfiguration` | The specified object does not have an ObjectLock configuration. | `404 Not Found` | Client -`NoSuchWebsiteConfiguration` | The specified bucket does not have a website configuration. | `404 Not Found` | Client -`NoSuchTagSet` | The specified tag does not exist. | `404 Not Found` | Client -`NoSuchUpload` | The specified multipart upload does not exist. The upload ID might not be valid, or the multipart upload might have been aborted or completed. | `404 Not Found` | Client -`NoSuchVersion` | The version ID specified in the request does not match an existing version. | `404 Not Found` | Client -`NotDeviceOwnerError` | The device that generated the token is not owned by the authenticated user. | `400 Bad Request` | Client -`NotImplemented` | A header that you provided implies functionality that is not implemented. | `501 Not Implemented` | Server -`NotModified` | The resource was not changed. | `304 Not Modified` | Server -`NoTransformationDefined` | No transformation found for this Object Lambda Access Point. | `404 Not Found` | Client -`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](https://aws.amazon.com/s3/) | `403 Forbidden` | Client -`ObjectLockConfigurationNotFoundError` | The Object Lock configuration does not exist for this bucket. | `404 Not Found` | Client -`OwnershipControlsNotFoundError` | The bucket ownership controls were not found. | `404 Not Found` | Client -`OperationAborted` | A conflicting conditional operation is currently in progress against this resource. Try again. | `409 Conflict` | Client -`PermanentRedirect` | The bucket that you are attempting to access must be addressed using the specified endpoint. Send all future requests to this endpoint. | `301 Moved Permanently` | Client -`PermanentRedirectControlError` | The API operation 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 that you specified did not hold. | `412 Precondition Failed` | Client -`Redirect` | Temporary redirect. You are being redirected to the bucket while the Domain Name System (DNS) server is being updated. | `307 Temporary Redirect` | Client -`RequestHeaderSectionTooLarge` | The request header and query parameters used to make the request exceed the maximum allowed size. | `400 Bad Request` | Client -`RequestIsNotMultiPartContent` | A bucket POST request must be of the enclosure-type multipart/form-data. | `412 Precondition Failed` | 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 -`ResponseInterrupted` | Returned to the original caller when an error is encountered while reading the WriteGetObjectResponse body. | `400 Bad Request` | Client -`RestoreAlreadyInProgress` | The object restore is already in progress. | `409 Conflict` | Client -`ServerSideEncryptionConfigurationNotFoundError` | The server-side encryption configuration was not found. | `400 Bad Request` | Client -`ServiceUnavailable` | Service is unable to handle request. | `503 Service Unavailable` | Server -`SignatureDoesNotMatch` | The request signature that the server calculated does not match the signature that you provided. Check your AWS secret access key and signing method. For more information, see [REST Authentication](https://docs.aws.amazon.com/AmazonS3/latest/userguide/RESTAuthentication.html) and [SOAP Authentication](https://docs.aws.amazon.com/AmazonS3/latest/userguide/SOAPAuthentication.html). | `403 Forbidden` | Client -`SlowDown` | Please reduce your request rate. | `503 Slow Down` | Server -`503 SlowDown` | Slow Down | `503 Slow Down` | Server -`TagPolicyException` | The tag policy does not allow the specified value for the following tag key. | `400 Bad Request` | Client -`TemporaryRedirect` | You are being redirected to the bucket while the Domain Name System (DNS) server is being updated. | `307 Temporary Redirect` | Client