bug: SES and S3 cannot use different credentials when using S3-compatible providers

[badal8381]

Description

AWS Settings has a single set of AWS credentials (Access Key ID and Secret Access Key) shared by both S3 file storage and SES email. When
using an S3-compatible provider like Wasabi, Backblaze B2, or MinIO alongside Amazon SES, both services are forced to use the same
credentials — which won't work since they are different providers with different authentication.

Steps to Reproduce

1. Go to AWS Settings
2. Enter Wasabi credentials for S3 file storage
3. Enable S3 — works correctly with Wasabi
4. Enable SES email — fails because Wasabi credentials are invalid for Amazon SES

Expected Behavior

It should be possible to use S3-compatible storage (Wasabi, B2, MinIO) for file storage and Amazon SES for email simultaneously.

Actual Behavior

Both services share the same credentials, so only one provider can work at a time.

Environment

• Frappe v15
• AWS Integration: s3 branch
• Affects any setup combining S3-compatible providers with Amazon SES

[SamarthPansare]

I’d like to take this up.
My understanding is that the fix would involve separating S3 and SES credentials in AWS Settings instead of using a single shared configuration.
Please confirm if this approach aligns with the expected solution.