You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recommendation is to create a new pattern aws-kinesisstreams-kinesisfirehose-s3(internally it should still make use of aws-kinesisfirehose-s3, similar to aws-iot-kinesisfirehose-s3).
👋 I may be able to implement this feature request
This is a 🚀 Feature Request
The text was updated successfully, but these errors were encountered:
Originally reported on #73
Kinesis Firehose supports two types (DirectPut and KinesisStreamAsSource). As of now, it isn't very straightforward to use KinesisStreamAsSource in the existing
aws-kinesisfirehose-s3
pattern, since the configuration for it (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-kinesisfirehose-deliverystream-kinesisstreamsourceconfiguration.html) requires the customer to pass the ARN of the role that provides access to the source Kinesis data stream (which is not available until after the construct is created).Recommendation is to create a new pattern
aws-kinesisstreams-kinesisfirehose-s3
(internally it should still make use ofaws-kinesisfirehose-s3
, similar toaws-iot-kinesisfirehose-s3
).This is a 🚀 Feature Request
The text was updated successfully, but these errors were encountered: