Cloud Provider Settings

Start Here

Manual Home Installation Getting Started Licensing Servers Connect Database Servers Troubleshoot Connectivity Host OS Login Enable WMI Multi-Engine Settings

Console

Console Overview Enterprise View AI Assistant Execution Plans Alerts Custom Alerts Reports Settings Service Log Connectivity Log Web Log About

PostgreSQL

Overview Connection and Permissions Activity Databases Queries Waits Memory I/O Indexes Deadlocks Server Log Settings Permissions Health Checks Alerts Performance Tuning

MySQL/MariaDB

Overview Connection and Permissions Activity Databases Queries Memory I/O InnoDB Permissions Deadlocks Health Checks Alerts Performance Tuning

Oracle

Overview Connection and Permissions Activity Databases Queries Waits Memory Health Checks Alerts Performance Tuning

Settings And Integrations

Security SQL Options Email Server Alert Recipients Recipient Groups Server Groups Cloud Providers Web Proxy Slack Microsoft Teams PagerDuty Jira Performance Logging AI Provider MCP Server

Legacy Documentation

Cloud Provider settings store credentials used by Mini DBA for cloud-related monitoring and integration workflows. The page includes AWS and Azure credential fields.

AWS Fields

Access Key ID.
Secret Access Key.
Region.

Azure Fields

Tenant ID.
Client ID.
Client Secret.
Region.

Test Cloud Connectivity

Enter the cloud provider credentials.
Select Save.
Select Test Connection.
Confirm the test succeeds.
If it fails, verify credentials, region, permissions, network access, and web proxy settings.

Security Notes

Use least-privilege cloud credentials. Rotate credentials according to your organization policy and remove credentials that are no longer required.

Cloud Credential Guidance

Cloud Provider settings are used when Mini DBA needs to reach cloud APIs for monitoring or integration workflows. Treat these credentials as production secrets. Store only the credentials needed for the monitored estate, restrict permissions to the required cloud resources, and rotate secrets according to your security policy.

For Azure SQL monitoring, cloud credentials may sit alongside database credentials. The cloud identity helps with provider-level information, while the database login or Entra user controls database-level visibility. If Azure SQL pages show missing database data, review Connect To Azure SQL and Azure SQL Permissions as well as the cloud provider settings.

If Test Connection fails, check the tenant or account identifiers, region, network path, proxy settings, secret expiry, and whether the identity has permission to call the required cloud APIs. In locked-down networks, Web proxy settings may be required for outbound HTTPS access.