- 新しい順
- 投票が多い順
- コメントが多い順
When you're using the CreateStreamingURL method via the API/CLI, you can pass the ApplicationId parameter with the ID (not display name) of your application. The application ID was created when you created the application (not app block), and can be found by viewing the application details page (the "name" field), or calling the DescribeApplications API (the "name" value) When this parameter is passed, the application catalog is skipped, and the session reservation process and application launch starts immediately, without user action. Note that this will start the timer of the billing duration of the Elastic fleet streaming session, rather than waiting for the user action of selecting the application.
This ApplicationId parameter is only available when you programmatically generate streaming URLs - it's not available via the console. Note that you should be generating the streaming URLs on user request, and they should last only as long as the user needs to start the streaming session. The validity of the URL doesn't impact the duration of the streaming session.
AppStream 2.0 also has some convenient workshops to help with adding your application to your website, too: https://aws.amazon.com/appstream2/getting-started/isv-workshops/. The workshops have sample JS code you can use to securely implement the workflow, and show how you can either use your own identity provider, or use Cognito.
Hope this helps!
This absolutely solved my problem and it works perfectly. Thank you! I didn't think to look at the CreateStreamingURL parameters other than the fields I was already using. Appreciate your quick and thorough answers. This is a really nice service.