Aspose Api Error

Hello!

We have faced error
Aspose.Words.Cloud.Sdk.ApiException: Error while get files in folder ‘Font’ from storage: Error while get file list in folder ‘Font’ from storage: 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.
at Aspose.Words.Cloud.Sdk.RequestHandlers.ApiExceptionRequestHandler.ThrowApiException(HttpWebResponse webResponse, Stream resultStream)
at Aspose.Words.Cloud.Sdk.RequestHandlers.ApiExceptionRequestHandler.ProcessResponse(HttpWebResponse response, Stream resultStream)
at System.Collections.Generic.List1.ForEach(Action1 action)
at Aspose.Words.Cloud.Sdk.ApiInvoker.ReadResponse(WebRequest client, Boolean binaryResponse)
at Aspose.Words.Cloud.Sdk.ApiInvoker.InvokeInternal(String path, String method, Boolean binaryResponse, String body, Dictionary2 headerParams, Dictionary2 formParams, String contentType)
at Aspose.Words.Cloud.Sdk.WordsApi.ConvertDocument(ConvertDocumentRequest request)

Could you please help us with this error?
We want to notice, that we use an internal storage to save fonts.

Thank you!

@AsposeCreatio

The error you are encountering, Aspose.Words.Cloud.Sdk.ApiException: Error while get files in folder ‘Font’ from storage: Error while get file list in folder ‘Font’ from storage: AmazonS3 Storage exception: The bucket you are attempting to access must be addressed using the specified endpoint, indicates that there is an issue with the way your application is trying to access the Amazon S3 bucket where your fonts are stored.

This error typically arises when the S3 bucket is not being accessed through the correct endpoint. Here are some steps you can take to resolve this issue:

  1. Check the S3 Bucket Endpoint: Ensure that you are using the correct endpoint for your S3 bucket. Each S3 bucket is associated with a specific region, and you need to use the endpoint that corresponds to that region. For example, if your bucket is in the us-east-1 region, the endpoint should be s3.amazonaws.com.

  2. Update Your Configuration: If you are using a configuration file or environment variables to set the S3 bucket details, make sure that the endpoint is correctly specified there.

  3. Verify Permissions: Ensure that the IAM user or role that your application is using has the necessary permissions to access the S3 bucket. This includes permissions to list the contents of the bucket.

  4. Test with AWS CLI: You can use the AWS CLI to test access to the S3 bucket. This can help you determine if the issue is with your application or with the S3 configuration itself. Use a command like:

    aws s3 ls s3://your-bucket-name --region your-region
    
  5. Contact Support: If the issue persists after checking the above points, consider reaching out to Aspose support with details of your implementation, including the code you are using to access the S3 bucket.

If you have any specific code snippets or configurations that you would like to share, I can help you review them for potential issues.

Thank you for your response. We would like to clarify that we are not using Amazon S3 or any external storage in our integration with Aspose.Words Cloud. We are using only Aspose’s internal (default) storage.

However, we are receiving the following error during document conversion:

Aspose.Words.Cloud.Sdk.ApiException: Error while get files in folder ‘Font’ from storage: …
AmazonS3 Storage exception: The bucket you are attempting to access must be addressed using the specified endpoint.

This suggests that the SDK or the Aspose Cloud backend is attempting to access Amazon S3, even though we do not specify any StorageName in our requests, and we do not have any external storage configured in our account.

Could you please help us investigate why this call is being redirected to S3 when we are only using internal storage, and how we can prevent that behavior?

You are getting this error because the Aspose internal storage is also using S3 and it looks like it’s not working:

1 Like

The work of fixing is in progress.
Sorry for the inconvenience.

Thank you for the information.

The task was created: Issues with storage after release 25.7