AppStream fleet session disconnect timeout should be set to less than or equal to 5 mins¶
The disconnect timeout in minutes refers to the duration for which a streaming session remains active even after users have disconnected. It is recommended to set the disconnect timeout to 5 minutes or less for the AppStream Fleet.
How to fix¶
Attribute disconnect_timeout_in_seconds of aws_appstream_fleet must be non-empty.
Implementation options¶
Choose the option that matches how you manage Terraform. All options satisfy this control.
Option 1: Terraform AWS provider resources¶
If you manage resources directly, configure the relevant Terraform AWS provider resources to meet this control. See docs for the resources involved: aws_appstream_fleet.
resource "aws_appstream_fleet" "this" {
compute_capacity {
desired_instances = 1
}
idle_disconnect_timeout_in_seconds = 600
instance_type = "stream.standard.small"
name = "pofix-example-fleet"
}
Which option should I choose?
- Compliance.tf module (recommended): controls enforced by default and mapped to frameworks.
- Open source module (
terraform-aws-modules): compatible by design with compliance.tf. Same variable names for an easy, low-change migration path when you are ready. - Terraform AWS provider resources: manage Terraform resources directly.
Tool mappings¶
Use these identifiers to cross-reference this control across tools, reports, and evidence.
Compliance.tf (CTF) Control:
appstream_fleet_session_disconnect_timeout_300_secondsPowerpipe Control:
aws_compliance.control.appstream_fleet_session_disconnect_timeout_300_seconds