📝 docs(README.md): update alb_config and fleet_config tables to reflect
new changes
🔧 fix(main.tf): add preferred_maintenance_window to rds module to allow
for scheduled maintenance
🔧 fix(variables.tf): add preferred_maintenance_window to rds_config
variable to allow for scheduled maintenance
🔧 fix(README.md): update fleet_config image version to v4.47.1 for
latest features and bug fixes
@pacamaster and I reviewed the example directory and found that the
example terraform was a bit bloated. This streamlines the example to be
a bare-bones minimum to get started.
This PR adds support for a new terraform module that will make it easy
to configure Fleet instances for S3 backend for file carving results.
Its intended to be applied in two phases.
1) apply target-account which will provision the s3 bucket, IAM role and
policy permissions
2) apply carve on the fleet instance, bootstrapping environment
variables for Fleet server & attaching the IAM policy.
# Checklist for submitter
- [X] Manual QA for all new/changed functionality
Since this was missing on the outputs, it broke apple mdm secret
population in existing implementations. This should re-assert backwards
compatibility.
These items fix the github action for use with the updates to the
monitoring module.
Additionally there were some changes needed to the monitoring module to
make it behave inside the GH action.
Once this is approved/merged, the new tag for them monitoring module
will be created as `tf-mod-addon-monitoring-v1.1.1`
# Checklist for submitter
- [X] Documented any API changes (docs/REST API/rest-api.md or
docs/Contributing/API-for-contributors.md)
- [X] Manual QA for all new/changed functionality
🔧 refactor(byo-vpc/main.tf): replace hardcoded cidr_blocks value with
dynamic data from aws_subnet.redis to ensure the CIDR blocks are always
up-to-date and accurate
