Hello, when trying to convert pdf to docx ( Aspose.Pdf Cloud - API References ) , I get this error. {
“RequestId”: “997b419d11948b41565ef737ac020b7d”,
“Error”: {
“Code”: “error”,
“Message”: “AmazonS3 Storage exception: Invalid region endpoint provided”,
“Description”: “Operation Failed. General Error.”,
“DateTime”: “2025-07-14T13:39:19.0690725Z”,
“InnerError”: null
}
}
Can you help, it seems like it wasn’t necessary to specify the region of the s3 bucket before, if it is necessary now, where should I do it?
Hi, @MykytaNos
What type of storage are you using? Please provide sample code to reproduce the issue.
We use Aws S3.
No code just api call via Aspose Swagger
curl -X GET "https://api.aspose.cloud/v3.0/pdf/<FILE_NAME>/convert/doc?format=DocX&folder=< FOLDER > &storage= < STORAGE > " -H “accept: multipart/form-data” -H "authorization: < TOKEN > " -H “x-aspose-client: Containerize.Swagger”
https://reference.aspose.cloud/pdf/#/Convert/GetPdfInStorageToDoc
image.png (63.0 KB)
@MykytaNos
It looks like your storage settings are incorrect. Please enter the correct bucket name, Amazon key and secret.
We double-check everything, the data is entered correctly, the user is given access, the bucket region is standard “us-east-1”. Also, there is access to the storage through Aspose Dashboard in Files ( Dashboard ), we can manipulate the bucket in aspose dashboard , but the convert API ( Aspose.Pdf Cloud - API References ) still returns this error: {
“RequestId”: “4daf7315cb8db7ce42f3842896a98c3f”,
“Error”: {
“Code”: “error”,
“Message”: “AmazonS3 Storage exception: Invalid region endpoint provided”,
“Description”: “Operation Failed. General Error.”,
“DateTime”: “2025-07-15T10:46:28.3844471Z”,
“InnerError”: null
}
}
we checked on a bucket with another region (‘eu-north-1’) and everything works fine, but on the region ‘us-east-1’ it still gives an error. The region ‘us-east-1’ is special in AWS, for example s3:GetBucketLocation returns “{ “LocationConstraint”: null }” on this region. Can you please tell me if there is any update on this problem
@MykytaNos
Thank you for feedback, we are currently investigating the issue. Unfortunately, for now, this issue may occur on some buckets that are not bound to a region. For now, try using a bucket that has regional constraint.