It seems like the AWS-secrets-manager-credentials-provider-plugin plugin assumes your running on EC2 (with a role) or have injected aws creds via env vars directly into the master's session

Id like to just configure access via a credential binding like I can for most of the other plugins

So I can tell the aws-secrets-manager-credentials-provider-plugin which cred binding to use which has AWS access keys with read access to Secrets Manager