Referencing https://github.com/xataio/agent/wiki/Xata-Agent-%E2%80%90-AWS-integration-guide

For your AWS users, they're probably running the agent container on AWS already, so it's redundant to create a separate IAM user which increases the security risk profile. Instead, you could leverage the IAM role already associated with the EC2 instance, ECS task, or IRSA (for k8s deployments) directly.

Could you add an option to the Cloud Management Integration page whereby a user can check a radio button that says like "use service-linked role", omit static credentials, and then run your permissions check during save?

This would greatly improve the security posture of your customers while using your tooling.

Thanks for reading and considering this.

--Chase