[bug] S3 Backup Configuration Fails with Incorrect Endpoint

[utkuozdemir]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

S3 backup configuration fails with the following error when saving credentials:

Failed to Update Storage Config
failed to validate: 1 error occurred: * incorrect settings for s3 client: failed to list objects in bucket "***": operation error S3: ListObjects, https response error StatusCode: 404, RequestID: ..., api error NoSuchKey: The specified key does not exist.

Investigation & Findings

• Credentials tested successfully using:

  aws s3 ls s3://****/

  This confirms the bucket exists and is accessible.
• Issue identified with the endpoint:
  • Setting the endpoint to https://***.s3.us-east-1.amazonaws.com caused failures.
  • Setting no endpoint resulted in an invalid URI error.
  • Fix: Using https://s3.amazonaws.com as the endpoint resolved the issue.
• Root Cause: us-east-1 is a legacy region with a region-less endpoint. The SDK should determine the endpoint automatically.

Suggested Fix

• Allow AWS SDK to automatically determine the endpoint when none is provided.
• Ensure that setting an explicit endpoint is only necessary for non-standard S3-compatible storage.

Expected Behavior

It to not fail.

Steps To Reproduce

1. Navigate to Settings > Backups in Sidero Omni.
2. Configure the S3 storage with the following values:
   • Endpoint: https://****.s3.us-east-1.amazonaws.com
   • Bucket: ****
   • Region: us-east-1
   • Access Key ID and Secret Access Key: (valid credentials)
3. Click Save.
4. Observe the failure message indicating NoSuchKey or Custom endpoint was not a valid URI.

What browsers are you seeing the problem on?

No response

Anything else?

No response

[github-actions]

This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 7 days.