AppStream 2.0 are single session host, not multi-session.
AppStream 2.0 is single user per instance, and intended to be a single streaming session at a time. User connections are per username per stack/fleet, so a subsequent user would be sharing the same username as the original user which would impact things like S3 Home Folder, App Settings Persistence, App Entitlements, and other things.
In the event that a user needs to share screen with another user, using a screen sharing utility like Amazon Chime, Cisco WebEx, Google Meet, or other similar technology is recommended. Those can provide the ability to delegate keyboard/mouse to another user, while the owner of that streaming session retains ability to revoke access.
AppStream 2.0 - Nice DCV - can a user delegate control to another user connected to the same streamasked 9 months ago
Can one customer's AppStream or Workspaces make connections to another customer's account via PrivateLink?Accepted Answerasked a year ago
Only one of several virtual nice-dcv sessions may be connected toAccepted Answerasked 2 years ago
Can I use the NICE DCV connection gateway to 'proxy' DCV client connections without defining a 'web resources' component?asked 9 months ago
AppStream 2.0 - Access Control for different users and monitoringAccepted Answerasked 3 years ago
Can I register multiple users in access control?asked 8 months ago
Can we two gitlab servers connect to the same RDS postgresql database?
Prevent users to share the stream endpointasked 2 years ago
Can two servers connect to the same AWS CodeCommit repository?
Nice DCV - Limit client access to applicationsAccepted Answerasked 5 months ago