Won Kim

Got the same issue and solved by adding `streamName` property under stream event. But I'm not sure it is a good or bad approach. Or, it can be solved by...

@medikoo I wrote an example configuration. input sls template ```yaml resources: Resources: MyPipe: Type: AWS::Pipes::Pipe Properties: RoleArn: !Ref AllowSendingToTargetRole Source: !Ref MyTable Target: !Ref MyEventBus ``` output CF template ```json...

@medikoo Here are configurations, not required but should be supported to use EventBrigePipe full features: - SourceParameter (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-pipes-pipe-pipesourceparameters.html) - TargetParameter (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-pipes-pipe-pipetargetparameters.html) - Enrichment - EnrichmentParameter (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-pipes-pipe-pipeenrichmentparameters.html)