Multiple s3Storage instances share S3 client configuration

[sharathsDev]

Describe the Bug

Description

When using two s3Storage plugin instances with different endpoints (e.g., AWS S3 and Cloudflare R2), the second plugin's endpoint configuration overwrites the first plugin's configuration, causing requests to use mixed endpoints.

Link to the code that reproduces this issue

private

Reproduction Steps

Configuration:

import { s3Storage } from '@payloadcms/storage-s3'

export default buildConfig({
  plugins: [
    // Plugin 1: AWS S3
    s3Storage({
      bucket: 'my-s3-bucket',
      collections: {
        fileupload: { /* ... */ },
        postmedia: { /* ... */ },
      },
      config: {
        credentials: { /* S3 credentials */ },
        endpoint: 'https://s3.us-east-1.amazonaws.com',
        region: 'us-east-1',
        forcePathStyle: true,
      },
    }),
    
    // Plugin 2: Cloudflare R2
    s3Storage({
      bucket: 'my-r2-bucket',
      collections: {
        media: { /* ... */ },
      },
      config: {
        credentials: { /* R2 credentials */ },
        endpoint: 'https://account-id.r2.cloudflarestorage.com',
        region: 'auto',
        forcePathStyle: true,
      },
    }),
  ],
})

Steps:

1. Configure two s3Storage plugins as shown above
2. Upload a file to the fileupload collection (first plugin)
3. Observe the error

Expected Behavior

Each plugin instance should maintain its own isolated S3 client with independent endpoint configuration.

Actual Behavior

The upload request uses a mixed endpoint:

Host: my-s3-bucket.account-id.r2.cloudflarestorage.com

Error received:

ERROR: Access Denied
httpStatusCode: 403
servername: "my-s3-bucket.account-id.r2.cloudflarestorage.com"

The hostname incorrectly combines:

• Bucket name from the first plugin (my-s3-bucket)
• Endpoint from the second plugin (.r2.cloudflarestorage.com)

Which area(s) are affected? (Select all that apply)

plugin: storage-*

Environment Info

### Environment
- **Payload Version:** 3.58.0
- **@payloadcms/storage-s3 Version:**3.58.0
- **Node Version:** v22.20.0
- **Package Manager:** pnpm

[github-actions]

Please add a reproduction in order for us to be able to investigate.

Depending on the quality of reproduction steps, this issue may be closed if no reproduction is provided.

Why was this issue marked with the invalid-reproduction label?

To be able to investigate, we need access to a reproduction to identify what triggered the issue. We prefer a link to a public GitHub repository created with create-payload-app@latest -t blank or a forked/branched version of this repository with tests added (more info in the reproduction-guide).

To make sure the issue is resolved as quickly as possible, please make sure that the reproduction is as minimal as possible. This means that you should remove unnecessary code, files, and dependencies that do not contribute to the issue. Ensure your reproduction does not depend on secrets, 3rd party registries, private dependencies, or any other data that cannot be made public. Avoid a reproduction including a whole monorepo (unless relevant to the issue). The easier it is to reproduce the issue, the quicker we can help.

Please test your reproduction against the latest version of Payload to make sure your issue has not already been fixed.

I added a link, why was it still marked?

Ensure the link is pointing to a codebase that is accessible (e.g. not a private repository). "example.com", "n/a", "will add later", etc. are not acceptable links -- we need to see a public codebase. See the above section for accepted links.

Useful Resources

• Reproduction Guide
• Contributing to Payload