Skip to content

Latest commit

 

History

History
42 lines (29 loc) · 2.51 KB

aws_crossaccount_policy.md

File metadata and controls

42 lines (29 loc) · 2.51 KB
Raw
subcategory
Deployment

databricks_aws_crossaccount_policy Data Source

-> Note This data source can only be used with an account-level provider!

This data source constructs necessary AWS cross-account policy for you, which is based on official documentation.

Example Usage

For more detailed usage please see databricks_aws_assume_role_policy or databricks_aws_s3_mount pages.

data "databricks_aws_crossaccount_policy" "this" {}

Argument Reference

  • policy_type (Optional) The type of cross account policy to generated: managed for Databricks-managed VPC and customer for customer-managed VPC, restricted for customer-managed VPC with policy restrictions
  • pass_roles (Optional) (List) List of Data IAM role ARNs that are explicitly granted iam:PassRole action. The below arguments are only valid for restricted policy type
  • aws_account_id — Your AWS account ID, which is a number.
  • aws_partition - (Optional) AWS partition. The options are aws or aws-us-gov. Defaults to aws
  • vpc_id — ID of the AWS VPC where you want to launch workspaces.
  • region — AWS Region name for your VPC deployment, for example us-west-2.
  • security_group_id — ID of your AWS security group. When you add a security group restriction, you cannot reuse the cross-account IAM role or reference a credentials ID (credentials_id) for any other workspaces. For those other workspaces, you must create separate roles, policies, and credentials objects.

Attribute Reference

In addition to all arguments above, the following attributes are exported:

  • json - AWS IAM Policy JSON document

Related Resources

The following resources are used in the same context: