Aspose Words Cloud uploadFile Error

Aspose.Words Cloud Product Family
1

We recently started receiving an S3 error when attempting to use the uploadFile function within the Words API.

The error is as follows:

code: "errorAmazonS3Storage"
description: "Operation Failed. Exception of type 'Amazon.Runtime.Internal.HttpErrorResponseException was thrown.'"
message: "AmazonS3 Storage exception: The bucket you are attempting to access must be addressed using the specified endpoint. Please send all future requests to this endpoint."

This error just started recently within a section of code that has worked without issue for many months, so we assume it has to do with a recent update within AWS/Aspose.

Do you have any insight as to how we can fix this?

Thanks

2

@jessewilliams

We are sorry for the inconvenience. We are investigating the issue of why Aspose storage is failing for some users.

3

any updates on this, We are also facing the same

4

Started getting this error again this morning

5

We are also facing the same about 12 hours before

6

Sorry for the inconvenience. We are investigating this issue. Please share if you use default Aspose storage or link your s3. In case of other s3 buckets, please share the region: west, east, etc.

7

we use default Aspose storage

8

We are also seeing this same error, using the default internal storage. Is there anything we can do to fix this? Thanks!

9

@jessewilliams
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.

Issue ID(s): WORDSCLOUD-2759

You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.

10

Please try our API reference at Aspose.Words Cloud - API References, authorize with your credentials, and use the “Upload File” method. By doing this, we will be able to determine if the issue is related to the SDK or not.

11

I Have done it, Same Error.
image.png (164.8 KB)

12

We have deployed a fix, and everything should now work fine. The issue was due to the incorrect functioning of the Amazon S3 SDK. Please try again and let us know if you encounter any further problems.

Thank you for your patience.

13

The issues you have found earlier (filed as WORDSCLOUD-2759) have been fixed in this update. This message was posted using Bugs notification tool by Ivanov_John