1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
0
The Workspaces FAQ discussing pricing seems to indicate that AlwaysOn is more about how "ready" the workspace is and how long you need to wait when connecting to it. I would suspect that this means that the workspace is suspended vs shutdown when you disconnect. I would expect that you need to be connected to the workspace for the processes and resources to be available. If you need a long running task to run while you're away, an EC2 instance would be more appropriate.
con risposta 2 anni fa
Contenuto pertinente
AWS UFFICIALEAggiornata 4 mesi fa- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 3 anni fa
Always ON Workspaces are always running, they do not go into suspended state or shutdown state. When you disconnect from the Always ON Workspaces, the session is just in disconnected state (similar to locking the Windows screen), but your application should still be running and so should be the background tasks and applications. Unless the tasks/application requires user to be always logged in your script should run fine I believe but we may need to check further. Please open a support case for further assistance.