Do not allow action “*” or resources “*” in an IOT Policy

Example policies are here: https://docs.aws.amazon.com/iot/latest/developerguide/example-iot-policies.html

https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-iot-policy.html
https://www.terraform.io/docs/providers/aws/r/iot_policy.html

cfn-lint version: 0.38.0

CloudFormation Lambda functions with inline code (through the {"Code": {"ZipFile": "...."}} property, or with SAM functions with the InlineCode property) have a size limit of 4096 bytes enforced by CloudFormation. It would be very helpful if cfn-lint could warn about crossing this threshold, since it's difficult to measure the code size in bytes in the text editor

While testing another PR, I found that mu pipeline logs command displays information from the pipelines, but also shows this error:

$ mu pipeline logs
[... normal, expected output ...]
func1 ▶ ERROR  ResourceNotFoundException: The specified log group does not exist.
	status code: 400, request id: f7260741-7f69-4772-b4cc-7c6a9c22d264

This error does not occur with the `-f

Good summary at https://matthewdf10.medium.com/how-to-enable-logging-on-every-aws-service-in-existence-circa-2021-5b9105b87c9 and https://docs.google.com/spreadsheets/d/1DBmCXX1irJvxdewa85p5nSsYEf3tpSKWBbwp700mbzs/edit#gid=0

Amazon Aurora
https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-rds-dbcluster.html#cfn-rds-dbcluster-enablecloudwatchlogsexports

AWS AppSync

Seems like we can encrypt environment variables effectively for free by adding a KmsKeyArn property to functions. See: https://github.com/awslabs/serverless-application-model/blob/master/versions/2016-10-31.md

This would be an easy contribution for a first timer...

Add error handling during credentials onChange event so that the Scan Account feature does not activate if credentials are invalid

The current behavior of --interactive is that any new stacks will get created, without any prompt. But this can be potentially dangerous (or at the very least, annoying) if you accidentally make a change, like changing the stack name, resulting in a whole new stack getting created.

Should stacker prompt you before creating a stack when using --interactive mode?