GetSlides Fails with AmazonS3 Storage Exception on AWS Access Key Id

Aspose.Slides Cloud Product Family
1

Issue Description

We are experiencing a sudden failure with the Aspose.Slides API that was working perfectly until yesterday. The API is now throwing an AmazonS3 Storage exception related to AWS Access Key Id.

Timeline

  • Until Yesterday: API was functioning normally with no issues
  • Today 6AM(UTC): We have found API started failing with AmazonS3 Storage exception

Error Details

GET http://api.aspose.cloud/v3.0/slides/494ad200-5e38-4663-a634-bd4e274e9a01.pptx/slides
Method Name: GetSlides
Product: Aspose.Slides
API Version: v3.0

Details
Error: GetSlides. Exception: AmazonS3 Storage exception: The AWS Access Key Id you provided does not

Application
Name: videostep
Client Id: caa1ee74-4e0d-4bc7-9aбe-c6cc5c17f198
Client Secret: e2eabeb55d6bd2ac50727ffa446c7d9c
Default Storage: Oeacb812-8898-4fb4-93be-a2c7e9f98d87
Created Date: 2023-09-13

Request Details
IP Address: 106.72.223.0, 172.22.0.21
Request Trace Id: 3ad5c7f0-72226-429f-a057-cd8cab09bbb9
Request Start Date: 2025-09-05 2:56:28 PM
Request End Date: 2025-09-05 2:56:28 PM

Thank you for your assistance in resolving this issue.

2

@VideoStep

Hello,

We’re sorry to hear that the GetSlides call is now failing with an AmazonS3 storage exception.
Below you’ll find the most common reasons for this error and the steps you can take to resolve it quickly.

Why the “AWS Access Key Id you provided does not …” error appears

Possible cause What it means How to verify / fix
The storage credentials (Access Key / Secret Key) are invalid or have been revoked The S3 bucket that Aspose Cloud uses for your default storage no longer accepts the key that was originally supplied. • Log into the Aspose Cloud Dashboard → Storage page.
• Verify the Access Key Id and Secret Access Key for the storage named Oeacb812-8898-4fb4-93be-a2c7e9f98d87.
• If you suspect the keys were rotated, update them (or re‑create the storage) and save.
The storage has been deleted or its bucket policy changed The bucket referenced by the storage ID no longer exists or its policy blocks the Aspose service. • Check the bucket existence in the AWS console.
• Ensure the bucket policy allows s3:GetObject, s3:PutObject, and s3:ListBucket for the IAM user whose keys you are using.
The default storage reference is corrupted The “default storage” GUID stored in your Aspose Cloud app points to a storage that is no longer valid. • In the Aspose Cloud Dashboard → Applications, open your app (videostep).
• Re‑select a valid storage as Default Storage (or remove the default and set it at request time).
OAuth token expired / client secret changed If the client secret was regenerated, the existing access token becomes invalid, causing the request to be rejected before it reaches the storage layer. • Regenerate a fresh access token using the client id / client secret you posted.
• Use that token for the next request.
Network / IP restriction on the S3 bucket The bucket’s VPC endpoint or IP whitelist no longer includes the IP address from which Aspose Cloud is calling. • Verify any IP‑based restrictions in the bucket’s CORS or VPC endpoint settings.

Immediate steps to get GetSlides working again

  1. Validate / Refresh Storage Credentials

    # Example: Re‑create the storage using the Aspose Cloud REST API
POST https://api.aspose.cloud/v3.0/storage
Content-Type: application/json
Authorization: Bearer <YOUR_ACCESS_TOKEN>

{
    "Name": "MyS3Storage",
    "Type": "AmazonS3",
    "AccessKey": "NEW_AWS_ACCESS_KEY_ID",
    "SecretKey": "NEW_AWS_SECRET_ACCESS_KEY",
    "Region": "us-east-1",
    "Bucket": "my-aspose-bucket"
}
    • After the storage appears in the list (GET /v3.0/storage), set it as the default for your application in the dashboard.

  2. Regenerate an OAuth 2.0 access token

    POST https://api.aspose.cloud/connect/token
Content-Type: application/x-www-form-urlencoded

grant_type=client_credentials
&client_id=caa1ee74-4e0d-4bc7-9aбe-c6cc5c17f198
&client_secret=e2eabeb55d6bd2ac50727ffa446c7d9c

    Use the returned access_token in the Authorization: Bearer <token> header for all subsequent calls.

  3. Test the GetSlides endpoint with Swagger / Postman

  4. If the error persists, re‑assign a different default storage

    In the Aspose Cloud Dashboard → Applications → videostep, change Default Storage to a different, already‑working storage (or leave it blank and specify storage query‑parameter in each request).

How to check the current storage configuration via the API

# List all storages
GET https://api.aspose.cloud/v3.0/storage
Authorization: Bearer <YOUR_ACCESS_TOKEN>

# Get details of a specific storage (replace GUID with your storage name)
GET https://api.aspose.cloud/v3.0/storage/<storageName>
Authorization: Bearer <YOUR_ACCESS_TOKEN>

The response will show the exact AccessKey, Region, and Bucket that Aspose Cloud is using. Verify that those values match the ones in your AWS console.

Recommended preventive measures

  • Rotate AWS keys periodically and update the corresponding Aspose Cloud storage entries immediately.
  • Enable Cloud‑side logging (GET /v3.0/storage/logs) to capture any future credential mismatches.
  • Monitor the Aspose Cloud Dashboard → Applications → “Last Used” timestamps – an abrupt change often signals a revoked key or bucket deletion.
  • Set up a health‑check script that periodically calls a lightweight API method (e.g., GET /v3.0/slides/{fileName}/info) for a known file; alert you if the call fails with a storage‑related error.

Next steps & information we may need

If you have already performed the steps above and the problem still occurs, please provide the following details so we can dive deeper:

  1. Exact SDK / language version you are using (e.g., Aspose.Slides for .NET 23.10, Java 23.10, etc.).
  2. Full request headers (especially the Authorization header) – you can obtain these from your HTTP client or from the Aspose Cloud Dashboard Request Logs.
  3. Whether the file (494ad200-5e38-4663-a634-bd4e274e9a01.pptx) is stored in the default storage or you are passing a storage query parameter.
  4. Any recent changes to the AWS IAM user, bucket policy, or region.

Feel free to share sanitized logs (remove the real secret values) and we’ll continue the investigation.

Helpful links

If you need any further assistance, just let us know. We’re here to help you get your Slides processing back on track! :rocket:

3

@VideoStep,
Thank you for reporting the issue. I have reproduced the AmazonS3 Storage exception when using the GetSlides method. We apologize for any inconvenience caused.

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): SLIDESCLOUD-2068

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.