https://github.com/grendel-consulting/cloud-factory-customisations

Account-specific customisations used in the Account Factory for Terraform
https://github.com/grendel-consulting/cloud-factory-customisations

aft aws control-tower

Last synced: about 2 months ago
JSON representation

Account-specific customisations used in the Account Factory for Terraform

• Host: GitHub
• URL: https://github.com/grendel-consulting/cloud-factory-customisations
• Owner: grendel-consulting
• License: mit
• Created: 2023-04-07T09:27:29.000Z (almost 2 years ago)
• Default Branch: main
• Last Pushed: 2024-10-23T22:29:56.000Z (3 months ago)
• Last Synced: 2024-10-24T11:36:02.123Z (2 months ago)
• Topics: aft, aws, control-tower
• Language: HCL
• Homepage:
• Size: 759 KB
• Stars: 0
• Watchers: 3
• Forks: 0
• Open Issues: 1
• Metadata Files:
  • Readme: README.md
  • Contributing: .github/CONTRIBUTING.md
  • License: LICENSE
  • Codeowners: .github/CODEOWNERS
  • Security: .github/SECURITY.md
  • Support: .github/SUPPORT.md

Awesome Lists containing this project

README

        
# Cloud Factory (Account) Customisations

[![OpenSSF Scorecard](https://api.scorecard.dev/projects/github.com/grendel-consulting/cloud-factory-customisations/badge)](https://scorecard.dev/viewer/?uri=github.com/grendel-consulting/cloud-factory-customisations)

Definitions for use with the Account Factory for Terraform (AFT) framework. Account Customizations are used to customize **specific** provisioned accounts with customer defined resources. The resources can be created through Terraform or through Python, leveraging the API helpers. The customization run is parameterized at runtime.

## Usage

Start by using the the ACCOUNT_TEMPLATE, copying into a new folder. It's name should match the `account_customizations_name` provided in the account request for the account(s) being configured in this way.

### Terraform

You can see AFT-provided Jinja templates for the Terraform backend and providers. These are rendered at the time the Terraform is applied. Further providers can be defined by creating a `providers.tf` file, as needed.

Define your own Terraform resources, placing `.tf` files in the 'terraform' directory or as submodules to it.

### API Helpers

Define any scripts that need to run before/after Terraform using the bash entry points. You can extend these to run Python scripts or to perform other actions, such as leveraging the AWS CLI.

Within the `api_helpers/python` folder is a requirements.txt, where you can specify packages to be installed via PIP.

## Deployment

Deployment must presently be triggered manually, on a per-OU or per-Account basis - or across the whole AWS Organization - through [re-invoking an AWS Step Function](https://docs.aws.amazon.com/controltower/latest/userguide/aft-account-customization-options.html#aft-re-invoke-customizations) in the factory management OU.

## Further Reading

See: [AFT Account Customizations](https://github.com/aws-ia/terraform-aws-control_tower_account_factory/tree/main/sources/aft-customizations-repos/aft-account-customizations)