AWS Deployment Diagram
Below is the deployment diagram for the Lakehouse Optimizer security flow when using AWS.
AWS components of an LHO deployment
AWS components created at deployment time by the deployment script:
AWS EC2 VM - hosting the LHO application, a docker-compose/docker image/container
AWS RDS for SQL Server - storing the LHO analyzed data, cost, recommendations etc
AWS DynamoDB - storing telemetry data from each monitored Databricks workspace
AWS SQS - DBX event notifications used for real-time analysis of Dbx workloads
AWS VPC - network configuration for the LHO EC2 VM and the RDS for SQL Server
AWS Secrets Manager - LHO stores all sensitive keys and secrets (SQL Server password, IAM user access key/secret key, Dbx Service Principal Oauth Secret, encryption private keys, license token etc)
IAM Role - instance profile that allows the EC2 VM access to its services (Secrets Manager, DynamoDB, SQS, AWS Cost Explorer, Dbx Billable Usage Logs)
AWS S3 - deployment Terraform backups
Optional components controlled by a script parameter (providedDnsUrl)
Elastic IP - used for accessing the VM from the Internet
Route53 registered domain using the above Elastic IP
AWS components created by the customer:
IAM User Access Key/Secret Key with permissions and trust policies for cross-AWS access
AWS Cost Explorer tag activation
Databricks Service Principal with OAuth secret
App Registration for Single Sign-On: Okta, Microsoft Entra ID (Azure AD), Google Cloud Console
Route53 hosted zone (not required if providedDnsUrl is set)