Andrei Neculau

`s3:PutLogEvents` (typo of a `logs:PutLogEvents`) will succeed

deleting a bucket or a firehose requires you to type/paste the resource's name in a confirmation dialog. but not deleting a kinesis stream...

When a stack encounters a failure, if it created a new Firehose resource, it may fail to delete the resource with a message like "Firehose FOO under accountBAR cannot be...

across the entire Console there are intertwined resources, yet only in very few places one can actually get links to jump from one resource to another e.g. Kinesis Firehose links...

Kinesis Firehose (S3) declares BufferingHints, CompressionFormat, Prefix as optional. CloudFormation as required.

one benefit that you buy into when switching to "serverless" cloud architecture is elasticity i.e. just show us the money, and we scale your infrastructure anyway you need. Wrong! Kinesis...

one benefit that you buy into when switching to "serverless" cloud architecture is elasticity i.e. just show us the money, and we scale your infrastructure anyway you need. Wrong! DynamoDB...

as per the docs "Only Amazon S3 buckets that are empty can be deleted. Deletion will fail for buckets that have contents." (even with DeletionPolicy is set to Delete). why...

although there is at least one resource, `AWS::KinesisFirehose::DeliveryStream` (not to mention policy statements), that requires not a bucket name, but a bucket ARN (?!), there's no cloudformation function to get...

`AWS::KinesisFirehose::DeliveryStream` talks about `BucketARN` and `RoleARN`, while `AWS::Lambda::Permission` talks about `SourceArn` and `AWS::Lambda::Function` talks about `Role` (referring to an ARN)