AWS whitepapers documentation change
Summary
Removed redundant bullet points about reasons for multiple organizations, standardized 'AWS Organization' capitalization, updated quota increase link, corrected product names, and fixed punctuation.
Security assessment
Changes focus on formatting, terminology consistency, and link updates. No explicit security vulnerabilities, mitigations, or new security features are introduced. The mention of data separation by classification levels remains unchanged in intent.
Diff
diff --git a/whitepapers/latest/organizing-your-aws-environment/multiple-organizations.md b/whitepapers/latest/organizing-your-aws-environment/multiple-organizations.md index ff12947f9..198ef3cbb 100644 --- a//whitepapers/latest/organizing-your-aws-environment/multiple-organizations.md +++ b//whitepapers/latest/organizing-your-aws-environment/multiple-organizations.md @@ -13,11 +12,0 @@ There are certain exceptions, outlined in this section, where you might need to - * Support acquisitions and divestments - - * Support large AWS environments - - * Align with your billing requirements - - * Different classification levels for government applications - - - - @@ -26 +15 @@ There are certain exceptions, outlined in this section, where you might need to -It is recommended to develop infrastructure as code that interacts with APIs and other mechanisms fundamental to the management of your AWS organization. In these cases, to determine whether your changes break something without having to make the changes in your production organization, we recommend that you test your changes in an organization different from the one running your production workloads. +It is recommended to develop infrastructure as code that interacts with APIs and other mechanisms fundamental to the management of your AWS Organization. In these cases, to determine whether your changes break something without having to make the changes in your production organization, we recommend that you test your changes in an organization different from the one running your production workloads. @@ -30 +19 @@ For example, you might need to either modify the automation that creates new acc -In these circumstances, we recommend that you establish an additional AWS organization for testing that closely resembles your production organization. You can perform testing of changes to how you manage your organization in your test organization before applying those changes to be applied to your production organization. +In these circumstances, we recommend that you establish an additional AWS Organization for testing that closely resembles your production organization. You can perform testing of changes to how you manage your organization in your test organization before applying those changes to be applied to your production organization. @@ -34 +23 @@ In these circumstances, we recommend that you establish an additional AWS organi -You might acquire an entity that has already established an organization. If you decide to merge the acquired entity’s AWS environment with your AWS environment, you can move member accounts from the acquired organization to your mainstream organization. In this case, you can later decommission the acquired entity’s organization. +You might acquire an entity that has already established an organization. If you decide to merge the acquired entity's AWS environment with your AWS environment, you can move member accounts from the acquired organization to your mainstream organization. In this case, you can later decommission the acquired entity's organization. @@ -40 +29 @@ If you plan to potentially divest a portion of your portfolio, you can manage th -You can request a quota increase if your organization reaches its maximum account limit. Support can help expand your organization’s capacity beyond the default number of accounts. For more details about the maximum number of accounts supported in an organization, refer to [Quotas for AWS Organizations](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_reference_limits.html). +You can request a [quota increase](https://docs.aws.amazon.com/servicequotas/latest/userguide/request-quota-increase.html) if your AWS Organization reaches its maximum account limit. Support can help expand your organization's capacity beyond the default number of accounts. For more details about the maximum number of accounts supported in an organization, refer to [Quotas for AWS Organizations.](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_reference_limits.html) @@ -44 +33 @@ You can request a quota increase if your organization reaches its maximum accoun -An organization gathers billing information from all member accounts into a single consolidated AWS bill. If you have use cases where different sets of accounts require distinct bills or payments, then multiple organizations might be required. Ensure you have reviewed AWS Billing Conductor and billing and management credit sharing options for your AWS accounts to understand the configurations that are supported within a single organization. +An organization gathers billing information from all member accounts into a single consolidated AWS bill. If you have use cases where different sets of accounts require distinct bills or payments, then multiple organizations might be required. Ensure you have reviewed AWS Billing and Cost Management Conductor and Billing and Management Credit sharing options for your AWS accounts to understand the configurations that are supported within a single AWS Organization. @@ -50 +39 @@ Some customers in government, critical national infrastructure providers, and de -As noted in this section, an organization itself contains collective data from multiple accounts. Data such as account names, billing data, organizational unit names, and activity logs can be accessed centrally for those with appropriate permissions, such as a cloud administrator or audit team. This means that commingling of billing and logging data from accounts that are processing data might not meet a customer’s requirements for separation by classification levels. +As noted in this section, an organization itself contains collective data from multiple accounts. Data such as account names, billing data, organizational unit names, and activity logs can be accessed centrally for those with appropriate permissions, such as a cloud administrator or audit team. This means that commingling of billing and logging data from accounts that are processing data might not meet a customer's requirements for separation by classification levels.