Aspose Cloud Giving Us An AmazonS3 Storage Exception

Aspose.PDF Cloud Product Family
1

Hi support,

Earlier today we’ve been getting this error:

"“AmazonS3 Storage exception: The AWS Access Key Id you provided does not exist in our records. Bucket ‘aspose.cloud-filestorage-prod’”

This is preventing us from delivering custom user-licensed pdfs to our members.

  1. We don’t have any configuration with S3
  2. We need this fixed ASAP
1 Like
2

@support.oceg.org

Overview

The “AmazonS3 Storage exception: The AWS Access Key Id you provided does not exist in our records.” message is generated by Aspose Cloud when the internal file‑storage bucket (aspose.cloud‑filestorage‑prod) cannot be accessed with the credentials that Aspose uses on its side.

Because you are not configuring an external S3 bucket, this error points to an authentication problem with Aspose Cloud’s own storage service (e.g., an expired/invalid client secret or a temporary service outage).

Immediate actions you can take

Step What to do Why it helps
1. Verify your access token Re‑request an access token using your Client Id and Client Secret (or OAuth token if you use that flow).
csharp<br>var client = new Aspose.Pdf.Client(<br> clientId: "YOUR_CLIENT_ID",<br> clientSecret: "YOUR_CLIENT_SECRET"<br>);<br>var token = await client.GetAccessTokenAsync();<br>		 If the token request fails, the subsequent PDF operation will also fail with the S3 error.
2. Regenerate the Client Secret Log in to the Aspose Cloud Console → App Management → select your app → Regenerate Secret. Update your code with the new secret. A compromised or expired secret can cause the internal storage service to reject the request.
3. Ensure you are using the latest SDK Download the latest NuGet/ Maven / pip package for the product you are using (e.g., Aspose.Pdf.Cloud). Older SDKs may contain hard‑coded endpoint URLs that no longer match the current storage backend.
4. Check Aspose Cloud Service Status Visit the Aspose Cloud Status page: https://status.aspose.cloud/. Look for any incidents related to File Storage or Authentication. If there is a temporary outage, the only remedy is to wait for the service to be restored.
5. Disable any custom storage configuration If you have called PdfApi.SetStorage(string storageName) or set storage parameters, remove them or set the storage name to "Default" (or simply omit the parameter). Custom storage names force the SDK to look for a bucket that may not exist in your account.

How to reproduce the error (for reference)

var pdfApi = new Aspose.Pdf.Cloud.Sdk.Api.PdfApi(clientId, clientSecret);
var request = new SavePdfOptions
{
    // Do NOT set Storage = "YourS3Bucket"
};

var result = await pdfApi.PutPdfInStorageAsync(
    name: "template.pdf",
    folder: "",
    storage: null,        // <-- leave null to use Aspose default storage
    outPath: "output.pdf",
    body: request);

If the access token is invalid, the call above returns the AmazonS3 storage exception you are seeing.

What to provide if the issue persists

If the steps above do not resolve the problem, please open a support ticket (or reply to this thread) with the following details so we can investigate quickly:

Information Description
Request ID / Call ID (if available) Returned in the exception body (X-Request-ID, X-Call-ID).
SDK version e.g., Aspose.Pdf.Cloud.SDK 22.12.0.
Authentication method Client‑Id/Secret, JWT, or OAuth.
Exact code snippet that triggers the error (including token acquisition).
Timestamp of the failing request (UTC).
Environment .NET Core, Java, Python, etc., and OS version.
Any recent changes New deployment, firewall/proxy updates, etc.

Providing these details allows our engineers to locate the call in the logs and determine whether the problem is on the Aspose side or a mis‑configuration in your application.

Helpful links

Next steps

  1. Try the token regeneration and SDK update steps above.
  2. If the error remains, reply with the details listed in the “What to provide” table.

We’ll prioritize this issue and work with you to get the PDFs delivered again as soon as possible.

Thank you for using Aspose Cloud!

— Aspose Support Team

3

Hi, @support.oceg.org
What settings for storage do you use, is it possible to download and view files in the bucket via the interface Dashboard. Provide examples of code that give an error.

4

We’ve regenerated the private key, updated our Node client, and created a new internal storage. Still getting the error, even when attempting an upload from a static local file inside a unit test:

const fileContent = fs.readFileSync(‘…/…/functions/emails/cancellation-policy.pdf’);
const pdfApi = new pdfApiPkg.PdfApi(process.env.ASPOSE_CLIENT_ID, process.env.ASPOSE_CLIENT_SECRET);
const sdkUploadResult = await pdfApi.uploadFile(‘cancellation-policy.pdf’, fileContent, ‘Stamp’);

We got an error saying the S3 Key ID doesn’t exist.

We then attempted to bypass the client and use the REST API directly, using Node Fetch. Now both fetch and the Aspose client get a 503 Service unavailable.

5

We are getting the same error when trying the API on your own site:

https://reference.aspose.cloud/pdf/#/File/UploadFile

Response:

{
“Uploaded”: [],
“Errors”: [
{
“Code”: “errorAmazonS3Storage”,
“Message”: “AmazonS3 Storage exception: The AWS Access Key Id you provided does not exist in our records.”,
“Description”: “Operation Failed. Exception of type ‘Amazon.Runtime.Internal.HttpErrorResponseException’ was thrown.”,
“InnerError”: {
“RequestId”: null,
“Date”: “2025-09-05T08:34:55.0088787+00:00”
}
}
]
}

6

@support.oceg.org
Please check this interface Dashboard. Do you check bucket exist before uploading files?

7

We use your internal storage. We have even tried creating a new one and using that. Still getting errors.

8

@support.oceg.org
Please check the error now, it should work.

9

Confirmed, the issue is resolved thank you.