Hmm. I don't know what's different, but I KNOW Steam games work on AppStream. I remember playing Arkham Asylum from my own Steam account.
As a developer I have tended to prefer the "standalone instance" route, and I almost certainly installed Steam that way: Follow the standalone instance instructions [1] and then log in to it as a remote desktop, installing whatever you need.
If the Steam install process needs GPU acceleration, then you'll also need to set up a VNC server on the instance and connect that way. Windows' "Remote Desktop Connection" can't use the GPU, where a VNC connection can.
BUT beware: Make sure your VNC password is as strong as possible; maybe even turn off VNC when you're not actively using it.
Thanks for the insights - Digging into it, my first install was standalone and failed for no proper reason (trying to run guacamelee from the humblebundle - no meaningful error message was given).
Steam games seem to fail whenever something needs to be admin, most likely installing directX on first - run. I'm going to try running them once first before packaging the appstream and then see how it goes.
As a developer I have tended to prefer the "standalone instance" route, and I almost certainly installed Steam that way: Follow the standalone instance instructions [1] and then log in to it as a remote desktop, installing whatever you need.
If the Steam install process needs GPU acceleration, then you'll also need to set up a VNC server on the instance and connect that way. Windows' "Remote Desktop Connection" can't use the GPU, where a VNC connection can.
BUT beware: Make sure your VNC password is as strong as possible; maybe even turn off VNC when you're not actively using it.
Good luck!
[1] http://docs.aws.amazon.com/appstream/latest/developerguide/a...