canonical: https://jentic.com/apis/amazonaws.com/aws-appstream

# AWS Amazon AppStream

Amazon AppStream 2.0 streams desktop applications from AWS to any HTML5-capable web browser. It manages the underlying fleets, image builders, and stacks so administrators can deliver Windows applications without provisioning end-user hardware or maintaining a VDI farm.

## For AI agents

Use the Amazon AppStream 2.0 API to stream desktop applications to web browsers on AWS, with 65 operations covering the full control-plane lifecycle.

## Scope

Does not handle full virtual desktop sessions, application licensing, or end-user identity provisioning - use for application streaming fleet and stack management only.

## Capabilities

- Provision streaming fleets sized for the expected concurrent user load
- Build and capture custom images using image builders with installed applications
- Bundle fleets, storage, and applications into stacks that users can launch
- Generate pre-signed streaming URLs that grant time-limited access to a stack
- Manage application catalog entries surfaced inside streaming sessions
- Associate users and entitlements with the stacks they are allowed to stream

## Use cases

### Browser-delivered access to a Windows engineering tool

Deliver licensed Windows engineering software - for example a CAD tool - to users on Mac or Chromebook hardware by capturing a custom image with the application installed, creating a fleet sized for concurrent usage, and bundling it into a stack. End users launch sessions through a pre-signed URL with no local install required. Initial bring-up typically takes a day per application.

Example prompt: Create a fleet named 'cad-fleet' from a custom image, create a stack named 'cad-stack', associate them, and generate a streaming URL for user-id 'engineer42'.

### Short-term contractor application access

Provision time-limited access to an internal application for a contractor by adding the user to a stack and issuing a pre-signed streaming URL valid for the engagement window. AppStream isolates the contractor's session from corporate infrastructure and tears down the streaming instance when the session ends, so there is no residual access on shared hardware.

Example prompt: Create a streaming URL for user-id 'contractor-jane' against the internal-tools stack with a validity of 8 hours.

### On-demand image build pipeline

Automate AppStream image refreshes by launching an image builder, scripting the application updates inside the session, and capturing a new image when validation succeeds. This lets a platform team ship application updates to streaming users without ad-hoc manual installs each release. Setup is generally completed in a day.

Example prompt: Create an image builder named 'cad-builder' from the previous golden image and instance type stream.standard.medium.

### AI agent provisioning streaming access through Jentic

A workforce-platform agent can grant streaming access on demand by calling AppStream operations through Jentic. The agent searches for the entitlement intent, loads the schemas it needs, and executes the call with scoped credentials, so AppStream admin keys never enter its context. New-hire access provisioning compresses to a single agent action.

Example prompt: Search Jentic for 'stream a Windows desktop application to a browser', load the schemas for CreateUser and CreateStreamingURL, and execute them for a new hire on the design-tools stack.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /#X-Amz-Target=PhotonAdminProxyService.CreateFleet | Create a fleet of streaming instances |
| POST | /#X-Amz-Target=PhotonAdminProxyService.CreateStack | Create a stack that bundles fleets and storage |
| POST | /#X-Amz-Target=PhotonAdminProxyService.CreateImageBuilder | Launch an image builder for installing apps |
| POST | /#X-Amz-Target=PhotonAdminProxyService.CreateStreamingURL | Generate a pre-signed streaming URL for a user |
| POST | /#X-Amz-Target=PhotonAdminProxyService.AssociateFleet | Associate a fleet with a stack |
| POST | /#X-Amz-Target=PhotonAdminProxyService.CreateApplication | Create an application catalog entry |

## Key resources

- **Fleets** — Pools of streaming instances that run user sessions
- **Stacks** — User-facing entitlements that combine fleets, applications, and storage
- **ImageBuilders** — Instances used to install applications and capture custom images
- **Images** — Captured machine images containing installed applications
- **Applications** — Application entries surfaced in the streaming catalog
- **Users** — End users entitled to stream from one or more stacks
- **StreamingURLs** — Pre-signed URLs that launch a streaming session in a browser

## Why Jentic

- **Setup:** Wiring Amazon AppStream 2.0 by hand means creating IAM credentials, choosing the right regional host from appstream.{region}.amazonaws.com, signing every request with AWS SigV4, and passing the X-Amz-Target action header on each call yourself. Through Jentic you install once, import Amazon AppStream 2.0 from the API Directory, store the AWS access key once, and your agent calls it.
- **Permission scoping:** Amazon AppStream 2.0 carries the fleet and stack targets in the request body rather than the URL path, so limit the agent to the operations it needs, such as CreateFleet, CreateStack, or CreateStreamingURL. You choose the operations it may call, so destructive ones like deleting a fleet or a stack are not included unless you add them.
- **Credential handling:** Your AWS access key for Amazon AppStream 2.0 is stored once, encrypted, by your own Jentic One instance and signed with SigV4 at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'stream a Windows desktop application to a browser' or 'generate a streaming URL for a user', and Jentic returns the matching Amazon AppStream 2.0 operation with its input schema so the agent calls the right endpoint without browsing the AWS service reference.

## Related APIs

- **EC2 self-managed instances** — EC2 lets you run Windows desktops yourself but without the streaming protocol or session management AppStream provides
- **Cognito identity pools** — Cognito provides federated identities that can drive AppStream user pools

## FAQ

### What authentication does the Amazon AppStream 2.0 API use?

The Amazon AppStream 2.0 API uses AWS Signature Version 4 (HMAC) request signing with IAM-issued credentials, the same scheme as every AWS service API. Jentic's your Jentic One instance stores those AWS credentials encrypted in the vault, generates short-lived signed requests at execution time, and never passes raw access keys into the agent's context.

### Can I create a streaming fleet for my application with the Amazon AppStream 2.0 API?

Yes - the Amazon AppStream 2.0 API exposes 65 operations including the actions needed for that scenario. Use the operations listed in the key endpoints section as the starting point, then chain calls as needed for your workflow.

### What are the rate limits for the Amazon AppStream 2.0 API?

AWS applies per-account, per-region request rate limits to the Amazon AppStream 2.0 control plane. Specific limits are not encoded in the OpenAPI spec; consult the AWS service quotas console for the Amazon AppStream 2.0 entry, and design retries with exponential backoff to absorb throttling responses.

### How do I stream a Windows desktop application to a browser through Jentic?

Run pip install jentic, then call client.search('stream a Windows desktop application to a browser') to discover the Amazon AppStream 2.0 operations that match. Load the schema for the chosen operation with client.load(...) and execute it with client.execute(...). Jentic handles AWS request signing automatically against the credentials stored in your Jentic One instance.

### Is the Amazon AppStream 2.0 API free to call?

AWS does not charge for control-plane API calls themselves on most Amazon AppStream 2.0 operations, but the underlying resources you create or operate (fleets, queries, deployments, and so on) incur usage charges according to the Amazon AppStream 2.0 pricing page. Refer to the AWS pricing page for the service to estimate cost.

### Which operations should an agent call first when working with the Amazon AppStream 2.0 API?

For most workflows, agents should start by listing existing resources to understand the current state, then call the create or update operation that matches the intent. The endpoints listed under Key Endpoints in the catalog give a ranked starting set.

### Can I limit what my agent is allowed to do with the AWS AppStream API?

Yes. Because you run Jentic One yourself, your own rules decide which AppStream operations and which AWS credentials the agent may use. Since AppStream carries the fleet and stack targets in the request body rather than the URL path, you scope the agent to just the operations it needs, such as CreateFleet, CreateStack, or CreateStreamingURL. Destructive operations like deleting a fleet or a stack are not included unless you explicitly add them.