Account Limit Service Quota Code and Enabling Budgets (#815)

Author: cloudpossebot

docs/layers/accounts/account-baseline.mdx

@@ -48,7 +48,17 @@ Now that all the accounts have been deployed, we need to finalize the setup of t
              budgets_slack_username: AWS Budgets
              budgets_slack_channel: aws-budgets-notifications
      ```
-  3. **To enable budgets for the entire organization**, update `account-settings` in the same account as the Organization root account, typically `core-root`. This budget will include the total spending of all accounts in the Organization.
+  3. **Enable Cost Explorer** (if not already enabled). When attempting to create budgets, you may encounter the following error:
+
+  ```console
+  Error: creating Budget (xxx-core-gbl-artifacts-1000-total-monthly): operation error Budgets: CreateBudget, 
+  https response error StatusCode: 400, RequestID: xxx, 
+  AccessDeniedException: Account xxx is a linked account. To enable budgets for your account, ask the payer account to enable budgets first.
+  ```
+
+  This error occurs when AWS Cost Explorer has not been activated for the organization. To resolve this, navigate to the AWS Cost Explorer console in your organization's management account and verify that Cost Explorer is enabled. Cost Explorer must be enabled at the organization level before individual member accounts can create budgets.
+
+  4. **To enable budgets for the entire organization**, update `account-settings` in the same account as the Organization root account, typically `core-root`. This budget will include the total spending of all accounts in the Organization.
      ```yaml
      # stacks/orgs/acme/core/root/global-region/baseline.yaml
      import:
@@ -85,7 +95,7 @@ Now that all the accounts have been deployed, we need to finalize the setup of t
                      subscribers:
                        - slack
      ```
-  4. **To enable budgets for individual accounts**, update `account-settings` in the account you want to enable budgets for or as the default setting for all `account-settings` components to apply to every account. This budget will include the spending of the given account only.
+  5. **To enable budgets for individual accounts**, update `account-settings` in the account you want to enable budgets for or as the default setting for all `account-settings` components to apply to every account. This budget will include the spending of the given account only.
      ```yaml
      # stacks/catalog/account-settings.yaml
      components:
@@ -105,7 +115,7 @@ Now that all the accounts have been deployed, we need to finalize the setup of t
                limit_unit: GB
                time_unit: MONTHLY
      ```
-  5. Finally, reapply `account-settings` in any changed account to apply the new settings
+  6. Finally, reapply `account-settings` in any changed account to apply the new settings
      <AtmosWorkflow workflow="deploy/account-settings" fileName="quickstart/foundation/accounts" />
   </Steps>
   </Step>

docs/layers/accounts/deploy-accounts.mdx

@@ -129,11 +129,11 @@ This step-by-step process outlines how to deploy AWS accounts using `atmos` work
     ```bash
     aws service-quotas request-service-quota-increase \
       --service-code organizations \
-      --quota-code L-29A42BEB \
+      --quota-code L-E619E033 \
       --desired-value 20
     ```
 
-    Where `L-29A42BEB` is the quota code for "Accounts per organization".
+    Where `L-E619E033` is the quota code for "Default maximum number of accounts" under "AWS Organizations" in "us-east-1".
 
     <Note title="Terraform Alternative">
       This quota increase can also be requested through our [account-quotas](/components/library/aws/account-quotas/) component, but it's generally faster to handle this manually or through the API since it's a one time request.