Jentic publishes the only available OpenAPI specification for Amazon API Gateway, keeping it validated and agent-ready. Amazon API Gateway is a managed service for creating and operating REST and WebSocket APIs at any scale, fronting AWS Lambda, EC2-hosted services, and any HTTP backend. The control-plane API exposes 120 operations covering REST API definitions, resources, methods, integrations, deployments, stages, custom domain names, API keys, usage plans, authorizers, and documentation parts. Platform teams use it to drive infrastructure-as-code workflows that go beyond what CloudFormation exposes.
120 endpointsAmazon 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.
65 endpointsAmazon EC2 Auto Scaling launches and terminates EC2 instances automatically in response to demand, scheduled actions, and instance health checks. The API lets you create Auto Scaling groups, define launch templates and configurations, attach load balancers and target groups, configure scaling policies driven by CloudWatch alarms, and set lifecycle hooks for graceful instance bring-up and tear-down. It is the control plane for keeping a fleet of EC2 instances at the size your workload requires while replacing failed instances and balancing them across Availability Zones.
130 endpointsJentic publishes the only available OpenAPI specification for Amazon Elastic Compute Cloud, keeping it validated and agent-ready. Amazon EC2 provides resizable compute capacity in AWS, and its API is the foundational control plane for EC2 instances, EBS volumes, VPC networking, security groups, and a broad set of related compute primitives. With more than a thousand operations, the API spans instance lifecycle, AMIs, key pairs, networking (VPC, subnets, route tables, NAT, VPN), elastic IP addresses, transit gateways, and capacity reservations. Use it when an agent needs to provision compute, manage networking, or automate any AWS infrastructure-as-API workflow.
1182 endpointsJentic publishes the only available OpenAPI specification for Amazon Elastic Kubernetes Service, keeping it validated and agent-ready. Amazon EKS is a managed Kubernetes service that runs upstream Kubernetes on AWS without requiring teams to operate the control plane themselves. The API covers cluster lifecycle management, managed node groups, Fargate profiles, EKS add-ons, and identity provider configuration. It is designed for platform teams that need to provision, scale, and upgrade Kubernetes clusters across multiple AWS regions while keeping pace with upstream Kubernetes releases.
35 endpointsJentic publishes the only available OpenAPI specification for Amazon Elasticsearch Service, keeping it validated and agent-ready. The Amazon Elasticsearch (now OpenSearch) Configuration API creates and manages Elasticsearch domains, including instance configuration, storage, VPC settings, access policies, package associations, and cross-cluster connection setup. The API also covers service software updates, package management, and VPC endpoint authorisation. It is built for platform teams that need to provision and operate search and analytics clusters on AWS without console-driven workflows.
50 endpointsJentic publishes the only available OpenAPI specification for Amazon EMR Containers, keeping it validated and agent-ready. Amazon EMR on EKS lets data teams run open-source big-data frameworks such as Apache Spark on existing Amazon EKS clusters. The API manages virtual clusters that map to EKS namespaces, job runs that submit Spark workloads, managed endpoints, and reusable job templates. It is designed for analytics platform teams that want EMR's runtime optimisations and managed Spark images while consolidating on Kubernetes for compute.
19 endpointsJentic publishes the only available OpenAPI specification for Amazon GameLift, keeping it validated and agent-ready. Amazon GameLift is AWS's managed service for hosting session-based multiplayer game servers in the cloud. The API covers fleets, builds, scripts, aliases, game sessions, player sessions, FlexMatch matchmaking, queues, and GameLift FleetIQ for cost-optimised Spot capacity. It is built for game studios that need to deploy custom server binaries to global AWS regions, scale match capacity dynamically, and route players into matches with low latency.
104 endpointsJentic publishes the only available OpenAPI specification for Amazon Managed Blockchain, keeping it validated and agent-ready. Amazon Managed Blockchain is a fully managed service for creating and operating blockchain networks built on open-source frameworks such as Hyperledger Fabric and read access to Ethereum. The control plane covers networks, members, peer nodes, proposals, voting, accessor tokens, and tag management. It removes the operational burden of provisioning ordering services, certificate authorities, and peer nodes so teams can focus on chaincode and application logic.
27 endpointsJentic publishes the only available OpenAPI specification for Amazon MQ, keeping it validated and agent-ready. Amazon MQ is the managed message-broker service for Apache ActiveMQ and RabbitMQ — it provisions broker instances, manages users and access, applies versioned configurations, schedules maintenance reboots and tags brokers for cost tracking. The 22 endpoints cover the full broker lifecycle: CreateBroker through DeleteBroker, ListConfigurations and ListConfigurationRevisions, CreateUser/UpdateUser/DeleteUser per broker, RebootBroker for in-place restarts, and tag management.
22 endpointsJentic publishes the only available OpenAPI specification for Amazon Route 53, keeping it validated and agent-ready. Amazon Route 53 is AWS's authoritative DNS, domain registration, and traffic-routing service. It manages public and private hosted zones, lets you create DNS records with health checks and failover policies, supports advanced traffic routing (weighted, latency-based, geolocation, geoproximity), and offers DNSSEC signing for zones. The same API also handles domain registration and CIDR-based traffic routing.
70 endpointsJentic publishes the only available OpenAPI specification for AmplifyBackend, keeping it validated and agent-ready. AWS AmplifyBackend is the admin API that powers backend resource generation for Amplify Hosting applications, including auth, API, storage, and config resources tied to specific Amplify backend environments. The API exposes 31 operations to clone, configure, list, and remove backends, manage authentication and API resources, and import existing Cognito user pools. Platform teams use it to script Amplify CLI generated backends from CI rather than developer machines.
31 endpointsJentic publishes the only available OpenAPI specification for AWS Amplify, keeping it validated and agent-ready. AWS Amplify Hosting provides continuous deployment and global hosting for full-stack web and mobile apps, building from a connected Git repository on every push. The control-plane API exposes 37 operations spanning apps, branches, deployments, backend environments, custom domains, webhooks, and access logs. Frontend platform teams use it to provision per-feature preview environments, automate domain bindings, and trigger deployments outside the standard Git push flow.
37 endpointsAWS App Mesh is a service mesh based on the Envoy proxy that standardises how microservices communicate. It provides routing, retries, circuit breaking, and end-to-end visibility for services running on ECS, EKS, EC2, and Fargate without requiring service code changes.
38 endpointsJentic publishes the only available OpenAPI specification for AWS App Runner, keeping it validated and agent-ready. Deploy containerized web applications and APIs directly from source code or container images without managing infrastructure. App Runner automatically handles provisioning, scaling, load balancing, and TLS certificate management across AWS regions, reducing deployment from days to minutes.
35 endpointsJentic publishes the only available OpenAPI specification for AWS Application Migration Service, keeping it validated and agent-ready. Application Migration Service (MGN) is AWS's lift-and-shift service for migrating physical, virtual, and cloud servers onto AWS. It continuously replicates source servers into a staging area in the target AWS account and orchestrates cutover and test launches into EC2. The control plane covers source servers, applications, waves, replication and launch configuration templates, post-launch actions, and lifecycle state changes such as archive, disconnect, and finalize cutover.
61 endpointsAWS Batch runs containerised batch computing workloads at any scale by dynamically provisioning the right amount and type of compute on EC2 or Fargate. The API lets you register job definitions, create compute environments backed by EC2 Spot, On-Demand, or Fargate capacity, define job queues with priority and scheduling policies, submit jobs with array and dependency support, and inspect or cancel jobs as they run. It is well suited to genomics pipelines, financial Monte Carlo, media transcoding, and other parallel container workloads.
24 endpointsJentic publishes the only available OpenAPI specification for AWS Cloud Map, keeping it validated and agent-ready. Cloud Map is the AWS service-discovery layer for microservices: it lets applications register service instances with a custom name, attach health checks, and resolve them via DNS or an HTTP API at runtime. Agents can create public or private DNS namespaces, define services with DNS or HTTP-only configurations, register and deregister instances, run DiscoverInstances queries, and inspect operation status. The 26 operations cover namespaces, services, instances, and discovery.
26 endpointsJentic publishes the only available OpenAPI specification for AWS Compute Optimizer, keeping it validated and agent-ready. AWS Compute Optimizer analyzes utilization metrics from CloudWatch to recommend right-sized configurations for EC2 instances, EC2 Auto Scaling groups, EBS volumes, Lambda functions, ECS services on Fargate, RDS, and idle resources. It quantifies the savings and performance risk of each recommendation and can export full recommendation sets to S3 for downstream analysis. Recommendations are refreshed daily based on at least 14 days of metric history.
21 endpointsJentic publishes the only available OpenAPI specification for AWS Direct Connect, keeping it validated and agent-ready. AWS Direct Connect provides dedicated network links between on-premises networks and AWS, bypassing the public internet for lower latency and predictable throughput. The API covers the lifecycle of physical connections, link aggregation groups (LAGs), virtual interfaces (private, public, transit), Direct Connect gateways, and BGP/MACsec configuration. Use it when an agent needs to provision hybrid networking, accept hosted connections, or manage virtual interface attachments to VPCs and Transit Gateways.
63 endpointsJentic publishes the only available OpenAPI specification for AWS Global Accelerator, keeping it validated and agent-ready. AWS Global Accelerator is a networking service that improves the availability and performance of applications by routing user traffic through the AWS global network to optimal regional endpoints. It provisions static anycast IP addresses, configures listeners and endpoint groups, and supports both standard and custom routing accelerators. The API covers full lifecycle management of accelerators, listeners, endpoint groups, BYOIP CIDR advertisement, and cross-account attachments across 49 endpoints.
49 endpointsJentic publishes the only available OpenAPI specification for AWS Lambda, keeping it validated and agent-ready. Lambda is the AWS serverless compute service that runs code in response to events without provisioning servers. The 66-endpoint API covers function lifecycle, alias and version management, layers, event source mappings to SQS, Kinesis, and DynamoDB, function URLs, code signing configurations, concurrency controls, and synchronous and asynchronous invocations. It is the foundation of most event-driven AWS architectures and pairs with API Gateway, EventBridge, and S3 for end-to-end serverless applications.
66 endpointsAWS Lambda runs code in response to events without requiring you to provision or manage servers. The Lambda API gives full control over functions, including creating and updating function code from zip archives or container images, configuring memory and timeout, attaching layers, managing aliases and versions, and wiring event source mappings to streams from Kinesis, DynamoDB, SQS, MSK, and self-managed Kafka. It also supports synchronous, asynchronous, and streaming invocation, plus URL-based public endpoints via Lambda function URLs.
50 endpointsJentic publishes the only available OpenAPI specification for AWS License Manager, keeping it validated and agent-ready. License Manager helps AWS customers track software licences from vendors such as Microsoft, Oracle, and SAP across multiple accounts and on-premises servers. The 50-endpoint API covers licence configurations, licence creation and check-in/check-out, grants for cross-account sharing, conversion tasks, report generators, and resource inventory. It enforces seat counts, BYOL workflows, and compliance reporting that compute-heavy organisations rely on for vendor audits.
50 endpointsAWS Migration Hub provides a single place to track the progress of application migrations into AWS across multiple migration tools, including Application Migration Service, Database Migration Service, partner tooling, and custom scripts. The API lets a tool register progress update streams, import migration tasks, associate discovered resources and created artifacts, and report task and application state. Migration Hub itself does not move workloads; it aggregates the operational signal from the tools that do.
17 endpointsJentic publishes the only available OpenAPI specification for AWS Migration Hub Config, keeping it validated and agent-ready. AWS Migration Hub Config lets organisations declare and inspect the home region for their Migration Hub data — the single AWS region where status from migration tools such as Application Migration Service (MGN), Database Migration Service (DMS), and partner tools is aggregated. Setting the home region is the first step before any migration tool can publish progress to Migration Hub, and it is a one-time control-plane decision per AWS account.
3 endpointsJentic publishes the only available OpenAPI specification for AWS Resource Groups, keeping it validated and agent-ready. AWS Resource Groups lets you organise Amazon Web Services resources such as EC2 instances, RDS databases, and S3 buckets into logical collections defined by tag or CloudFormation stack membership. The service exposes group lifecycle operations, query-based membership rules, and account-level configuration so platform teams can apply consistent automation across many resources at once. It is the foundation for cross-resource search, batch tagging, and environment-scoped dashboards in the AWS Console.
18 endpointsJentic publishes the only available OpenAPI specification for AWS Resource Groups Tagging API, keeping it validated and agent-ready. The Tagging API provides a unified interface for applying, removing, and querying tags across more than 100 supported AWS resource types — EC2, RDS, S3, Lambda, ECS, and more — without calling each service's individual tag operation. It also exposes tag-compliance reporting, so finance and platform teams can audit which resources are missing required cost-allocation tags. This is the operational backbone of cross-service tagging in AWS.
8 endpointsJentic publishes the only available OpenAPI specification for AWS Service Catalog App Registry, keeping it validated and agent-ready. App Registry gives organisations a structured repository of their applications, the AWS resources that compose them, and the metadata needed to operate and govern them. Agents can create applications, attach attribute groups that carry custom JSON schemas, associate or disassociate AWS resources, and query the resulting application graph. The 24 operations cover applications, attribute groups, resource associations, sync, and tag management.
24 endpointsJentic publishes the only available OpenAPI specification for AWS Step Functions, keeping it validated and agent-ready. Step Functions coordinates distributed applications and microservices using state machines defined in Amazon States Language (ASL). Agents can create state machines and activities, start standard or express executions, send task success or failure for activity workers, inspect execution history step by step, and run Map runs over large iterables. The 26 operations cover state machines, executions, activities, map runs, and execution history.
26 endpointsJentic publishes the only available OpenAPI specification for Elastic Load Balancing, keeping it validated and agent-ready. Elastic Load Balancing v2 covers Application, Network, and Gateway Load Balancers on AWS. The API manages load balancer creation, listeners, routing rules, target groups, target registration, and health checks across multiple Availability Zones. It is built for platform and SRE teams that need to programmatically expose services, shift traffic between target groups, and roll out blue-green or weighted deployments without console interaction.
68 endpointsJentic publishes the only available OpenAPI specification for Amazon Managed Streaming for Apache Kafka (MSK), keeping it validated and agent-ready. The MSK control plane API has 36 endpoints for provisioning Kafka clusters, managing broker counts, applying broker configurations, attaching SCRAM secrets stored in Secrets Manager, and tracking cluster operations such as version upgrades and storage expansions. It does not handle topic-level produce or consume calls — those run over native Kafka protocol against the broker bootstrap endpoints. MSK is built for teams that want managed brokers, automated patching, and ZooKeeper or KRaft mode without operating the underlying instances themselves.
36 endpointsStep 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 | shStep 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 instanceJentic 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.