AWSStatic-verified

Data Lake Permissions That Are Actually in Effect

AWS Lake Formation with its own permissions switched on for new databases and tables: admins, registered S3 locations and explicit grants. AWS ships it in IAM-only mode, and its settings resource clears any admin it is not given, so admins are required and the settings are protected from destroy. Existing databases keep IAM-only access until revoked outside Terraform, and it says so.

terraformAWSaws
aws-lake-formationvizier v1.2.0

Verification

Static-verified

Passed: validated and lint-clean (provider-schema-validated for AWS/Azure/GCP; Terraform-language lint elsewhere).

Conformance

  • Static validation (fmt · validate · tflint)
  • Security scan clean (Checkov)
  • Plan tests (mocked: validation rules · outputs)

Provenance

  • SHA-256 checksum
  • Signature (pending)

Functional

  • Live test pending (no cloud run yet)

Last verified 2026-09-16 · how we verify

Use it from the registry

terraform · opentofu
module "lake_formation" {
  source  = "www.iac-bazaar.com/iac-bazaar/aws-lake-formation/aws"
  version = "1.0.0"
}

Needs a registry token from /account/tokens. The module itself is free; the account is what identifies you. Full setup: registry docs.

Inputs & outputs

Create a free account to read this module's contract

The declared contract - every input name, type, default and description, plus every output - is shown to signed-in accounts, not to anonymous visitors.

A free account sees the contract of every module in the catalogue. There is no subscription and nothing to buy - the modules are free to download, and they run under Vizier.

Documentation

aws-lake-formation

Data lake permissions that take effect on AWS Lake Formation. Works with Terraform and OpenTofu (>= 1.6), aws provider >= 6.0, < 7.0.

Out of the box, Lake Formation permissions do nothing. AWS grants Super to IAMAllowedPrincipals on existing catalog resources and uses IAM-only control for new ones. This module moves NEW databases and tables to Lake Formation control; existing ones keep their IAMAllowedPrincipals grant until revoked in the console or CLI, and existing_resources_changed says false.

The settings resource clears what it is not given, so admins and cross_account_version are required.

Destroying the settings removes every admin. They are protected from destroy; stop managing them with tofu state rm.

Grants to admins or to IAMAllowedPrincipals are refused: admins hold implicit permissions, and the provider warns that mixing IAMAllowedPrincipals with individual grants gives unexpected results.

A location registered with a role stays with a role: AWS does not support switching it to the service-linked role later.

Verification

Static validation runs tofu fmt, init, validate, tflint and checkov. This module has not yet had a live test, so it is published as statically validated with its live test pending and does not carry the live-tested mark.

Usage code & full reference need an account

The complete copy-paste usage, the full input/output reference, and operational notes are free with an account - shown here and bundled in the download. Sign in and this section fills in.

  • Usage

Related modules

Static validatedLive test pending

aws-verified-permissions

validation_settings.mode defaults to OFF, so a Cedar policy naming an action the schema does not define is accepted and then never matches. A broken permit fails closed and somebody complains; a broken forbid fails OPEN and nobody does. STRICT here, with the schema that makes it possible.

View module
Static validatedLive test pending

aws-rolesanywhere

Any certificate chaining to the trust anchor can exchange itself for AWS credentials, so the CA is the perimeter - and it is usually run by people who were never told. The profile carries the scope, sessions are narrowed below the role, the caller cannot name itself in CloudTrail, and CA expiry warns before every workload loses credentials at once.

View module
Static validatedLive test pending

aws-signer

Signing profiles for Lambda packages and container images, plus the code signing configuration that enforces them. Defaults to Enforce rather than the API default Warn, which logs an untrusted artifact and deploys it anyway.

View module
Live-tested

aws-cognito

A secure-by-default Cognito user pool and app client with optional hosted-UI domain - strong password policy, TOTP MFA, account-enumeration protection, SRP-only flows, and refresh-token revocation.

View module
Static validatedLive test pending

aws-conformance-packs

AWS Config conformance packs for one account or a whole organisation, with a ten-rule baseline of AWS managed rules taken from AWS's CIS sample pack. AWS Audit Manager no longer takes new customers and points them here. The module says a pack evaluates nothing without a configuration recorder and that Terraform cannot detect a pack edited in the console.

View module
Static validatedLive test pending

aws-detective

Builds an investigable graph from CloudTrail, VPC flow logs and GuardDuty findings, with member accounts and organization delegation. It detects nothing itself - it makes an existing finding into a timeline.

View module