|
2 | 2 |
|
3 | 3 | ## Terraform for AWS plaground |
4 | 4 |
|
| 5 | +The goal of this AWS setup is to have an automated AWS Organization set up that: |
| 6 | + |
| 7 | +1. Is fully compliant with SOC2 |
| 8 | +1. Is fully compliant with AWS, CIS, and NIST security standards. |
| 9 | +1. Has minimal AWS cost overhead |
| 10 | +1. Facilitates easily testing out things in AWS test accounts |
| 11 | + |
| 12 | +### Running locally |
| 13 | + |
5 | 14 | This requires env vars with user credentials that can assume to adminstrator. |
| 15 | +If `aws sts get-caller-identity` works, you are good, otherwise: |
6 | 16 |
|
7 | | -``` |
| 17 | +```bash |
8 | 18 | export AWS_ACCESS_KEY_ID= |
9 | 19 | export AWS_SECRET_ACCESS_KEY= |
10 | 20 | ``` |
11 | 21 |
|
12 | | -Currently only works in tenants/management with `terraform apply`. |
| 22 | +Currently only works in `tenants/management` with `terraform apply`. |
| 23 | + |
| 24 | +Run `prowler` to populate Security Hub with any breaking things it fines by: |
| 25 | +`cd tools/prowler/ && ./install-prowler.sh && ./run-prowler.sh` |
13 | 26 |
|
14 | 27 | ### TODO |
15 | 28 |
|
16 | | -- [] linters and formatters etc |
17 | | -- [] saml2aws for logging in, what to use for IdP? |
18 | | -- [] import everything in root account, test1 account, test2 account |
19 | | -- [] get some securityhub things passing |
20 | | -- [] setup github actions for terraform plan, terraform apply |
21 | | -- [] terraform plugin caching |
22 | | -- [] Setup AWS Config |
23 | | -- [] lots more |
| 29 | +- [ ] linters and formatters etc |
| 30 | +- [ ] saml2aws for logging in, what to use for IdP? |
| 31 | +- [ ] get test1 and test2 accounts working with `terraform apply` |
| 32 | +- [ ] import everything in root account, test1 account, test2 account |
| 33 | +- [ ] get prowler checks to 100% green |
| 34 | +- [ ] setup github actions for terraform plan, terraform apply, prowler |
| 35 | +- [ ] terraform plugin caching |
| 36 | +- [ ] Setup AWS Config |
| 37 | +- [ ] lots more |
0 commit comments