Check ID:
Provider: AWS
Service:
Severity: MEDIUM
Categories:
Resource type:
appstream_fleet_session_idle_disconnect_timeoutProvider: AWS
Service:
appstreamSeverity: MEDIUM
Categories:
identity-accessResource type:
OtherWhat this check verifies
Amazon AppStream fleets are evaluated for the idle disconnect timeout setting, confirming it is configured to10 minutes (<=600s) or less before inactive users are dropped and the session’s disconnect_timeout window begins.
Risk
Long idle sessions keep desktops/apps accessible without user presence, enabling session hijacking, shoulder surfing, and data exposure. They also consume capacity and extend billing, reducing availability for other users.Recommendation
Configure an idle disconnect timeout 10 minutes. Pair with a shortdisconnect_timeout, require re-authentication on reconnect, and enforce least privilege. Monitor session metrics and adjust per role to balance security, cost, and user experience.
Remediation
- CLI
- Terraform
- Native IaC
- Dashboard steps
aws appstream update-fleet —name <FLEET_NAME> —idle-disconnect-timeout-in-seconds 600
References
- https://docs.aws.amazon.com/appstream2/latest/developerguide/set-up-stacks-fleets.html
- https://awscli.amazonaws.com/v2/documentation/api/2.9.6/reference/appstream/update-fleet.html
Where this check fires
This check runs on every scheduled scan against your AWS account. Findings appear at Cloud Security → Findings filterable byCheck ID = appstream_fleet_session_idle_disconnect_timeout. To re-evaluate after a fix, hit Run now on the account’s schedule under Cloud Security → Schedules — the next scan re-checks this control and marks the finding fixed or keeps it persistent.
← Back to AWS checks