AWS Amazon WorkLink

Name: Amazon WorkLink API
Brand: Amazon WorkLink
Availability: InStock

★ Only Publicly Available OpenAPI DocumentIdentity AuthAuthorizationapiKey33 EndpointsREST

Install Jentic One Beta

Connect the Amazon WorkLink to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Amazon WorkLink, 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 WorkLink API.

Create, describe, update, and delete WorkLink fleets

Associate and disassociate internal web domains with a fleet

Configure the company network (VPC, subnets, security groups) that WorkLink reaches into

GET STARTED

Start building with Amazon WorkLink API

Explore with Jentic

View OpenAPI Document

For Agents

Manage Amazon WorkLink fleets, domain associations, and identity provider configuration for legacy mobile-access deployments still in operation.

Use for: Create a new WorkLink fleet for a business unit, Associate an internal domain with a WorkLink fleet, List all devices currently registered to a fleet, Configure the SAML identity provider for a WorkLink fleet

Not supported: Does not handle desktop streaming, full VPN tunnelling, or device management for non-mobile clients - use for managing Amazon WorkLink mobile fleets, internal domains, and identity provider configuration only. Note: AWS announced WorkLink end-of-life on April 30, 2024.

Jentic publishes the only available OpenAPI specification for Amazon WorkLink, keeping it validated and agent-ready. Amazon WorkLink was a managed service that provided secure access to internal websites and web apps from iOS and Android phones without VPN clients or app distribution. The API manages fleets, associates internal domains, configures audit streams, registers website certificate authorities, attaches SAML identity providers, and lists devices. The 33 operations include Associate/Disassociate verbs for domains, certificate authorities, and authorization providers, and the standard fleet CRUD plus device listing. Note: AWS ended Amazon WorkLink on April 30, 2024 - this spec is provided for legacy automation maintenance only.

Use Cases

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

★ Operating a Legacy WorkLink Fleet

Customers still running an Amazon WorkLink deployment use this API to keep their fleets healthy through to migration. ListFleets and DescribeFleetMetadata enumerate fleets; ListDomains and DescribeDomain show their associated internal sites; ListDevices and DescribeDevice surface registered handsets. UpdateAuditStreamConfiguration keeps the access log flowing to Kinesis Data Streams for compliance until the workload is replaced.

Call ListFleets, then for each FleetArn call DescribeFleetMetadata and ListDomains, returning a per-fleet summary with domain count and device count.

Incident Response: Revoking Access

When a phone is lost or an employee leaves, revoke their access to internal apps in seconds. SignOutUser terminates active WorkLink sessions for a username; RevokeDomainAccess blocks an internal domain from being reached through the fleet during an incident. RestoreDomainAccess re-enables the domain once the incident is resolved.

Call SignOutUser with FleetArn and Username 'jane.doe@example.com', then RevokeDomainAccess with FleetArn and DomainName 'sensitive.internal.example.com'.

Migration Inventory Build

Before retiring WorkLink, capture a full inventory: fleets, domains, certificate authorities, authorization providers, devices, audit configuration, and identity provider metadata. The Describe* and List* operations together produce the source of truth for designing the replacement (e.g. a VPN with mobile MDM or a zero-trust application proxy).

For each fleet, call DescribeFleetMetadata, DescribeIdentityProviderConfiguration, DescribeCompanyNetworkConfiguration, DescribeAuditStreamConfiguration, ListDomains, ListWebsiteCertificateAuthorities, ListWebsiteAuthorizationProviders, and ListDevices, and aggregate into a JSON inventory.

Agent-Driven Fleet Operations via Jentic

Even on a legacy service, an operations agent can manage WorkLink through Jentic without holding AWS keys. The agent submits intents like 'list all worklink fleets and their device counts', Jentic loads ListFleets and ListDevices, executes them, and returns structured results. This pattern keeps the secret material out of the agent's context until the workload is finally migrated off WorkLink.

Through Jentic, search for 'list amazon worklink fleets', load ListFleets, execute it, then for each fleet load and call ListDevices.

Key Endpoints

33 endpoints — jentic publishes the only available openapi specification for amazon worklink, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/listFleets

List WorkLink fleets

POST

/createFleet

Create a WorkLink fleet

POST

/associateDomain

Associate an internal domain with a fleet

POST

/listDevices

List devices registered to a fleet

POST

/signOutUser

Sign a user out of WorkLink sessions

POST

/revokeDomainAccess

Revoke access to an internal domain

POST

/listFleets

List WorkLink fleets

POST

/createFleet

Create a WorkLink fleet

POST

/associateDomain

Associate an internal domain with a fleet

POST

/listDevices

List devices registered to a fleet

POST

/signOutUser

Sign a user out of WorkLink sessions

Why Jentic?

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

Credential isolation

Your AWS access keys are stored once, encrypted, by your own Jentic One instance and used to sign each WorkLink request with SigV4 at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list WorkLink fleets' or 'list devices in a fleet', and Jentic returns the matching WorkLink operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Amazon WorkLink API through Jentic.

Why is there no official OpenAPI spec for Amazon WorkLink?

AWS does not publish an OpenAPI specification for Amazon WorkLink; it ships Smithy models and language-specific SDKs instead. Jentic generates and maintains this OpenAPI spec so that AI agents and developers can call Amazon WorkLink via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does Amazon WorkLink use?

WorkLink uses AWS SigV4 in the Authorization header. The IAM principal needs worklink:* permissions on the relevant fleet ARN. Through Jentic, your AWS keys stay in the vault and Jentic signs each request.

Can I still use Amazon WorkLink?

AWS announced end-of-life for Amazon WorkLink on April 30, 2024. This API is documented for customers maintaining or migrating off existing fleets; new deployments should use a VPN, AWS Verified Access, or another zero-trust application proxy.

What are the rate limits for the WorkLink API?

WorkLink has modest management-API throughput intended for fleet administration: a few transactions per second per account. Throttling responses use the standard ThrottlingException; retry with exponential back-off.

How do I list WorkLink fleets through Jentic?

Search Jentic with 'list amazon worklink fleets', load ListFleets, and execute it (paginating with NextToken if needed). Jentic returns the FleetSummaryList with each fleet's ARN, name, and creation time.

Can I sign a user out of all WorkLink sessions at once?

Yes. SignOutUser with FleetArn and Username terminates the user's active WorkLink sessions on every device for that fleet. Pair with RevokeDomainAccess if you also need to block specific internal domains.

Does WorkLink support SAML for user authentication?

Yes. Use UpdateIdentityProviderConfiguration to attach SAML metadata for the fleet; users then authenticate to internal apps with their corporate SSO. DescribeIdentityProviderConfiguration returns the current SAML metadata document URL.

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

Yes. Because Jentic One is self-hosted, you decide which WorkLink operations and which AWS keys the agent may use, and your own rules are what grant access. You can scope the agent to read-only operations such as ListFleets and ListDevices, so state-changing calls like RevokeDomainAccess or SignOutUser are excluded unless you explicitly add them. WorkLink identifies fleets by an ARN passed in the request body rather than a resource id in the path, so the safest approach is to allow only the specific operations the agent needs.

AWS Amazon WorkLink

Connect the Amazon WorkLink to your agent

Capabilities

Start building with Amazon WorkLink API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs