DBeaver is integrated with AWS IAM authentication.
Thus it provides the possibility to authenticate in AWS to access your cloud databases.
AWS IAM has endless ways to authorize and authenticate users. DBeaver supports all basic ones.
When you use Default Credentials, AWS will then try to determine credentials by using the standard credential providers chain:
- Java system properties
- Environment variables
- Web identity token from AWS STS
- The shared credentials and config files
- Amazon ECS container credentials
- Amazon EC2 instance profile credentials
- Amazon SSO credentials
Using default credentials is essentially the simplest way to integrate with various SSO providers and web identity providers as they usually provide credentials through config files.
Please read the AWS credentials documentation for a detailed explanation.
It is the most straightforward way to authenticate. You only need to enter the IAM user access key and secret key. You can save them locally or (more securely) enter them every time you connect to a database.
Official AWS instructions: Managing access keys for IAM users
Similar to default credentials but you can also choose which credentials profile you want to use.
The official AWS instructions can be found at credentials config files.
If your AWS account has a configured SSO portal, you can use a web-based SSO authorization.
SSO support can be enabled for Default and Profile-based AWS authorization types.
You need to turn on the "Enable SSO" option.
AWS Secrets Manager
If you have a configured AWS Secret you can use it to access you database. Secrets can be used for a RDS databases and Redshift. Instructions on how to create AWS Secret can be found here. Password field is required.
Secret needs to be in the same region as the database.