Big Data Virtualization AMI Launch Guide

MDACA Big Data Virtualization AMI Launch Guide

1. Upon launching the AMI several scripts will run to configure the instance. By default, it is setup to listen on port 80 for BDV, port 6080 for policy manager, and port 8080 for the identity provider (Keycloak) using the public DNS hostname provided by AWS:

2. The instance ID will be the default password for both your keyadmin and madmin default accounts. Both should be reset to unique values. When browsing to the public DNS, you will be presented with the MDACA login page:

3. You can login with madmin as your username and the instance ID as your password. The madmin has access to all of the catalogs and policy manager. It can be used to configure your users, groups, authorization policies, data masking and row filtering. For more information on BDV administration, please visit our guide: BDV Documentation

User Management

User management can be performed through Keycloak by logging in to http://public-hostname:8080/auth using keyadmin and your instance ID as your password. Keycloak can be federated with an existing enterprise IdP, synced with LDAP, and utilize Kerberos authentication. For more information please see the Keycloak documentation here: https://www.keycloak.org/documentation

Policy Management

You can login with madmin as your username and the instance ID as your password to access policy manager. It is accessible on port 6080. Within policy manager, you can restrict access to catalogs, schemas, tables, and columns. You can also apply data masking policies and row level filtering.

Connecting with JDBC

The JDBC driver is in the following location:

/opt/mdaca/trino-jdbc-372-mdaca-3.jar

It can be used to connect from any JDBC compliant IDE or application. You will want to specify externalAuthentication=true in your JDBC connection URL.

Additional drivers, such as ODBC, are available. Please contact us for more info.

Updating the Hostname

By default, the application is setup to utilize the public DNS provided by AWS. If you would like to use an alternative hostname, you can run the following scripts:

/opt/mdaca/scripts/set-hostname.sh new-hostname

/opt/mdaca/scripts/update-config.sh

Example:

/opt/mdaca/scripts/set-hostname.sh cse.mdaca.io

/opt/mdaca/scripts/update-config.sh

SSL/TLS Configuration

By default, the application is setup to listen on ports 80 and 8080. It can be setup to utilize TLS and ports 443 (BDV), 6182 (Policy Manager) and 8443 (Keycloak) instead. The following files need to be updated with your certificates:

tls.key	Private key of your certificate
tls.crt	Public key of your certificate
server.p12	Public and private key in PKCS12 format
ca.crt	Public key of your certificate authority
server.truststore	Java keystore (JKS) containing the public keys of your CA and your certificate

You will then need to run the following scripts:

/opt/mdaca/scripts/set-hostname.sh new-hostname

/opt/mdaca/scripts/set-tls.sh true

/opt/mdaca/scripts/update-config.sh

Example:

/opt/mdaca/scripts/set-hostname.sh cse.mdaca.io

/opt/mdaca/scripts/set-tls.sh true

/opt/mdaca/scripts/update-config.sh

MDACA Big Data Virtualization AMI Launch Guide

User Management

Policy Management

Connecting with JDBC

Updating the Hostname

SSL/TLS Configuration

You will then need to run the following scripts:

Certifications

Follow Us

About Us

Contracts