In order to make your issue reports as actionable as possible, please provide the following information, depending on the issue type.

Bug report

For bug reports, provide this information, please:

What Debezium connector do you use and what version?

Debezium Server, Postgres connector

What is the connector configuration?

DEBEZIUM_SINK_TYPE=kinesis
DEBEZIUM_SINK_KINESIS_REGION=eu-west-2
DEBEZIUM_SOURCE_CONNECTOR_CLASS=io.debezium.connector.postgresql.PostgresConnector
DEBEZIUM_SOURCE_OFFSET_STORAGE_FILE_FILENAME=data/offsets.dat
DEBEZIUM_SOURCE_OFFSET_FLUSH_INTERVAL_MS=0
DEBEZIUM_SOURCE_DATABASE_HOSTNAME=postgres
DEBEZIUM_SOURCE_DATABASE_PORT=5432
DEBEZIUM_SOURCE_DATABASE_USER=postgres
DEBEZIUM_SOURCE_DATABASE_PASSWORD=postgres
DEBEZIUM_SOURCE_DATABASE_DBNAME=postgres
DEBEZIUM_SOURCE_DATABASE_SERVER_NAME=checkstream
DEBEZIUM_SOURCE_PLUGIN_NAME=PGOUTPUT 

What is the captured database version and mode of depoyment?

RDS postgres provisioned 

What behaviour do you expect?

Debezium Server should see ECS task credentials (maybe DefaultCredentialsProvider class?)

What behaviour do you see?

Unable to authorize to Kinesis 

Do you see the same behaviour using the latest relesead Debezium version?

<Your answer>

Do you have the connector logs, ideally from start till finish?

(You might be asked later to provide DEBUG/TRACE level log)

<Your answer>

How to reproduce the issue using our tutorial deployment?

<Your answer>

Feature request or enhancement

For feature requests or enhancements, provide this information, please:

Which use case/requirement will be addressed by the proposed feature?

<Your answer>

Implementation ideas (optional)

Default implementation DefaultCredentialsProvider flexible?