AWS Amazon AppStream

Name: Amazon AppStream API
Brand: Amazon AppStream 2.0
Availability: InStock

✓ Official Vendor SpecCloud InfrastructureComputeapiKey65 EndpointsREST

For 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.

Install Jentic One Beta

Connect the Amazon AppStream to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Amazon AppStream, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Amazon AppStream API.

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

GET STARTED

Start building with Amazon AppStream API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Amazon AppStream API for, with concrete tasks.

★ 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.

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.

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.

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.

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

65 endpoints — amazon appstream 2.

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

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

AWS IAM access keys for Amazon AppStream 2.0 are stored encrypted in the Jentic vault. Jentic signs each request with AWS SigV4 at execution time and returns only the API response — raw access keys never enter the agent's context.

Intent-based discovery

Agents express intents like 'stream a Windows desktop application to a browser' and Jentic returns matching Amazon AppStream 2.0 operations along with their input schemas, so the agent picks the right call without browsing the AWS service reference.

Time to first call

Direct Amazon AppStream 2.0 integration: 2-5 days for IAM scoping, SigV4 wiring, retry logic, and pagination handling. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using Amazon AppStream API through Jentic.

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 MAXsystem 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 vault.

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.

AWS Amazon AppStream

Connect the Amazon AppStream to your agent

Capabilities

Start building with Amazon AppStream API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs