You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|<a name="input_automation_account_service_role_name"></a> [automation\_account\_service\_role\_name](#input\_automation\_account\_service\_role\_name) | Name of the custom role in the automation account. See https://docs.meshcloud.io/docs/meshstack.how-to.integrate-meshplatform-aws-manually.html#set-up-aws-account-3-automation | `string` | `"MeshfedAutomationRole"` | no |
198
198
|<a name="input_aws_sso_instance_arn"></a> [aws\_sso\_instance\_arn](#input\_aws\_sso\_instance\_arn) | AWS SSO Instance ARN. Needs to be of the form arn:aws:sso:::instance/ssoins-xxxxxxxxxxxxxxx. Setup instructions https://docs.meshcloud.io/docs/meshstack.aws.sso-setup.html. | `string` | n/a | yes |
199
+
|<a name="input_can_close_accounts_in_resource_org_paths"></a> [can\_close\_accounts\_in\_resource\_org\_paths](#input\_can\_close\_accounts\_in\_resource\_org\_paths) | AWS ResourceOrgPaths that are used in Landing Zones and where meshStack is allowed to close accounts. | `list(string)` | `[]` | no |
199
200
|<a name="input_control_tower_enrollment_enabled"></a> [control\_tower\_enrollment\_enabled](#input\_control\_tower\_enrollment\_enabled) | Set to true, to allow meshStack to enroll Accounts via AWS Control Tower for the meshPlatform. | `bool` | `false` | no |
200
201
|<a name="input_control_tower_portfolio_id"></a> [control\_tower\_portfolio\_id](#input\_control\_tower\_portfolio\_id) | Must be set for AWS Control Tower | `string` | `""` | no |
201
202
|<a name="input_cost_explorer_management_account_service_role_name"></a> [cost\_explorer\_management\_account\_service\_role\_name](#input\_cost\_explorer\_management\_account\_service\_role\_name) | Name of the custom role in the management account used by the cost explorer user. | `string` | `"MeshCostExplorerServiceRole"` | no |
@@ -214,6 +215,7 @@ Before opening a Pull Request, we recommend following the below steps to get a f
214
215
| Name | Description |
215
216
|------|-------------|
216
217
|<a name="output_automation_account_id"></a> [automation\_account\_id](#output\_automation\_account\_id) | Automation Account ID |
|<a name="output_cost_explorer_management_account_role_arn"></a> [cost\_explorer\_management\_account\_role\_arn](#output\_cost\_explorer\_management\_account\_role\_arn) | Amazon Resource Name (ARN) of Management Account Role for replicator |
218
220
|<a name="output_cost_explorer_privileged_external_id"></a> [cost\_explorer\_privileged\_external\_id](#output\_cost\_explorer\_privileged\_external\_id) | Cost explorer privileged\_external\_id |
219
221
|<a name="output_management_account_id"></a> [management\_account\_id](#output\_management\_account\_id) | Management Account ID |
| <aname="input_allow_federated_role"></a> [allow\_federated\_role](#input\_allow\_federated\_role)| n/a |`bool`|`false`| no |
41
41
| <aname="input_aws_sso_instance_arn"></a> [aws\_sso\_instance\_arn](#input\_aws\_sso\_instance\_arn)| ARN of the AWS SSO instance to use |`string`| n/a | yes |
42
+
| <aname="input_can_close_accounts_in_resource_org_paths"></a> [can\_close\_accounts\_in\_resource\_org\_paths](#input\_can\_close\_accounts\_in\_resource\_org\_paths)| AWS ResourceOrgPaths that are used in Landing Zones and where meshStack is allowed to close accounts. |`list(string)`|`[]`| no |
42
43
| <aname="input_control_tower_enrollment_enabled"></a> [control\_tower\_enrollment\_enabled](#input\_control\_tower\_enrollment\_enabled)| Set to true, to allow meshStack to enroll Accounts via AWS Control Tower for the meshPlatform |`bool`|`false`| no |
43
44
| <aname="input_control_tower_portfolio_id"></a> [control\_tower\_portfolio\_id](#input\_control\_tower\_portfolio\_id)| Must be set for AWS Control Tower |`string`|`""`| no |
44
-
| <aname="input_landing_zone_ou_arns"></a> [landing\_zone\_ou\_arns](#input\_landing\_zone\_ou\_arns)| Organizational Unit ARNs that are used in Landing Zones. We recommend to explicitly list the OU ARNs that meshStack should manage. |`list(string)`|<pre>[<br> "arn:aws:organizations::*:ou/o-*/ou-*"<br>]</pre>| no |
45
+
| <aname="input_landing_zone_ou_arns"></a> [landing\_zone\_ou\_arns](#input\_landing\_zone\_ou\_arns)| Organizational Unit ARNs that are used in Landing Zones. We recommend to explicitly list the OU ARNs that meshStack should manage. |`list(string)`|`[]`| no |
45
46
| <aname="input_management_account_service_role_name"></a> [management\_account\_service\_role\_name](#input\_management\_account\_service\_role\_name)| Name of the custom role in the management account. See https://docs.meshcloud.io/docs/meshstack.how-to.integrate-meshplatform-aws-manually.html#set-up-aws-account-2-management|`string`|`"MeshfedServiceRole"`| no |
46
47
| <aname="input_meshcloud_account_id"></a> [meshcloud\_account\_id](#input\_meshcloud\_account\_id)| The ID of the meshcloud AWS Account |`string`| n/a | yes |
47
48
| <aname="input_meshcloud_account_service_user_name"></a> [meshcloud\_account\_service\_user\_name](#input\_meshcloud\_account\_service\_user\_name)| Name of the meshfed-service user. This user is responsible for replication. |`string`|`"meshfed-service-user"`| no |
@@ -55,4 +56,4 @@ No modules.
55
56
|------|-------------|
56
57
| <aname="output_management_account_role_arn"></a> [management\_account\_role\_arn](#output\_management\_account\_role\_arn)| Amazon Resource Name (ARN) of Management Account Role |
57
58
| <aname="output_meshstack_access_role_name"></a> [meshstack\_access\_role\_name](#output\_meshstack\_access\_role\_name)| The name for the Account Access Role that will be rolled out to all managed accounts. |
0 commit comments