Windows File Shares That Record Who Opened What
Amazon FSx for Windows File Server joined to AWS Managed Microsoft AD. The provider leaves file and share access auditing disabled and keeps 7 days of backups where the API keeps 30; this module audits both to CloudWatch Logs for a year, keeps 30 days with tags copied, and builds the security group from AWS's port table, with remote PowerShell closed by default.
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-16 · how we verify
Use it from the registry
terraform · opentofumodule "fsx_windows" {
source = "www.iac-bazaar.com/iac-bazaar/aws-fsx-windows/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-fsx-windows
Amazon FSx for Windows File Server. Works with Terraform and OpenTofu
(>= 1.6), aws provider >= 6.0, < 7.0.
Access auditing is off unless you turn it on. The provider leaves both file
access and file share access auditing DISABLED, so nothing records who opened
or connected to what. This module enables both and sends events to a CloudWatch
Logs group under /aws/fsx, kept for a year. File access events still follow
the SACLs on your files and folders: auditing records nothing for data whose
SACLs do not ask for it.
Backups: 30 days, tags copied. AWS's API default is 30 days of automatic backups but the provider's is 7; this module sets 30. Copying tags to backups is on, because changing that setting later replaces the file system. Deleting the file system takes a final backup.
The security group follows AWS's port table. Clients get SMB (TCP 445); remote PowerShell (TCP 5985) is closed unless you name administrator networks; outbound rules open the Active Directory ports AWS lists (DNS, Kerberos, LDAP, RPC and the rest) to the directory's networks, the VPC by default.
AWS Managed Microsoft AD only. Joining a self-managed directory needs a service account password, which would sit in Terraform state.
Some changes replace the file system, which means restoring from a backup:
active_directory_id, deployment_type, storage_type, subnet_ids,
kms_key_arn and additional_security_group_ids. SINGLE_AZ_1 is AWS's
default and has no standby; MULTI_AZ_1 needs a Region with three Availability
Zones.
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-datasync
preserve_deleted_files = REMOVE deletes files at the DESTINATION that are absent from the source, so an unmounted share or a renamed path empties the destination on schedule and the task reports success. PRESERVE here, with verification on, a bandwidth ceiling so it cannot take the whole Direct Connect, and a per-file report of what failed.
aws-s3-bucket
Private S3 bucket with encryption, versioning, public-access block, and TLS-only policy.
aws-backup
A vault, its plans and what they protect, with the service role that can restore as well as back up. Vault Lock is stated rather than defaulted: COMPLIANCE mode cannot be removed by anybody once its window elapses, which is the point and is irreversible.
aws-efs
An EFS file system with mount targets, a least-privilege NFS security group, lifecycle tiering, automatic backups, and a resource policy that enforces encryption in transit.
aws-ebs-volume
Volumes that are always encrypted, optional attachment, and a DLM snapshot schedule in the same module - because a volume with no schedule is one copy of your data on hardware that can fail, and leaving snapshots to somebody else usually means nobody.
aws-fsx-lustre
A Lustre file system with the S3 link, root squash and compression set deliberately. SCRATCH deployments are not replicated - a lost file server loses the data - so this defaults to PERSISTENT_2 and refuses the combinations FSx accepts quietly.