Matthew Clark
10/23/2024, 6:21 PMorganization_enabled to false in accounts component in catalog stack. If we set this to false, it runs - we then just renamed the existing management account to core-root. Is core-root referencing the management account, or is there an expectation that core-root is another separate account? Once we get past that - the OUs/accounts exist, but when we apply account-settings it's implying the the account_name doesn't exist in local.account_org_role_arns. In your experience, is this likely an issue with what I mention above re: organizations, something running in the wrong workspace and by proxy not having access to the intended tfstate, or something else?
This error is occurring in the account-map IAM roles module which is pulling from full account map from account map module.
full_account_map = {
"core-artifacts" = "<REDACTED>"
"core-audit" = "<REDACTED>"
"core-dns" = "<REDACTED>"
"core-identity" = "<REDACTED>"
"core-root" = "<REDACTED>"
}
How would we go about debugging this? Still working our way around atmos, heh.Erik Osterman (Cloud Posse)
10/23/2024, 7:02 PMMatthew Clark
10/23/2024, 7:02 PMErik Osterman (Cloud Posse)
10/23/2024, 7:04 PMDan Miller (Cloud Posse)
10/23/2024, 7:09 PMaccount component on initial creation, you may need to import the existing organization into Terraform if it was manually created alreadyDan Miller (Cloud Posse)
10/23/2024, 7:09 PMDan Miller (Cloud Posse)
10/23/2024, 7:10 PMDan Miller (Cloud Posse)
10/23/2024, 7:10 PMaws organizations describe-organization
atmos terraform import account --stack core-gbl-root 'aws_organizations_organization.this[0]' 'o-7qcakq6zxw'Matthew Clark
10/23/2024, 9:05 PMBen Smith (Cloud Posse)
10/23/2024, 9:06 PM