AWS organizations: Clarify SUSPENDED account API and console access behavior
Summary
Expanded the SUSPENDED state description to note that API calls to AWS services are blocked while billing/account console access remains available.
Security assessment
Describes account state behavior; it clarifies access restrictions but is not a security feature or vulnerability fix.
Evidence
+SUSPENDED | In this state, the account is unusable because AWS has restricted access. You can't make API calls to AWS services from a suspended account. You can still sign in and access the AWS Billing and Account Management console using its direct link, where the account holder can view billing information and contact Support, who can explain why the account is suspended.
Diff
diff --git a/organizations/latest/userguide/orgs_manage_accounts_account_state.md b/organizations/latest/userguide/orgs_manage_accounts_account_state.md index dc7363c99..87659ed2d 100644 --- a//organizations/latest/userguide/orgs_manage_accounts_account_state.md +++ b//organizations/latest/userguide/orgs_manage_accounts_account_state.md @@ -32 +32 @@ ACTIVE | This state indicates that the account is fully operational and availab -SUSPENDED | In this state, the account is unusable because AWS has restricted access. The account holder can still view billing information and contact Support, who can explain why the account is suspended. +SUSPENDED | In this state, the account is unusable because AWS has restricted access. You can't make API calls to AWS services from a suspended account. You can still sign in and access the AWS Billing and Account Management console using its direct link, where the account holder can view billing information and contact Support, who can explain why the account is suspended.