Skip to content

Merge pull request #141 from damzempire/feature/high-volume-transacti… #104

Merge pull request #141 from damzempire/feature/high-volume-transacti…

Merge pull request #141 from damzempire/feature/high-volume-transacti… #104

Triggered via push April 24, 2026 13:20
Status Failure
Total duration 31s
Artifacts

terraform.yml

on: push
Matrix: Terraform Validate
Security Check
27s
Security Check
Matrix: terraform-plan
Infrastructure Test
0s
Infrastructure Test
Cost Estimation
0s
Cost Estimation
Matrix: terraform-apply
Fit to window
Zoom out
Zoom in

Annotations

18 errors and 4 warnings
Terraform Validate (dev)
Process completed with exit code 1.
Terraform Validate (dev)
Terraform exited with code 3.
Terraform Validate (prod)
The strategy configuration was canceled because "terraform-validate.dev" failed
Terraform Validate (prod)
Process completed with exit code 1.
Terraform Validate (prod)
Terraform exited with code 3.
Terraform Validate (staging)
The strategy configuration was canceled because "terraform-validate.dev" failed
Terraform Validate (staging)
Process completed with exit code 1.
Terraform Validate (staging)
Terraform exited with code 3.
Security Check
CKV_AWS_26: "Ensure all data stored in the SNS topic is encrypted"
Security Check
CKV_AWS_158: "Ensure that CloudWatch Log Group is encrypted by KMS"
Security Check
CKV_AWS_157: "Ensure that RDS instances have Multi-AZ enabled"
Security Check
CKV_AWS_226: "Ensure DB instance gets all minor upgrades automatically"
Security Check
CKV_AWS_118: "Ensure that enhanced monitoring is enabled for Amazon RDS instances"
Security Check
CKV_AWS_354: "Ensure RDS Performance Insights are encrypted using KMS CMKs"
Security Check
CKV_AWS_382: "Ensure no security groups allow egress from 0.0.0.0:0 to port -1"
Security Check
CKV_AWS_355: "Ensure no IAM policies documents allow "*" as a statement's resource for restrictable actions"
Security Check
CKV_AWS_288: "Ensure IAM policies does not allow data exfiltration"
Security Check
CKV_AWS_31: "Ensure all data stored in the ElastiCache Replication Group is securely encrypted at transit and has auth token"
Terraform Validate (dev)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, hashicorp/setup-terraform@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Terraform Validate (prod)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, hashicorp/setup-terraform@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Terraform Validate (staging)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, hashicorp/setup-terraform@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Security Check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/