> ## Documentation Index
> Fetch the complete documentation index at: https://cloudanix.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Enable All AWS Organization Features

### More Info:

Ensure that All Features is enabled within your Amazon Organizations to achieve full control over the use of AWS services and actions across multiple AWS accounts using Service Control Policies (SCPs). An SCP is a type of organization control policy that can be used to restrict what users and even administrators can do in affected AWS accounts. For example, the master account from an organization can apply SCPs that can prevent member accounts from leaving the organization. A Service Control Policy is similar to an IAM access policy except the SCP does not grant any access permissions but instead it acts like a filter that allows only the specified services and actions to be used within the organization. SCPs make use of whitelisting and blacklisting methods to filter the permissions that are available to member accounts. When whitelisting is used, you can explicitly specify the access that is allowed and all other access is implicitly blocked. When blacklisting is used, you can explicitly specify the access that is not allowed and all other access is granted

### Risk Level

Medium

### Address

Security

### Compliance Standards

* APRA CPS 234 (Australia)
* BSI C5 (Germany)
* Brazil LGPD
* CCPA / CPRA (California)
* CIS Critical Security Controls v8
* CMMC 2.0
* CSA Cloud Controls Matrix v4
* Cloudanix Best Practice
* DPDPA
* Digital Operational Resilience Act (EU)
* Essential 8
* ISO/IEC 27017
* ISO/IEC 27018
* ISO/IEC 27701
* KSA PDPL
* MAS Technology Risk Management (Singapore)
* MITRE ATT\&CK (Cloud)
* NIS2 Directive
* NIST SP 800-171
* NYDFS 23 NYCRR 500
* SWIFT Customer Security Controls Framework
* Sarbanes-Oxley IT General Controls
* UK NCSC Cyber Assessment Framework

### Triage and Remediation

<Tabs>
  <Tab title="Remediation">
    ### Remediation

    <AccordionGroup>
      <Accordion title="Using Console" defaultOpen="true">
        To remediate the misconfiguration "Enable All AWS Organization Features" for AWS using AWS console, follow these steps:

        1. Log in to your AWS Management Console.
        2. Navigate to the AWS Organizations service.
        3. Click on the "Settings" tab in the left navigation menu.
        4. Scroll down to the "Feature Configuration" section.
        5. Click on the "Enable All Features" button.
        6. Review the features that will be enabled and click "Confirm".
        7. Wait for the process to complete.

        Once the process is complete, all the AWS organization features will be enabled and the misconfiguration will be remediated.

        #
      </Accordion>

      <Accordion title="Using CLI">
        To enable all AWS Organization features, you can follow these steps using AWS CLI:

        1. Open the AWS CLI on your local machine or EC2 instance.

        2. Run the following command to enable all AWS Organization features:

        ```
        aws organizations enable-all-features
        ```

        3. If you receive an error message that says "You don't have permissions to enable all features," you need to ensure that you have the necessary permissions to perform this action. You can check your permissions by running the following command:

        ```
        aws iam list-policies --scope Local | grep "AWSServiceRoleForOrganizations"
        ```

        4. If you do not have the necessary permissions, you can add them by creating a new policy. For example, you can create a new policy called "EnableAllOrgFeatures" with the following permissions:

        ```
        {
            "Version": "2012-10-17",
            "Statement": [
                {
                    "Sid": "EnableAllOrgFeatures",
                    "Effect": "Allow",
                    "Action": [
                        "organizations:EnableAllFeatures"
                    ],
                    "Resource": "*"
                }
            ]
        }
        ```

        5. Once you have the necessary permissions, you can run the command again to enable all AWS Organization features:

        ```
        aws organizations enable-all-features
        ```

        6. Wait for a few minutes for the changes to take effect.

        7. Verify that all AWS Organization features are enabled by running the following command:

        ```
        aws organizations describe-organization
        ```

        This should return a JSON object that includes information about your organization, including the status of all enabled features.
      </Accordion>

      <Accordion title="Using Python">
        To enable all AWS Organization features, you can use the AWS Organizations API in Python. Here are the steps to remediate this misconfiguration:

        1. First, you need to install the `boto3` library in Python. You can install it using the following command:

        ```
        pip install boto3
        ```

        2. Next, you need to set up your AWS credentials in your Python environment. You can do this by creating a new profile in your `~/.aws/credentials` file or by setting the `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` environment variables.

        3. Once you have set up your credentials, you can use the following Python code to enable all AWS Organization features:

        ```python theme={null}
        import boto3

        # Create a new AWS Organizations client
        org_client = boto3.client('organizations')

        # Enable all features for the organization
        org_client.enable_all_features()
        ```

        4. Finally, you can run the Python script to enable all AWS Organization features. Once the script has completed, all features will be enabled for your AWS Organization.

        Note: Before enabling all features, make sure that you understand the implications of doing so and that it is appropriate for your organization.
      </Accordion>

      <Accordion title="Using Terraform">
        This specific action (enabling “All Features” on an AWS Organization) cannot be managed via Terraform for Route53 or any other AWS service; it must be done once at the Organizations level from the management account using the AWS CLI or Console, and is irreversible.

        ```hcl theme={null}
        # There is no Terraform resource or argument in the hashicorp/aws provider
        # to run `aws organizations enable-all-features` or to toggle Organization
        # feature sets. This must be performed manually or via the AWS CLI:
        #
        #   aws organizations enable-all-features
        #
        # from the organization management account.
        #
        # After this one-time operation, you can use Terraform to manage
        # Service Control Policies (SCPs) and other org-level resources,
        # but not the feature-set toggle itself.
        ```

        Verification: `terraform plan` will show no changes related to Organization features; instead, confirm with `aws organizations describe-organization` that `FeatureSet` is `ALL`.
      </Accordion>
    </AccordionGroup>
  </Tab>
</Tabs>

### Additional Reading:

* \[[https://aws.amazon.com/organizations/features/\](](https://aws.amazon.com/organizations/features/]\()[https://aws.amazon.com/organizations/features/](https://aws.amazon.com/organizations/features/)]\([https://aws.amazon.com/organizations/features/](https://aws.amazon.com/organizations/features/)]\([https://aws.amazon.com/organizations/features/](https://aws.amazon.com/organizations/features/))
