Resource Shares that Stop at the Organization
A share, what is in it and who it reaches. External principals are off, so a mistyped account number is an error rather than a silent share with a stranger - and access ends when an account leaves the organization, which AWS defaults the other way.
Verification
Static-verifiedPassed: 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-12 · how we verify
Use it from the registry
terraform · opentofumodule "ram" {
source = "www.iac-bazaar.com/iac-bazaar/aws-ram/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.
Cite it in your README
badge · attributionPaste this beside the module in the repository that uses it. The badge is rendered from this artifact's verification record, so it reads static-verified because the record says so, and the link lands on this page.
[](https://www.iac-bazaar.com/catalog/aws-ram?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
Terraform module 1.0.0, static-verified on IaC Bazaar: [Resource Shares that Stop at the Organization](https://www.iac-bazaar.com/catalog/aws-ram?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
```hcl
module "ram" {
source = "www.iac-bazaar.com/iac-bazaar/aws-ram/aws"
version = "1.0.0"
}
```Preview:
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-ram
A Resource Access Manager share, what is in it and who it reaches. Works with
Terraform and OpenTofu (>= 1.6), AWS provider >= 6.0, < 7.0.
allow_external_principals shares outside your organization. With it on the
principal list is not checked against accounts you control - any AWS account id
is accepted, so a mistyped account number is a share with a stranger that nobody
is notified about. Off, RAM refuses a principal outside the organization and the
typo becomes an error. Off is the default, and a precondition makes turning it
on an explicit statement.
A share survives an account leaving the organization. That is the AWS
default and it is rarely what anybody means: an account that is spun out, sold
or removed keeps reaching the shared subnet, prefix list or transit gateway
until somebody remembers this share exists. retain_on_leave defaults to
false here, so access ends when membership does.
The permission decides what they can do. Without permission_arns, RAM
applies the default managed permission for each resource type, and for some
types that allows more than "use it". Naming the permission makes it a decision.
Two outputs exist to be asserted on in a policy test rather than read:
reaches_outside_the_organization and survives_account_leaving_org.
The example shares with an OU ARN rather than a list of account ids, because that follows the organization - an account added next month needs no edit.
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
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.
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.
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.
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.
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.
aws-lake-formation
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.