⭐ Repository → 📁 Compliance Engine → 📁 CloudAware → 📁 AWS → 📁 WorkSpaces

🛡️ AWS WorkSpace is unused🟢

• Contextual name: 🛡️ WorkSpace is unused🟢
• ID: /ce/ca/aws/workspaces/workspace-unused
• Tags:
  • 🟢 Policy with categories
  • 🟢 Policy with type
  • 🟢 Production policy
• Policy Type: COMPLIANCE_POLICY
• Policy Categories: COST

Logic

• 🧠 prod.logic.yaml🟢
  • 📗 AWS WorkSpace
  • 🔌 AWS WorkSpace - object.extracts.yaml
  • 🧪 test-data.json

Description

Open File

Description

This policy identifies AWS WorkSpaces that are considered unused. A WorkSpace is considered unused if it remains in an AVAILABLE or STOPPED state without any user connections for 30 days or more.

Rationale

AWS WorkSpaces incur costs whether they are actively used, or automatically stopped (which still generates a stopped-instance fee). Maintaining idle WorkSpaces unnecessarily increases expenses. Furthermore, unused but running WorkSpaces may not be regularly patched or monitored, creating potential security vulnerabilities and expanding the attack surface of the environment.

Audit

This policy flags an AWS WorkSpaces as INCOMPLIANT if it is in either the AVAILABLE or STOPPED State and the Last Known User Connection Timestamp is empty or older than 30 days.

Remediation

Open File

Remediation

Terminate unused AWS WorkSpaces to reduce costs and minimize security risks. Before proceeding, ensure that any important data is backed up, as termination is irreversible.

Terminate a WorkSpace

Warning

Terminating a WorkSpace is a permanent action. All associated user data will be destroyed and cannot be recovered. To safeguard important information, ensure user data is backed up prior to termination. For help with backing up user data, contact AWS Support.

From AWS CLI

aws workspaces terminate-workspaces \
    --terminate-workspace-requests {{workspace-ids}}

policy.yaml

Open File

Linked Framework Sections

Section	Sub Sections	Internal Rules	Policies	Flags	Compliance
💼 Cloudaware Framework → 💼 Waste Reduction			25		no data