AWS solutions documentation change
Summary
Updated description of 'Frozen' lease state to include manual freezing by Admins/Managers and clarify resource preservation recommendations
Security assessment
The change clarifies operational procedures for frozen leases but does not address security vulnerabilities or introduce security features.
Diff
diff --git a/solutions/latest/innovation-sandbox-on-aws/manager-guide.md b/solutions/latest/innovation-sandbox-on-aws/manager-guide.md index a3a27af55..8a4afe6bd 100644 --- a//solutions/latest/innovation-sandbox-on-aws/manager-guide.md +++ b//solutions/latest/innovation-sandbox-on-aws/manager-guide.md @@ -261 +261 @@ Active | The lease is actively being used by a sandbox user. -Frozen - Threshold Reached | The lease has reached the predefined freeze threshold based on either spend, or lease duration. Sandbox users will no longer have access to the lease but the account could still have active AWS Resources running in it, that you will be billed for. The We recommend Admin review and eject the account out of the account pool. +Frozen | The lease has been frozen either by reaching a predefined freeze threshold (based on spend or lease duration) or through manual action by an Admin or Manager. Sandbox users will no longer have access to the lease but the account could still have active AWS Resources running in it, that you will be billed for. If you want to preserve the resources in the account, we recommend an Admin review and eject the account out of the account pool.