AWS Amazon Kinesis Analytics

Name: Amazon Kinesis Analytics API
Brand: Amazon Kinesis Analytics
Availability: InStock

★ Only Publicly Available OpenAPI DocumentAnalyticsData Pipelineshmac20 Endpoints

Install Jentic One Beta

Connect the Amazon Kinesis Analytics to your agent

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

Create SQL streaming applications via CreateApplication

Configure inputs from Kinesis Data Streams or Firehose with AddApplicationInput

Add reference data from S3 with AddApplicationReferenceDataSource

GET STARTED

Start building with Amazon Kinesis Analytics API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Amazon Kinesis Analytics API for, with concrete tasks.

★ Real-Time Fraud Signals

Run continuous SQL queries over a transaction event stream to flag anomalous patterns in seconds. The Kinesis Analytics application reads from a Kinesis Data Stream, joins reference data from S3, and emits alerts to a downstream Firehose or Lambda output. Teams use this to detect velocity violations, dollar-amount thresholds, and other rule-based anomalies without writing Flink jobs.

Create application 'fraud-rules' with SQL that flags transactions where amount > 10000 from input stream txn-events

Stream Aggregation for Dashboards

Aggregate a high-volume event stream into per-minute metrics for live dashboards. Kinesis Analytics supports tumbling and sliding windows in SQL, which makes it straightforward to compute count, sum, and average over time windows and write the results into a destination stream that powers a near-real-time dashboard or alerting system.

Create an application that emits per-minute counts of input stream click-events to output stream click-counts using a tumbling window

Schema Discovery for Pipelines

Bootstrap a new streaming pipeline by discovering the schema of an input stream automatically. The DiscoverInputSchema operation samples records from a Kinesis stream and infers column names, types, and record format, which speeds up onboarding new event sources and reduces manual SQL configuration mistakes.

Run DiscoverInputSchema against stream txn-events with role arn:aws:iam::123:role/kinesis-analytics-discovery and return the inferred columns

AI Agent Streaming Pipeline Operations

AI agents call Kinesis Analytics through Jentic to create new applications when teams onboard event sources, start and stop applications based on cost guards, and inspect schemas before configuring downstream consumers. Through Jentic, the agent searches by intent, loads the operation schema, and executes with credentials stored in the vault. SigV4 signing happens inside Jentic so the agent runtime stays slim.

Search Jentic for 'start kinesis analytics application', load the StartApplication schema, and execute against application 'fraud-rules'

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/#X-Amz-Target=KinesisAnalytics_20150814.CreateApplication

Create a streaming SQL application

POST

/#X-Amz-Target=KinesisAnalytics_20150814.StartApplication

Start an application

POST

/#X-Amz-Target=KinesisAnalytics_20150814.StopApplication

Stop a running application

POST

/#X-Amz-Target=KinesisAnalytics_20150814.AddApplicationInput

Configure an input stream

POST

/#X-Amz-Target=KinesisAnalytics_20150814.AddApplicationOutput

Configure an output destination

POST

/#X-Amz-Target=KinesisAnalytics_20150814.DiscoverInputSchema

Auto-discover the schema of a stream

POST

/#X-Amz-Target=KinesisAnalytics_20150814.CreateApplication

Create a streaming SQL application

POST

/#X-Amz-Target=KinesisAnalytics_20150814.StartApplication

Start an application

POST

/#X-Amz-Target=KinesisAnalytics_20150814.StopApplication

Stop a running application

POST

/#X-Amz-Target=KinesisAnalytics_20150814.AddApplicationInput

Configure an input stream

POST

/#X-Amz-Target=KinesisAnalytics_20150814.AddApplicationOutput

Configure an output destination

Why Jentic?

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

Credential isolation

Your AWS access key and secret for Kinesis Analytics are stored once, encrypted, by your own Jentic One instance and signed 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 'create a streaming sql application over a kinesis stream' or 'start a kinesis analytics application', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without reading the AWS reference.

Time to first call

FAQs

Specific to using Amazon Kinesis Analytics API through Jentic.

Why is there no official OpenAPI spec for Amazon Kinesis Analytics?

AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Amazon Kinesis Analytics 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 the Kinesis Analytics API use?

Kinesis Analytics uses AWS Signature Version 4 (SigV4) HMAC request signing. Each call must be signed with an access key, secret key, and optional session token scoped to the kinesisanalytics IAM service. Through Jentic, these credentials sit in the encrypted vault and signing happens at execution time.

Can I run streaming SQL with the Kinesis Analytics API?

Yes. CreateApplication accepts an ApplicationCode field containing your SQL, plus input and output configurations that wire the application to Kinesis Data Streams, Firehose, or Lambda. The service handles parsing, scheduling, and scaling automatically.

How do I start a streaming application through Jentic?

Search Jentic for 'start kinesis analytics application', load the StartApplication schema, submit the application name and an InputConfiguration with the InputId and starting position, and Jentic will sign and execute the call.

What are the rate limits for the Kinesis Analytics API?

Per-region quotas apply, including a default cap on applications per account and TPS limits on control plane operations such as CreateApplication and DescribeApplication. Check the Kinesis Analytics service quotas in the AWS console for current values.

Can the Kinesis Analytics API discover an input schema automatically?

Yes. DiscoverInputSchema samples records from a Kinesis Data Stream or Firehose using a supplied IAM role and returns the inferred record format and column list. Use this before configuring AddApplicationInput so the schema is correct on the first attempt.

How does Kinesis Analytics differ from Kinesis Data Analytics for Apache Flink?

This API covers the v1 SQL-based service. AWS also offers a separate Kinesis Data Analytics for Apache Flink service for Java, Scala, and Python applications. Pick the SQL service for simple windowed transforms; pick Flink for stateful processing and custom code.

Can I limit what my agent is allowed to do with the Kinesis Analytics API?

Yes. Because you run Jentic One yourself, your own rules decide which Kinesis Analytics operations and AWS credentials the agent can use. Since this is an X-Amz-Target RPC API where the application name and configuration travel in the request body, you can restrict the agent to only the operations it needs, such as DescribeApplication or DiscoverInputSchema. Destructive operations like DeleteApplication or StopApplication are excluded unless you explicitly add them.

AWS Amazon Kinesis Analytics

Connect the Amazon Kinesis Analytics to your agent

Capabilities

Start building with Amazon Kinesis Analytics API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs