Amazon Kinesis to Databricks

fa source inspect kinesis
fa source plan kinesis --variant kinesis_data_streams
fa source plan kinesis --variant kinesis_firehose --json

Inventory streams, shards, schemas, consumer applications, Firehose destinations, retention, IAM, producers, and downstream consumers. Run checkpointed shard reads, enhanced fan-out, or delivery-file ingestion from a recorded sequence boundary and retain checkpoint, restart, lag, throughput, and reconciliation evidence.

Independent validation covers sequence continuity, event loss and duplicates, partition-key ordering, schema compatibility, resharding, business aggregates, and accepted latency or throughput thresholds. Producer aggregation, consumer lease state, Firehose transforms, and cross-stream ordering remain explicit residue.

Airlift freezes the exact streams and consumers, enforces separation of duties, and records a checkpointed switch, verification, or rollback. Structured Streaming, Lakeflow, Delta event tables, Unity Catalog, and streaming tables are modernized in a separate release.

The pack is cataloged pending live adapter and scale evidence.

Complete developer command sequence

Generate this exact recipe from the installed CLI so the guide and executable surface stay in sync:

fa source recipe kinesis
fa source recipe kinesis --variant kinesis_data_streams --json > .airlift/kinesis-recipe.json

The App is engagement-aware. Amazon Kinesis appears under Active sources only after the source estate is added to an active engagement. The menu is derived from governed engagement scope; installing Airlift does not expose unrelated source pages.

Every remote mutation below requires --host, --org, authenticated workspace identity, and a stable --idempotency-key. JSON request files contain identifiers, artifact references, and opaque credential references—never passwords, tokens, or connection strings. Run fa <resource> <operation> --help for the current schema and exit semantics.

0. Inspect the source contract

fa source inspect kinesis --json > .airlift/kinesis-profile.json
fa source plan kinesis --variant kinesis_data_streams --json > .airlift/kinesis-capability-plan.json

Expected artifacts:

• .airlift/kinesis-profile.json
• .airlift/kinesis-capability-plan.json

Open Engagements → active engagement in the App. This stage is visible at /engagements after replacing the placeholder ID with the governed engagement ID.

1. Create governed scope and connection references

fa engagement create --file engagement.json --idempotency-key migration-create-v1
fa estate register --file kinesis-estate.json --idempotency-key kinesis-estate-v1
fa connection register --file kinesis-connection.json --idempotency-key kinesis-connection-v1
fa engagement update --file kinesis-scope.json --idempotency-key kinesis-scope-v1
fa engagement preflight <engagement-id>

Expected artifacts:

• Governed engagement
• Source estate
• Opaque connection binding

Open Engagements → active engagement in the App. This stage is visible at /engagements/<engagement-id> after replacing the placeholder ID with the governed engagement ID.

2. Assess and accept inventory

fa assessment start --file kinesis-assessment-start.json --idempotency-key kinesis-assessment-start-v1
fa assessment status <assessment-id> --json
fa assessment record --file kinesis-assessment-record.json --idempotency-key kinesis-assessment-record-v1
fa assessment accept --file kinesis-assessment-accept.json --idempotency-key kinesis-assessment-accept-v1
fa inventory list --estate-id <estate-id> --json

Expected artifacts:

• Assessment report reference
• Normalized inventory
• Dependency graph

Open Engagements → active engagement in the App. This stage is visible at /engagements/<engagement-id>/sources/kinesis after replacing the placeholder ID with the governed engagement ID.

3. Implement the admitted source adapter

No source-specific executable compiler exists in this release. Continue with assessment, governed work, and an admitted adapter; Airlift does not invent executable output.

Expected artifacts:

• Capability plan and adapter requirements only

Open Engagements → active engagement in the App. This stage is visible at /engagements/<engagement-id>/artifacts after replacing the placeholder ID with the governed engagement ID.

This source is cataloged or assessable but has no source-specific executable compiler in the installed Airlift generation.

4. Convert, move, and remediate

fa plan generate --file kinesis-migration-plan.json --idempotency-key kinesis-plan-v1
fa conversion batch create --file kinesis-batch.json --idempotency-key kinesis-batch-v1
fa conversion batch start --file conversion-batch-start.json --idempotency-key conversion-start-v1
fa residue list --engagement-id <engagement-id>
fa transfer plan --file kinesis-transfer.json --idempotency-key kinesis-transfer-v1
fa transfer run <transfer-id> --idempotency-key transfer-run-v1
fa transfer reconcile <transfer-id> --idempotency-key transfer-reconcile-v1

Expected artifacts:

• Target artifacts
• Residue cases
• Transfer checkpoints
• Reconciliation evidence

Open Engagements → active engagement in the App. This stage is visible at /engagements/<engagement-id>/runs after replacing the placeholder ID with the governed engagement ID.

5. Validate independently and inspect discrepancies

fa validation run --file kinesis-validation.json --idempotency-key kinesis-validation-v1
fa validation status <validation-execution-id> --json
fa discrepancy list --engagement-id <engagement-id>
fa artifact list --engagement-id <engagement-id>

Expected artifacts:

• Provider run references
• Readiness evidence
• Discrepancies

Open Engagements → active engagement in the App. This stage is visible at /engagements/<engagement-id>/runs after replacing the placeholder ID with the governed engagement ID.

6. Certify, cut over, and export evidence

fa certificate list --object-id <object-id>
fa cutover status <wave-id> --json
fa evidence list --engagement-id <engagement-id>
fa evidence export --file kinesis-evidence-export.json --idempotency-key kinesis-evidence-export-v1

Expected artifacts:

• Migration certificates
• Cutover evidence
• Content-digested evidence export

Open Engagements → active engagement in the App. This stage is visible at /assurance after replacing the placeholder ID with the governed engagement ID.

Runway executes releases; Experiments owns validation verdicts; Airlift owns migration readiness and cutover policy.

What developers see in the App

The contextual source workspace shows the accepted estate and the factory stages for this engagement. Artifacts displays immutable references, content digests, media types, and provider lineage. Runs displays assessment, conversion, transfer, validation, and deployment executions without treating a provider's success as an Airlift verdict.

View full size

These are automated captures from public synthetic engagements. The source workspace is specific to Amazon Kinesis; no unrelated source is presented as its migration journey. For sources without an evidence-backed journey, the image demonstrates setup, navigation, and developer entry points only—not a live connection, converted output, or certified migration. No client data, credentials, workspace hostnames, or internal deployment identifiers are embedded in the images.