Skip to content

DynamoDBStreamReadPolicy is cumbersome to work with #289

@iamatypeofwalrus

Description

@iamatypeofwalrus

Hi!

I'm spinning up a toy Go lambda that reads stream events from a DynamoDB table. Both are specified in the same CloudFormation template.

The DynamoDBStreaReadPolicy requires the table name and a stream name. It looks like it's constructing the StreamArn under the hood.

The DynamoDB table resource already includes a return value for the StreamArn but it doesn't look like it gives access to the stream's name. Given that it's some sort of timestamp it looks like it will be difficult to infer the stream name without creating the stream first.

Can the DynamoDBStreaReadPolicy be updated to accept the StreamArn directly?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions