/
Cross AWS Account access policies for LHO deployment
Cross AWS Account access policies for LHO deployment
Terms:
LHO Application Role - a IAM role that is assigned to the EC2 Instance (VM) where the Lakehouse Monitor is deployed, the role allows sts:AssumeRole permission for cross account access or just regular permission policies for resource access.
LHO Agent Role - a IAM role that will be assumed by the Databricks Workspace Instance Profile Roles enabled for the Databricks workloads monitored by LHO.
LHO VM host AWS Account - AWS account where the LHO app (VM) is deployed and where DynamoDB and SQS artifacts are also created.
Databricks Workspace AWS account - AWS accounts hosting Databricks workspaces
Databricks costs
Cloud Costs via AWS CostExplorer
DynamoDB and SQS
Related content
Single AWS Account access policies for LHO
Single AWS Account access policies for LHO
More like this
DynamoDB and SQS
DynamoDB and SQS
More like this
Deploy Lakehouse Optimizer on Client Provided Resources in AWS
Deploy Lakehouse Optimizer on Client Provided Resources in AWS
Read with this
Permissions Required to Complete Deployment in AWS
Permissions Required to Complete Deployment in AWS
Read with this
AWS Deployment Diagram
AWS Deployment Diagram
Read with this
Deployment and Quick Setup Guide: AWS
Deployment and Quick Setup Guide: AWS
Read with this