|
il y a 4 ans | |
---|---|---|
.. | ||
000-mdradmin-bootstrap | il y a 4 ans | |
001-tfstate | il y a 4 ans | |
004-iam-okta | il y a 4 ans | |
006-account-standards | il y a 4 ans | |
006-account-standards-regional | il y a 4 ans | |
008-xdr-binaries | il y a 4 ans | |
010-shared-ami-key | il y a 4 ans | |
015-security-vpc | il y a 4 ans | |
019-qualys-service-account | il y a 4 ans | |
021-qualys-connector-role | il y a 4 ans | |
072-salt-master-inventory-role | il y a 4 ans | |
disabled | il y a 4 ans | |
README.md | il y a 5 ans | |
account.hcl | il y a 4 ans |
I'm not sure if this is a helpful readme or not tbh
A handful of these need the static access keys for the MDRAdmin account, mostly because at that point of setting up a new AWS account we don't have the okta integration in place.
Subdirectory | auth | Purpose |
---|---|---|
000-mdradmin-bootstrap | MDRAdmin + aws-mfa | Configures MDRAdmin Account to have IAM rights to create terraform state |
001-tfstate | MDRAdmin + aws-mfa | Creates TF state s3 bucket, dynamodb tables |
005-iam | okta + saml2aws | Fundamental IAM setup - does OKTA linkage, sets up user roles and policies |