AWS Injector Failed to Push: Troubleshooting Kinesis

The AWS Injector failure moved between services after module upgrades: version 4.0.20 restored DynamoDB connectivity but Kinesis pushes failed with a Java class-cast exception. Downgrading to 4.0.18 removed the Kinesis exception but brought back the DynamoDB disconnection. The evidence therefore supports a version-dependent module defect or incompatibility, not an AWS credential failure.

Identify the Kinesis push failure

On Ignition 8.1.35 with AWS Injector 4.0.20, the push path attempts to cast KinesisFirehoseIngestService to KinesisIngestService. Java rejects that cast, and execution stops in AbstractKinesisIngestService.push before AWS Injector can complete the push.

java.lang.ClassCastException:
class com.cirruslink.ingest.kinesis.KinesisFirehoseIngestService
cannot be cast to class com.cirruslink.ingest.kinesis.KinesisIngestService

at com.cirruslink.ingest.kinesis.AbstractKinesisIngestService.push(
    AbstractKinesisIngestService.java:269)
at com.cirruslink.injector.aws.gateway.AwsInjectorSettings$1.push(
    AwsInjectorSettings.java:161)

This trace identifies an internal Java type mismatch. It does not establish whether the trigger is a specific Kinesis configuration, a module defect, or an interaction with another component.

Compare the observed version behavior

Version 4.0.18 and 4.0.20 exchange one observed failure for another. The evidence does not identify a version that supports both DynamoDB and Kinesis successfully in this environment.

Isolate and verify the failure

1. Record the Ignition and AWS Injector versions before changing the installation. Preserve the complete exception, including the service classes and stack locations.
2. On 4.0.20, initiate the affected Kinesis push and confirm whether the log reports the cast from KinesisFirehoseIngestService to KinesisIngestService.
3. Check DynamoDB separately and verify that it remains connected rather than reporting Connected followed by Disconnected.
4. If evaluating 4.0.18 as a temporary Kinesis workaround, retest DynamoDB because that version removed the observed Kinesis error but restored the DynamoDB failure.
5. Escalate the version matrix and full stack trace through the module vendor's official support channel. Request a compatible release or confirmed workaround that addresses both service paths.

Upgrading Ignition to 8.1.35, installing AWS Injector 4.0.20, restarting the EC2 instance, and testing a clean Ignition installation with module 4.0.20 did not eliminate the reported push problem. Repeating those changes without a different module build or configuration hypothesis is therefore unlikely to add diagnostic value.

FAQ