From what we've been told, the AWS Connector sets these environment variables to work

AWS_ACCESS_KEY

AWS_SECRET_ACCESS_KEY

AWS_SESSION_TOKEN

Setting these seems to override all profiles used in Terraform. We'd like the ability to use this connector without overriding the profiles we have set. To give some context, each team sets 1-3 different profiles in order to accomplish their Terraform Deployment. Usually each of these profiles only has permissions to specific parts of what we are trying to accomplish in Terraform. For example, the default profile we use has access to the S3 backend but the dev profile has access to the resources being deployed in Terraform. If we use the connector and set it to the credentials for the default profile, we're able to initialize the backend but we're not able to run Plan or Apply successfully. The reverse is true if we set the connector credentials to dev. We aren't able to initialize the backend but, if we remove it, we're able to run Plan and Apply just fine.

It'd be great if we could add some functionality or feature to set the connector as a separate profile instead of always setting the aforementioned environment variables which will override the profiles we have set.