You can use an Elasticsearch catalog to configure access to Elasticsearch in the following deployments:
Follow these steps to begin creating a catalog for Elasticsearch:
On the Select a data source pane, click the Elasticsearch icon.
The Cloud provider configuration is necessary to allow Starburst Galaxy to correctly match catalogs and clusters.
The data source configured in a catalog, and the cluster must operate in the same cloud provider and region for performance and cost reasons.
The Catalog name is visible in the query editor and other clients. It is used to identify the catalog when writing SQL or showing the catalog and its nested schemas and tables in client applications.
The name is displayed in the query editor, and in the output of a SHOW
CATALOGS command. It is used to fully
qualify the name of any table in SQL queries following the
catalogname.schemaname.tablename syntax. For example, you can run the
following query in the sample cluster without first setting the catalog or
SELECT * FROM tpch.sf1.nation;.
The Description is a short, optional paragraph that provides further details about the catalog. It appears in the Starburst Galaxy user interface and can help other users determine what data can be accessed with the catalog.
The connection to the database requires username and password authentication and details to connect to the database server, typically hostname or IP address and port. The following sections detail the setup for the supported cloud providers.
A connection to the database can be established directly, if the Starburst Galaxy IP range/CIDR is allowed to connect.
If the database is only accessible inside the virtual private cloud (VPC) of the cloud provider, you can use an SSH tunnel with a bastion host in the VPC.
To configure the connection to your Elasticsearch cluster, you must provide details according to your cloud provider.
Provide the following details to connect to your Elasticsearch or OpenSearch cluster with AWS:
Select one of the following authentication methods:
With Password based authentication, provide your username and password.
With Cross account IAM role authentication, provide the endpoint region and the alias for the cross account role.
With AWS access key authentication, provide the endpoint region, AWS access key, and the AWS secret key.
Read External security in AWS to learn about configuring these details in the AWS console.
Provide the following details to connect to your Elasticsearch cluster with Google Cloud or Microsoft Azure:
Once you have configured the connection details, click Test connection to confirm data access is working. If the test is successful, you can save the catalog.
If the test fails, look over your entries in the configuration fields, correct any errors, and try again. If the test continues to fail, Galaxy provides diagnostic information that you can use to fix the data source configuration in the cloud provider system.
Click Connect catalog, and proceed to set permissions where you can grant access to certain roles.
Use the following steps to assign read-only access to a specified set of roles:
You can add your catalog to a cluster later by editing a cluster. Click Skip to proceed to the catalogs page.
Use the following steps to add your catalog to an existing cluster or create a new cluster in the same cloud region:
Click Add to cluster to view your new catalog’s configuration.
The Pending changes to clusters dialog appears when you try to add a catalog to a running cluster.
On the Clusters page, click the Update icon beside the running cluster, to add the catalog.
The catalog provides read access to data and metadata in Elasticsearch. It supports the following features:
Is the information on this page helpful?