[Feature Request] Auto-detect AWS Amplify key structure and enforce AWS Amplify ENV var naming constraints

Bug Description

Root cause: Amplify uses S3_ACCESS_KEY_ID / S3_SECRET_ACCESS_KEY instead of the standard AWS_ACCESS_KEY_ID /
AWS_SECRET_ACCESS_KEY. The @aws-sdk/client-ses couldn't find credentials via its default provider chain.

Basically I am running an AWS AMPLIFY app so the key naming conventions must be followed as per AWS Amplify naming guidelines. Given the app is Amplify it should already know the key structure and it should know the prefix on the ENV vars in AWS Amplify have special rules (They cannot start with AWS I think and they instead usually start with S3_ or similar)

Environment Info

• Platform: win32
• Terminal: windows-terminal
• Version: 2.1.63
• Feedback ID: c7f52a82-b4bf-4651-af5c-d868b8b1e8a5