Please note: This article has been updated and its content is now available in a revised form at a new location. Please refer to the updated article Cloud Explorer for the most current information.

CloudBeaver AWS is a multi-user web tool for managing databases, built to work with Amazon Web Services (AWS). It allows teams to collaborate easily and take advantage of AWS infrastructure. This edition is especially useful for teams and organizations using AWS cloud environments. It provides a shared, web-based platform for managing databases, making it easier to collaborate, access, and manage data while using AWS infrastructure.

The CloudBeaver AWS Edition provides a powerful set of features tailored for database management within the AWS ecosystem. These features focus on seamless integration with AWS services, scalability, security, and collaboration.

• AWS Services

  • Cloud Explorer: A tool for managing and connecting cloud-hosted databases. Learn more.
  • Amazon S3 support: Manage cloud storage directly from CloudBeaver by integrating with Amazon S3. Learn more.

• Secure access

  • Access management: CloudBeaver AWS integrates IAM, SAML, OpenID, and various security identity providers to provide secure access. Learn more.
  • User management: Centralize access control with admin tools. Import users directly from identity providers like Google, Okta, and Azure. Learn more.

• Collaboration

  • Multi-user collaboration: Collaborate in real-time with multiple users, setting custom teams and permissions to maintain data security.
  • Query history: Track and review past queries. Learn more.

• Data management and SQL development

  • Data filters and views: Utilize flexible filters and interactive views for efficient data handling. Learn more.
  • SQL development tools: Enhance SQL development with autocomplete, syntax highlighting, and script execution capabilities. Learn more.

• Data import/export

  • Data export: Export data to a variety of formats, including CSV, Excel, and more. Learn more.
  • Data import: Import data from files directly into your database. Learn more.

• Data Visualization

  • Entity relationship diagrams: Visualize database schemas through entity-relationship diagrams. Learn more.

• Query development

  • AI assistant in SQL Editor: Integrates an AI assistant to offer guidance and automation within the SQL Editor. Learn more.
  • Search in query history: Enables searching through previous queries for easier management and reuse. Learn more
  • Visual query builder: Provides a graphical interface to construct SQL queries without writing code. Learn more.

CloudBeaver AWS has a comprehensive set of JDBC drivers, offering connectivity to various databases without needing separate downloads and configurations.

The CloudBeaver AWS provides support for a wide range of databases. For a full list of supported databases, refer to Supported databases.

CloudBeaver AWS is available for subscription through the AWS Marketplace. The subscription price depends on the instance size you choose. A bigger instance allows more users to work with the application at the same time.

You get a one-month free trial with access to all CloudBeaver features. After the trial, billing is managed based on the AWS pricing plan for the chosen instance size. You don’t need an extra license, as everything is handled through the AWS Marketplace subscription.

In rare cases, CloudBeaver AWS may request a license if access to the EC2 metadata service is restricted. This is often due to enforced IMDSv2 policies by AWS. Since CloudBeaver runs inside a Docker container with a different network interface, it might be unable to communicate with the EC2 instance metadata. Refer to the Troubleshooting section for guidance on resolving this issue.

After subscribing, navigate to

For more information on initial configuration, see Server configuration wizard.

CloudBeaver AWS runs inside a Docker container on your EC2 instance. To update it manually, connect to your EC2 instance via SSH or the instance console, and pull the desired Docker image.

To update CloudBeaver AWS:

1. Access your EC2 instance via SSH.
2. Once connected, stop the running CloudBeaver container, pull the latest Docker image, remove the old container, and start the updated version.

Refer to the following documentation for additional guidance:

• CloudBeaver AWS images and tags on Docker Hub
• AWS EC2: Connecting via SSH
• AWS key pairs
• Docker documentation

For technical support with CloudBeaver AWS, you will need to submit a ticket through the DBeaver customer portal on dbeaver.com. When creating a support request, ensure to include your AWS Agreement ID, which is necessary for verifying your subscription.

You can locate your Agreement ID by going to AWS Marketplace > Manage Subscriptions and selecting CloudBeaver AWS. This ID is essential for the CloudBeaver support team to handle your request properly.

Tip: If you need assistance on how to access the Manage Subscriptions section, refer to the official AWS documentation.

Once you have your Agreement ID, log into your account on the DBeaver website, navigate to Profile -> Tickets, and create a new support ticket. Be sure to include all relevant details about the issue to allow the support team to assist you effectively.

CloudBeaver AWS installations from the AWS Marketplace may prompt for a license due to issues with EC2 metadata service availability. This can happen when AWS policies enforce the use of IMDSv2 and restrict access to IMDSv1.

Since CloudBeaver runs inside a Docker container, it operates with a different IP address, which prevents it from connecting to the EC2 metadata service using IMDSv2. As a result, CloudBeaver cannot verify that it was launched through a Marketplace installation.

Solution: To resolve this, ensure your Docker container is run with the

Note: This feature is available in Enterprise, AWS, Team editions only.

This article guides you through the initial steps to configure AWS integration in CloudBeaver.

Once AWS integration is configured, you can access Cloud Explorer, and Cloud Storage.

Configuring an Identity Provider is essential for authenticating and authorizing user access to AWS resources.

For a list of available Identity Providers and detailed configuration instructions, see Authentication Methods.

You can configure the AWS partitions and regions where your resources are located. This ensures the system connects to the correct environment based on your selection.

1. Go to Settings -> Administration -> AWS Settings.
2. In the Partition dropdown, select the partition where your resources are located:
   • AWS Standard: Standard AWS regions.
   • AWS China: Regions compliant with Chinese regulations.
   • AWS GovCloud (US): Regions for sensitive or regulated U.S. government workloads.
3. After selecting a partition, choose one or more AWS regions from the Region List.
4. Click Save to confirm and apply your settings.

Note: This feature is available in Enterprise, AWS, Team editions only.

CloudBeaver allows for database connections through AWS SAML with Okta authentication. This guide details the process for establishing such connections. Please ensure you meet all the prerequisites outlined below before proceeding with the configuration steps.

• AWS IAM Configuration: An active configuration of AWS IAM is necessary. This includes a properly set up AWS account with IAM Connect enabled. Additionally, ensure the account has the required permissions to create and manage identity providers and roles.
• Okta setup: Access an Okta account with the necessary permissions to configure applications.
• CloudBeaver administrative access: Ensure administrative privileges in CloudBeaver.

For this type of authentication, proxy access keys and secret keys are not required. This means there is no need to generate static keys in AWS.

1. Log in to CloudBeaver as an Administrator.

2. Enable AWS services and AWS SAML provider:

   • Navigate to Settings -> Administration -> Server Configuration and select the checkboxes for both Cloud (AWS) and AWS SAML.

3. Create a blank Identity Provider:

   • Go to Settings -> Administration -> Identity Providers.
   • Click on the + Add button to create a draft of a new identity provider.
   • Initially, fill in only the necessary fields to generate the Sign-in/Sign-out URLs and ACS links. The remaining fields will be completed later.
   • After filling in the fields, click on the Create button to complete the blank identity provider configuration.

For instructions on configuring AWS Regions, see AWS Settings.

4. Copy links:

   1. Enter the newly created identity provider.
   2. Copy the Sign in, Sign out and the ACS link.
   3. Also, you need to copy the Entity ID link. To find the Entity ID link, click on the download metadata file link and copy the
      entityID
      value.

   

5. Create SAML 2.0 application in Okta:

   1. Initiate the process by creating SAML 2.0 application in Okta. For detailed steps, consult the official Okta documentation on application creation.

   

   2. Under Single Sign-on URL, paste the copied from CloudBeaver application Sign in link.
   3. In the same section, locate the Audience URI (SP Entity ID). To formulate the Entity ID link, start with the ACS link from CloudBeaver application. Modify this URL by replacing the segment that reads
      acs
      with
      metadata
      , and then paste this newly created link into the Audience URI (SP Entity ID) field.
   4. In the same section, locate the Show Advanced Settings button and click to open additional settings.
      • Find Other Requestable SSO URIs and click the Add Another + button. Paste the ACS link and enter
        0
        in the Index field.
      • Insert
        http://www.okta.com/${org.externalKey}
        into the SAML User ID field. This is your provider ID value, which is automatically populated.
   5. Click Next and then Finish to finalize these configurations.

   

6. Configure SAML settings in CloudBeaver:

   1. Access Settings -> Administration -> Identity Providers in CloudBeaver.
   2. Click on the identity provider that was set up for SAML integration.

   3. Retrieve SAML configuration URLs from Okta:

      • In Okta, navigate to the Sign On settings of your SAML application.
      • Expand the Hide details section to view the necessary URLs.

   4. Enter SAML details into CloudBeaver:

      • Copy the SSO sign-on URL, SSO sign-out URL, and the Issuer URL from Okta.
      • Paste these URLs into the corresponding fields in CloudBeaver’s identity provider settings.
      • Upload the IDP x509 certificate, which can be downloaded from Okta, into the respective field in CloudBeaver.
   5. Complete additional fields

   Field Name	Description
   Description (Optional)	Provide a brief description of the identity provider.
   Icon URL (Optional)	Enter the URL of an icon to represent this identity provider in CloudBeaver.
   User group mapping attribute (Optional)	Specify the attribute that will be used for mapping user groups between CloudBeaver and the identity provider.

   6. After entering all necessary information, save the settings to finalize the configuration of your SAML identity provider.

   

7. Add users to application in Okta:

   • In your newly created Okta application, assign people or groups. For detail steps, consult the official Okta documentation on assign applications to users.

8. Add Identity Provider in AWS IAM:

• Add a SAML identity provider in AWS IAM. This allows AWS to authenticate users managed by Okta. For comprehensive instructions, refer to the official AWS documentation on identity providers.

  

Hint to obtain the Metadata document:

• Navigate to Okta and select your application under Applications.
• Proceed to the Sign On tab, locate the SAML 2.0 section, and click on the Metadata URL.
• Then, paste this URL into a new browser tab to open the XML content. Copy the XML content displayed in your browser into a new file.

9. Configure a role for SAML 2.0 federation:

• The next step involves configuring an AWS role for SAML. This role will be used to grant permissions based on the authenticated identity from Okta. For a detailed walkthrough, visit the official AWS documentation on creating roles for SAML 2.0 federation.

  

Hints for filling fields on the initial page when creating a role:

• Attribute: You can choose
  SAML:iss
  .
• Value: To find Issuer, navigate to Okta and select your application under Applications. Then proceed to the Sign On tab, locate the SAML 2.0 section, and there you will find the Issuer URL to copy.

10. Configure SAML attributes in Okta for AWS:

To ensure proper session management and permissions during SAML authentication with AWS, configure the following SAML attributes in Okta:

• Steps to Configure SAML Attributes:

  • Go to Applications in Okta, select your application, and edit the SAML Settings under General.
  • Scroll down to find the SAML Settings section and click Edit to modify the configurations.
  • After entering the edit mode, proceed to the Configure SAML section.
  • Locate and fill in the Attribute statements (Optional) settings.

  

Note: In the Value for the Role attribute, ensure the ARNs are correctly copied from AWS IAM. The

roleArn

is the ARN for the role created for SAML integration, and

identityProviderArn

is the ARN for the identity provider (Okta) configured in AWS IAM.

Set a default role and AWS session lifetime in the SAML configuration for consistent permissions, or customize via attribute mapping for user-specific roles. See documentation for details.

11. Now you can log in through the newly created Federated authentication method in CloudBeaver, using the Configuration name you assigned during the setup.

12. Verify the integration of AWS SAML and Okta

    1. Once logged in, click on your username in CloudBeaver and navigate to the User Info tab.
    2. Here, you should see two AUTH tokens. Their presence indicates that the integration of AWS OpenID and Okta has been successfully completed, and CloudBeaver has access to the necessary credentials.

13. Following successful login, you can access the databases listed in Cloud Explorer that are integrated with your AWS account.

Note: This feature is available in Enterprise, AWS, Team editions only.

CloudBeaver supports AWS IAM authentication to enhance security for database operations within AWS environments.

This guide details the configuration process for AWS IAM authentication, applicable to all CloudBeaver versions, with an emphasis on the initial setup required for the AWS version.

For comprehensive setup information of AWS IAM itself, refer to the official AWS IAM documentation.

1. As an administrator, go to Settings -> Server Configuration.

2. Find the AWS option (in the Configuration section) and AWS IAM (in the Authentication Settings section). Activate this setting to enable AWS authentication.

   

3. Save the changes.

For instructions on configuring AWS Regions, see AWS Settings.

1. As an administrator, navigate to Settings -> Identity Providers.

2. Click on the + Add button.

3. Fill in the following fields:

   

   Field	Description
   Provider	Select AWS IAM from the dropdown menu.
   ID	Enter a unique identifier for the configuration.
   Configuration name	Enter a descriptive name for this configuration.
   Description	Provide a brief description of this identity provider configuration.
   Icon URL	Enter the URL of an icon to represent this provider.
   Disabled	Leave unchecked to enable this identity provider.
   Account IDs	Enter AWS Account IDs, separated by commas. Only users from these accounts are allowed.
   AWS session lifetime	Specify the duration for the AWS session in seconds.

Tip for Account IDs: You can create entries for different Identity Providers for a more flexible configuration.

4. Click on the Create button.

1. With the AWS configuration now established, proceed to the login screen.

2. You will be presented with two options for key types:

   • For permanent credentials, select
     Static access keys
     .
   • If using credentials that change regularly, select
     Temporary access keys
     .

3. Input your

   Access Key
   and
   Secret Key
   in the respective fields.
   1. If you selected
      Temporary access keys
      , enter your
      Session Token
      in the additional field that appears.

4. Confirm your details and click the

   LOGIN
   button to authenticate.

   

Note: To make databases available for users who log in via AWS IAM, the administrator must first add the desired databases. This is done by navigating to Connections -> Cloud Connections and including them in the Database Navigator.

When configuring the CloudBeaver AWS Edition for the first time, AWS IAM credentials are mandatory. This version is optimized for the AWS Marketplace and specifically requires IAM authentication to integrate with AWS services.

During the initial launch, you are required to input your IAM user’s Access Key ID and Secret Access Key to establish the necessary AWS integrations.

• No Server-Side Key Storage: CloudBeaver is designed not to store AWS access and secret keys on the server, ensuring they are not held in databases or configuration files. This approach is crucial for maintaining the security of your data.

• Automatic administrator role assignment: The AWS user responsible for configuring CloudBeaver automatically receives administrator privileges in the CloudBeaver instance. This user will have comprehensive control over the instance’s settings and configurations.

• AWS account association: Upon completing the server configuration, the AWS account of the administrator is associated with the CloudBeaver instance. This means that only AWS users belonging to this specific account can authenticate and access this instance of CloudBeaver.

• User management within AWS scope: CloudBeaver for AWS does not support the creation of new users within its platform. It solely operates with existing AWS user accounts. Consequently, every user who needs access must authenticate through their AWS account.

• Database Authentication Requirements: AWS databases typically have their own authorization mechanisms, requiring additional authentication parameters such as a username and password. For RDS/Aurora databases using IAM authentication, you may only need to provide the database username, leaving the password field empty.

CloudBeaver uses the following AWS services in order to operate with databases (most of them are optional):

• STS (required): used for user authentication
• RDS: list RDS/Aurora instances for cloud databases explorer (describeDBInstances)
• Redshift: list Redshift clusters for cloud databases explorer (describeClusters)
• DynamoDB: all DynamoDB services for DynamoDB operating. Can be read-only for read-only DynamoDB access.
• DocumentDB: list DocumentDB clusters for cloud databases explorer (describeDBClusters)
• IAM (optional): additional user/organization information read (like account organization name)

CloudBeaver uses native database clients to connect and operate with most databases. It uses AWS services only to find database instances and configure database connection.
The only exception is the DynamoDB service which is a database driver by itself. You can limit DynamoDB access directly in the AWS console.

Note: This feature is available in Enterprise, AWS, Team editions only.

CloudBeaver allows for database connections through AWS OpenID with Okta authentication. This guide details the process for establishing such connections. Please ensure you meet all the prerequisites outlined below before proceeding with the configuration steps.

• AWS OpenID Configuration: An active configuration of AWS OpenID is necessary. This includes a properly set up AWS account with OpenID Connect enabled. Additionally, ensure the account has the required permissions to create and manage identity providers and roles.
• Okta setup: Access an Okta account with the necessary permissions to configure applications.

• CloudBeaver administrative access: Ensure administrative privileges in CloudBeaver.

1. Create an Application in Okta:

   • Initiate the process by creating an application in Okta. For detailed steps, consult the official Okta documentation on application creation.

   

2. Add Identity Provider in AWS IAM:

   • Add an identity provider in AWS IAM. This allows AWS to authenticate users managed by Okta. For comprehensive instructions, refer to the official AWS documentation on identity providers.

   

Hints for AWS IAM Identity Provider configuration: >- Provider URL: Use your Okta domain, for example,

your-domain.okta.com/

. >- Audience: Enter Okta’s client ID, which can be copied from the application created in Okta.

3. Configure a Role for Web Identity in AWS:

   • The next step is configuring an AWS role for web identity. This role will be used to grant permissions based on the authenticated identity from Okta. For a detailed walkthrough, visit the official AWS documentation on creating roles for identity providers.

   

4. Log in to CloudBeaver as an Administrator.

5. Enable AWS Services and AWS OpenID Provider:
   • Navigate to Settings -> Administration -> Server Configuration and select the checkboxes for both Cloud (AWS) and AWS OpenID.

6. Configure Identity Provider

   • Continue to Settings -> Administration -> Identity Providers.

   • Click on the + Add button to begin configuring a new identity provider.

     

   Below is the table with fields to be completed for configuring the identity provider:

> Important: The Role ARN added during this step acts as the default role. It’s not advisable to use an > administrator role at this step. It is recommended to use a role with minimum privileges during provider setup. >

After the provider is configured, you will see an AWS Role ARN field for each user, where > you can specify a role with higher privileges, if necessary.

• After filling in the fields, click on the Create button to complete the identity provider configuration.

> For instructions on configuring AWS Regions, see AWS Settings.

7. Copy Redirect and Sign out Links:

   1. Enter the newly created identity provider.
   2. Copy the Redirect link and the Sign out link.

   

8. Update Redirect URIs in Okta:

   1. In your Okta application, navigate to General -> Login.
   2. Under Sign-in redirect URIs, paste the copied Redirect link.
   3. In the same section, locate Sign-out redirect URIs and paste the Sign out link there.
   4. Click Save in Okta to finalize these configurations.

   

9. Now you can log in through the newly created Federated authentication method in CloudBeaver, using the Configuration name you assigned during the setup.

   

10. Verify the Integration of AWS OpenID and Okta

    1. Once logged in, click on your username in CloudBeaver and navigate to the User Info tab.
    2. Here, you should see two tokens. Their presence indicates that the integration of AWS OpenID and Okta has been successfully completed, and CloudBeaver has access to the necessary credentials.

    

11. Following successful login, you can access the databases listed in Cloud Explorer that are integrated with your AWS account.

Note: This feature is available in Enterprise, AWS, Team editions only.

CloudBeaver offers the ability to construct SQL queries using natural language through AI smart completion feature. This capability is achieved through integrations with OpenAI’s GPT language model, Azure OpenAI, Google Gemini and Ollama.

Note: CloudBeaver is not affiliated with OpenAI. Integration is achieved through the public API.

• To utilize this feature, register with OpenAI and obtain a secret key.

With the AI smart completion feature, you can type queries in natural language and CloudBeaver will convert them into SQL statements. This tool simplifies writing complex queries by interpreting your input and automatically generating the correct SQL code.

To activate the AI features in CloudBeaver, configure the API token:

1. Navigate to Settings -> Administration -> Server Configuration

2. Ensure the AI option is activated.

3. Navigate to AI Settings tab -> Choose an engine

4. Insert credentials.

5. Save the changes.

For instructions on utilizing the AI features, visit the AI Smart completion usage section.

We prioritize data safety and user privacy. In this section, we outline how data is managed and the measures taken to protect user privacy when using the AI features.

To enable AI features capabilities, metadata such as table and column names from the current database schema are transmitted to third-party AI services. This step is crucial for accurately translating user requests into SQL queries.

• No table data: Only metadata like table and column names are shared with OpenAI. Actual table data is not transmitted.
• Log transparency: The entire request can be logged for your review. To enable this, navigate to AI Settings tab and check the Write GPT queries to debug log option.
• Azure OpenAI privacy: If you use Azure OpenAI, be aware that it operates under its own privacy policy. It’s recommended to review their terms before using.

• Google Gemini privacy: When utilizing Google Gemini, it is important to understand the specific data privacy measures.

To utilize the AI-enhanced functionalities within CloudBeaver, certain configurations and setup processes are required. This section offers a comprehensive guide on initial setup and customization options to tailor the AI integration according to specific preferences.

1. Sign up on the OpenAI platform.

2. Navigate to the API Keys section and generate a new secret key.

3. Insert this key into CloudBeaver’s Engine Settings.

Here is a list of the currently supported models:

• gpt-3.5-turbo (recommended for SQL).
• gpt-3.5-turbo-instruct.
• gpt-4.
• gpt-4-turbo.
• gpt-4o.

• gpt-4o-mini.

1. Sign up on the Azure platform.

2. Navigate to the Azure Portal and create a new AI service under the AI + Machine Learning section.

3. Generate and copy the credentials for the newly created service.

4. Insert these credentials into CloudBeaver’s Engine Settings.

1. Sign up on the Google Cloud Platform.

2. Navigate to the Google Cloud Console and create a new project.

3. Enable the Gemini API for your project by searching for the Gemini API in the marketplace and clicking Enable.

4. Create credentials for your project by navigating to the Credentials page under APIs & Services. Choose Create credentials and select the appropriate type for your Gemini integration.

5. Insert these credentials into CloudBeaver’s Engine Settings.

Ensure that Ollama is already installed and running on a server. You will need the host address where Ollama is installed to proceed.

1. Specify the host address of your Ollama server in the Hostname field, ensuring it follows the format
   http://host:port
   .
2. Insert the Model, Context Size, and Temperature you need for your integration.

For specific requirements or troubleshooting, you might want to adjust some of the following settings:

• Navigate to Settings -> Administration -> AI Settings -> Engine settings to access these settings.

There is also an option to switch the Engine from OpenAI to Azure OpenAI, Gemini and Ollama. These services provide a set of distinct settings:

To interact with databases using the AI Smart completion feature:

1. Launch the SQL Editor.

2. Click on the AI smart completion icon located in the left toolbar of the SQL Editor.

3. Input your natural language request in the AI smart completion window.

4. Click Translate to obtain the SQL query.

Prompts history allows you to review previous prompts in the scope of the session for the chosen tab.

To hide the AI smart completion icon in the SQL Editor:

• Navigate to Administration page -> Server Configuration tab -> Services section.

• Deselect AI option.

When using AI to generate SQL queries, it’s essential to provide clear and specific input. Here’s how to optimize your questions:

• Language: While AI supports multiple languages, it’s recommended to use English for best results.
• Database knowledge: Familiarity with your database structure enhances the accuracy of generated queries.
• Explicit details: If you know certain tables or columns that should be part of the query, include them in your request for better accuracy.

For instance, if you’re using the CloudBeaver sample SQLite database, you might phrase your request as:

Example 1: “List all customers from Italy”

Resulting SQL:

SELECT *

FROM customers

WHERE country = 'Italy';

Example 2: “montre les clients de France”

SELECT *

FROM customer

WHERE country = 'France';

Example 3: “show customers who purchased blues tracks, use joins”

SELECT c.FirstName, c.LastName, t.Name, g.Name

FROM Customer c

         JOIN Invoice i ON c.CustomerId = i.CustomerId

         JOIN InvoiceLine il ON i.InvoiceId = il.InvoiceId

         JOIN Track t ON il.TrackId = t.TrackId

         JOIN Genre g ON t.GenreId = g.GenreId

WHERE g.Name = 'Blues'

ORDER BY c.LastName, c.FirstName;

Example 4: “get names of customers who purchased blues tracks, use joins”

SELECT DISTINCT c.FirstName, c.LastName

FROM Customer c

         JOIN Invoice i ON c.CustomerId = i.CustomerId

         JOIN InvoiceLine il ON i.InvoiceId = il.InvoiceId

         JOIN Track t ON il.TrackId = t.TrackId

         JOIN Genre g ON t.GenreId = g.GenreId

WHERE g.Name = 'Blues';

CloudBeaver – Web Database Manager

• Application overview
• Demo Server
• Administration
  • Server configuration
  • Create Connection
  • Network configuration settings
    • SSH configuration
    • SSL configuration
  • Connection Templates Management
  • Access Management
    • Users
    • Teams
    • Users Provisioning
  • Authentication methods
    • Local Access Authentication
    • Anonymous Access Configuration
    • Reverse proxy header authentication
    • LDAP
    • Single Sign On
    • SAML
    • OpenID
    • AWS OpenID
    • AWS SAML
    • AWS IAM
    • AWS OpenId via Okta
    • Snowflake SSO
    • Okta OpenId
    • Cognito OpenId
    • JWT authentication
    • Kerberos authentication
    • NTLM
    • Microsoft Entra ID authentication
    • Google authentication
  • User credentials storage
  • Cloud Explorer
  • Cloud storage
  • Query Manager
  • Drivers Management
• Supported databases
• Accessibility
• Keyboard shortcuts

• Features

  • Create Connection
  • Database navigator
    • DB Navigator toolbar
    • DB Navigator Settings menu
    • DB Navigator folders
    • Simple and Advanced View
  • Data editor
    • Data Filters
    • Data Ordering
    • Value Panel
    • Grouping Panel
    • Result details Panel
    • Managing Charts
    • JSON and Document View
    • Working with GIS data
  • Data export
  • Data import
  • Entity Diagrams
  • SQL Editor
    • SQL Formatting
    • Query Execution Plan
    • Visual Query Builder
    • AI Smart Assistance
    • Auto and Manual commit modes
  • Log Viewer
  • Query History
  • Resource Manager
  • Session Manager

• Installation
• Version upgrade
• Workspace location

• Workspace backup

• Server configuration
  • Configuring server datasources
  • Initial data configuration
  • Admin password recovery
  • Password policy
  • Query manager database configuration
  • Server database
• CloudBeaver and Nginx
• Domain manager
• Configuring HTTPS for Jetty server
• Product configuration parameters
  • Authentication
  • Theming
  • Localization
  • Database Navigator
  • Data Editor
  • SQL Editor
  • Log Viewer
  • Data Export
  • ERD
  • Connections
• Command line parameters
• Local Preferences

• API

  • Server API explorer
  • API token generation

• Overview
• AWS Settings

• Cloud Explorer

• Overview

• License Management

• CloudBeaver AWS
  • AWS Marketplace
  • Docker image
• CloudBeaver Enterprise
  • Docker image
  • AWS AMI
  • Google Cloud
  • Microsoft Azure
• Deployment options
  • SSL certificate configuration
  • How to connect CloudBeaver to a database on a separate machine in Azure
  • Managing CloudBeaver server on AWS