|
| 1 | +# AWS Backup Global Settings Example |
| 2 | + |
| 3 | +This example demonstrates how to configure AWS Backup global settings for centralized cross-account backup governance. |
| 4 | + |
| 5 | +## Features Demonstrated |
| 6 | + |
| 7 | +- **Global Settings Management**: Enable and configure AWS Backup global settings |
| 8 | +- **Cross-Account Backup**: Enable centralized backup governance across multiple AWS accounts |
| 9 | +- **Enterprise Governance**: Account-level settings for backup operations |
| 10 | +- **Backup Configuration**: Basic vault, plan, and selection setup with global settings |
| 11 | + |
| 12 | +## Architecture |
| 13 | + |
| 14 | +``` |
| 15 | +AWS Account (Management/Central) |
| 16 | +├── Global Settings (Account-level) |
| 17 | +│ └── isCrossAccountBackupEnabled: true |
| 18 | +├── Backup Vault |
| 19 | +├── Backup Plan |
| 20 | +└── Resource Selections |
| 21 | +``` |
| 22 | + |
| 23 | +## Usage |
| 24 | + |
| 25 | +To run this example you need to execute: |
| 26 | + |
| 27 | +```bash |
| 28 | +$ terraform init |
| 29 | +$ terraform plan |
| 30 | +$ terraform apply |
| 31 | +``` |
| 32 | + |
| 33 | +Note that this example will create resources which may cost money. Run `terraform destroy` when you don't need these resources. |
| 34 | + |
| 35 | +## Requirements |
| 36 | + |
| 37 | +| Name | Version | |
| 38 | +|------|---------| |
| 39 | +| <a name="requirement_terraform"></a> [terraform](#requirement\_terraform) | >= 1.0 | |
| 40 | +| <a name="requirement_aws"></a> [aws](#requirement\_aws) | >= 5.0 | |
| 41 | + |
| 42 | +## Providers |
| 43 | + |
| 44 | +| Name | Version | |
| 45 | +|------|---------| |
| 46 | +| <a name="provider_aws"></a> [aws](#provider\_aws) | >= 5.0 | |
| 47 | + |
| 48 | +## Modules |
| 49 | + |
| 50 | +| Name | Source | Version | |
| 51 | +|------|--------|---------| |
| 52 | +| <a name="module_aws_backup_global_settings"></a> [aws\_backup\_global\_settings](#module\_aws\_backup\_global\_settings) | ../.. | n/a | |
| 53 | + |
| 54 | +## Resources |
| 55 | + |
| 56 | +Created by the module: |
| 57 | +- `aws_backup_global_settings` - Account-level backup settings |
| 58 | +- `aws_backup_vault` - Backup vault for storing recovery points |
| 59 | +- `aws_backup_plan` - Backup plan with scheduling and lifecycle policies |
| 60 | +- `aws_backup_selection` - Resource selection for automated backups |
| 61 | + |
| 62 | +## Inputs |
| 63 | + |
| 64 | +| Name | Description | Type | Default | Required | |
| 65 | +|------|-------------|------|---------|:--------:| |
| 66 | +| <a name="input_backup_retention_days"></a> [backup\_retention\_days](#input\_backup\_retention\_days) | Number of days to retain backups | `number` | `30` | no | |
| 67 | +| <a name="input_backup_schedule"></a> [backup\_schedule](#input\_backup\_schedule) | Cron expression for backup schedule | `string` | `"cron(0 2 * * ? *)"` | no | |
| 68 | +| <a name="input_enable_cross_account_backup"></a> [enable\_cross\_account\_backup](#input\_enable\_cross\_account\_backup) | Enable cross-account backup functionality | `bool` | `true` | no | |
| 69 | +| <a name="input_tags"></a> [tags](#input\_tags) | A mapping of tags to assign to resources | `map(string)` | `{"BackupGovernance": "centralized", "Environment": "production", "Owner": "backup-team", "Terraform": true}` | no | |
| 70 | +| <a name="input_vault_name"></a> [vault\_name](#input\_vault\_name) | Name of the backup vault to create | `string` | `"centralized-backup-vault"` | no | |
| 71 | + |
| 72 | +## Outputs |
| 73 | + |
| 74 | +| Name | Description | |
| 75 | +|------|-------------| |
| 76 | +| <a name="output_cross_account_backup_enabled"></a> [cross\_account\_backup\_enabled](#output\_cross\_account\_backup\_enabled) | Whether cross-account backup is enabled | |
| 77 | +| <a name="output_global_settings"></a> [global\_settings](#output\_global\_settings) | Configured global settings | |
| 78 | +| <a name="output_global_settings_id"></a> [global\_settings\_id](#output\_global\_settings\_id) | AWS Account ID where global settings are applied | |
| 79 | +| <a name="output_global_settings_summary"></a> [global\_settings\_summary](#output\_global\_settings\_summary) | Summary of global settings configuration | |
| 80 | +| <a name="output_plan_arn"></a> [plan\_arn](#output\_plan\_arn) | ARN of the backup plan | |
| 81 | +| <a name="output_vault_arn"></a> [vault\_arn](#output\_vault\_arn) | ARN of the backup vault | |
| 82 | + |
| 83 | +## Global Settings Configuration |
| 84 | + |
| 85 | +### Cross-Account Backup Enablement |
| 86 | + |
| 87 | +When `isCrossAccountBackupEnabled` is set to `"true"`: |
| 88 | + |
| 89 | +1. **Centralized Governance**: Enables centralized backup management across AWS accounts |
| 90 | +2. **Organization Policies**: Allows AWS Organizations backup policies to be applied |
| 91 | +3. **Cross-Account IAM**: Enables backup operations across account boundaries |
| 92 | +4. **Compliance**: Supports enterprise compliance frameworks requiring centralized backup |
| 93 | + |
| 94 | +### Enterprise Use Cases |
| 95 | + |
| 96 | +- **Multi-Account Organizations**: Centralized backup governance for AWS Organizations |
| 97 | +- **Compliance Requirements**: Meeting regulatory requirements for backup management |
| 98 | +- **Security**: Controlled cross-account backup operations |
| 99 | +- **Cost Optimization**: Centralized backup strategies and policies |
| 100 | + |
| 101 | +## Next Steps |
| 102 | + |
| 103 | +After deploying this example: |
| 104 | + |
| 105 | +1. **Configure AWS Organizations Backup Policies** for centralized governance |
| 106 | +2. **Set up cross-account IAM roles** for backup operations |
| 107 | +3. **Implement backup compliance frameworks** across accounts |
| 108 | +4. **Monitor backup activities** through AWS CloudTrail and CloudWatch |
| 109 | + |
| 110 | +## Important Notes |
| 111 | + |
| 112 | +- Global settings are **account-level** configurations (one per AWS account) |
| 113 | +- Cross-account backup requires proper **IAM permissions** across accounts |
| 114 | +- This feature is particularly valuable for **enterprise environments** |
| 115 | +- Consider **AWS Organizations integration** for complete centralized governance |
| 116 | + |
| 117 | +## Compliance and Security |
| 118 | + |
| 119 | +This configuration supports: |
| 120 | +- SOC 2 compliance for backup governance |
| 121 | +- GDPR requirements for data retention |
| 122 | +- HIPAA backup and recovery standards |
| 123 | +- Financial services backup regulations |
0 commit comments