aws appstream create-stack

Creates a stack to start streaming applications to users. A stack consists of an associated fleet, user access policies, and storage configurations


--name <string>The name of the stack
--description <string>The description to display
--display-name <string>The stack name to display
--storage-connectors <list>The storage connectors to enable
--redirect-url <string>The URL that users are redirected to after their streaming session ends
--feedback-url <string>The URL that users are redirected to after they click the Send Feedback link. If no URL is specified, no Send Feedback link is displayed
--user-settings <list>The actions that are enabled or disabled for users during their streaming sessions. By default, these actions are enabled
--application-settings <structure>The persistent application settings for users of a stack. When these settings are enabled, changes that users make to applications and Windows settings are automatically saved after each session and applied to the next session
--tags <map>The tags to associate with the stack. A tag is a key-value pair, and the value is optional. For example, Environment=Test. If you do not specify a value, Environment=. If you do not specify a value, the value is set to an empty string. Generally allowed characters are: letters, numbers, and spaces representable in UTF-8, and the following special characters: _ . : / = + \ - @ For more information about tags, see Tagging Your Resources in the Amazon AppStream 2.0 Administration Guide
--access-endpoints <list>The list of interface VPC endpoint (interface endpoint) objects. Users of the stack can connect to AppStream 2.0 only through the specified endpoints
--embed-host-domains <list>The domains where AppStream 2.0 streaming sessions can be embedded in an iframe. You must approve the domains that you want to host embedded AppStream 2.0 streaming sessions
--cli-input-json <string>Performs service operation based on the JSON string provided. The JSON string follows the format provided by ``--generate-cli-skeleton``. If other arguments are provided on the command line, the CLI values will override the JSON-provided values. It is not possible to pass arbitrary binary values using a JSON-provided value as the string will be taken literally
--generate-cli-skeleton <string>Prints a JSON skeleton to standard output without sending an API request. If provided with no value or the value ``input``, prints a sample input JSON that can be used as an argument for ``--cli-input-json``. If provided with the value ``output``, it validates the command inputs and returns a sample output JSON for that command