Amazon AppFlow moves data between SaaS applications and AWS services without writing custom integration code. It supports scheduled, event-driven, and on-demand flows, with built-in connectors for Salesforce, Slack, Zendesk, ServiceNow, Marketo, S3, Redshift, and more.
23 endpointsAmazon Athena is an interactive query service that runs standard SQL against data stored in Amazon S3 without provisioning infrastructure. It supports federated queries to other data sources, parameterised prepared statements, named saved queries, and managed workgroups for cost and access control.
60 endpointsJentic publishes the only available OpenAPI specification for Amazon Kinesis Analytics, keeping it validated and agent-ready. Kinesis Analytics is the v1 SQL-based service for running continuous queries over streaming data from Kinesis Data Streams or Kinesis Firehose. Its 20-endpoint API covers application creation, input and output configuration, reference data sources, CloudWatch logging options, schema discovery, and lifecycle controls to start and stop applications. The service is suited to teams running SQL transformations on event streams without standing up Spark or Flink clusters themselves.
20 endpointsJentic publishes the only available OpenAPI specification for Amazon Mobile Analytics, keeping it validated and agent-ready. Amazon Mobile Analytics is a lightweight event-collection endpoint for mobile applications — apps batch user events on the device and POST them to a single PutEvents endpoint with a per-call x-amz-Client-Context header that identifies the app, version and device. AWS has since folded this surface into Amazon Pinpoint, but the legacy ingest endpoint remains callable for apps that have not yet migrated.
1 endpointsJentic publishes the only available OpenAPI specification for Amazon Timestream Query, keeping it validated and agent-ready. Amazon Timestream Query is the read-and-schedule API for Amazon Timestream, AWS's serverless time-series database. It runs SQL queries against memory and magnetic stores, prepares parameterised queries, and manages scheduled queries that pre-compute aggregations on a cron-like schedule. The 13 operations cover ad-hoc Query and CancelQuery, the full lifecycle of scheduled queries, endpoint discovery, and resource tagging.
13 endpointsJentic publishes the only available OpenAPI specification for AWS Data Pipeline, keeping it validated and agent-ready. AWS Data Pipeline configures and runs data-driven workflows that move and transform data between AWS services and on-premises sources. The API manages pipeline definitions, activations, task runners, and validation. AWS announced Data Pipeline as legacy in 2023 and recommends Step Functions, Glue Workflows, or MWAA for new work, but the API is still available for existing pipelines.
19 endpointsJentic publishes the only available OpenAPI specification for AWS Glue DataBrew, keeping it validated and agent-ready. AWS Glue DataBrew is a visual data preparation service for analysts and data scientists. The API manages datasets, projects, recipes (transformations), recipe jobs, profile jobs, schedules, and rulesets that enforce data quality. Recipes capture hundreds of cleaning, transformation, and feature-engineering steps as code, and jobs apply them at scale to data in S3, Redshift, Snowflake, and JDBC sources.
44 endpointsJentic publishes the only available OpenAPI specification for the Amazon Redshift Data API, keeping it validated and agent-ready. The Redshift Data API runs asynchronous SQL against provisioned Redshift clusters and Redshift Serverless workgroups over HTTPS without persistent connections. Ten operations cover statement execution, batch execution, statement status and result fetch, table and schema discovery, and statement listing. It is the primary interface for analytical queries from Lambda, Step Functions, and AI agents that need ad-hoc access to a warehouse without ODBC or JDBC.
10 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.