fix default behaviour when not aws_sns_topic does not exist #27
RenatovnctavaresAnnotations
10 errors and 1 warning
|
scan:
alarms.tf#L10
CKV_AWS_124: "Ensure that CloudFormation stacks are sending event notifications to an SNS topic"
|
|
scan:
iam.tf#L19
CKV_AWS_290: "Ensure IAM policies does not allow write access without constraints"
|
|
scan:
iam.tf#L19
CKV_AWS_355: "Ensure no IAM policies documents allow "*" as a statement's resource for restrictable actions"
|
|
scan:
main.tf#L1
CKV_AWS_117: "Ensure that AWS Lambda function is configured inside a VPC"
|
|
scan:
main.tf#L1
CKV_AWS_173: "Check encryption settings for Lambda environmental variable"
|
|
scan:
main.tf#L1
CKV_AWS_272: "Ensure AWS Lambda function is configured to validate code-signing"
|
|
scan:
main.tf#L1
CKV_AWS_115: "Ensure that AWS Lambda function is configured for function-level concurrent execution limit"
|
|
scan:
main.tf#L1
CKV_AWS_116: "Ensure that AWS Lambda function is configured for a Dead Letter Queue(DLQ)"
|
|
scan:
main.tf#L32
CKV_AWS_158: "Ensure that CloudWatch Log Group is encrypted by KMS"
|
|
scan:
sns.tf#L4
CKV_AWS_26: "Ensure all data stored in the SNS topic is encrypted"
|
|
scan
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|