InfraScan Cloud

Repository scan

mattermost-cloud-monitoring

mattermost/mattermost-cloud-monitoring · branch main · scanned 25 Jun 2026 · 1,158 resources

FOverall
FSecurity
–Reliability · N/A
DCost
788findings · 0 critical, 17 high
$848–$1,408estimated savings per month, from the code

High 17

High Expensive NAT Gateway Cost · 16 places
High RDS Old Generation Instance Cost · 1 place

Usage of old generation RDS instance classes (db.t2, db.m3, db.m4, db.r3, db.r4). Newer generations are cheaper and faster.

How to fix

Upgrade to current generation instance classes (e.g., db.t3, db.m5, db.r5, db.r6g).

Where

Medium 752

Medium Ensure no security groups allow egress from 0.0.0.0:0 to port -1 Security · 48 places
Medium Ensure no IAM policies documents allow "*" as a statement's resource for restrictable actions Security · 46 places
Medium Ensure every security group and rule has a description Security · 38 places
Medium Ensure IAM policies does not allow write access without constraints Security · 36 places
Medium Ensure Terraform module sources use a commit hash Security · 31 places
Medium Ensure that Security Groups are attached to another resource Security · 27 places
Medium Ensure that an S3 bucket has a lifecycle configuration Security · 19 places
Medium Ensure S3 buckets should have event notifications enabled Security · 19 places
Medium Ensure that AWS Lambda function is configured for function-level concurrent execution limit Security · 19 places
Medium Ensure that AWS Lambda function is configured for a Dead Letter Queue(DLQ) Security · 19 places
Medium Ensure the S3 bucket has access logging enabled Security · 19 places
Medium Ensure AWS Lambda function is configured to validate code-signing Security · 19 places
Medium Ensure IAM policies are attached only to groups or roles (Reducing access management complexity may in-turn reduce opportunity for a principal to inadvertently receive or retain excessive privileges.) Security · 19 places
Medium Ensure that S3 bucket has a Public Access block Security · 18 places
Medium Check encryption settings for Lambda environmental variable Security · 18 places
Medium Ensure that S3 bucket has cross-region replication enabled Security · 17 places
Medium Ensure Instance Metadata Service Version 1 is not enabled Security · 17 places
Medium Missing S3 Lifecycle Policy Cost · 17 places
Medium X-Ray tracing is enabled for Lambda Security · 14 places
Medium Multiple NAT Gateways (Potential Redundancy) Cost · 13 places

More than one aws_nat_gateway defined. In development or staging environments a single NAT Gateway is usually sufficient; multiple gateways add ~$32/month each plus data-processing fees.

How to fix

Verify that each additional NAT Gateway is needed for HA in production. For dev/staging environments consider consolidating to a single gateway.

Where

Medium Ensure access is controlled through SSO and not AWS IAM defined users Security · 12 places
Medium Ensure an IAM role is attached to EC2 instance Security · 9 places
Medium Ensure IAM policies does not allow permissions management / resource exposure without constraints Security · 9 places
Medium Ensure that detailed monitoring is enabled for EC2 instances Security · 8 places
Medium Ensure that EC2 is EBS optimized Security · 8 places
Medium Ensure no security groups allow ingress from 0.0.0.0:0 to port 22 Security · 8 places
Medium Missing Cost and Usage Report Cost · 8 places
Medium Load Balancer for Single Instance Cost · 8 places

Load balancer detected. Verify it's needed - load balancers cost $15-20/month even if unused.

How to fix

Consider if load balancer is necessary for single-instance deployments or low-traffic applications.

Where

Medium Ensure that S3 buckets are encrypted with KMS by default Security · 7 places
Medium Ensure DB instance gets all minor upgrades automatically Security · 7 places
Medium Ensure all data stored in the Launch configuration or instance Elastic Blocks Store is securely encrypted Security · 7 places
Medium Ensure all data stored in the SNS topic is encrypted Security · 6 places
Medium Ensure no security groups allow ingress from 0.0.0.0:0 to port 80 Security · 6 places
Medium Missing Spot Instance Usage Cost · 6 places

No spot instances detected. Spot instances can save 50-90% on compute costs for interruptible workloads.

How to fix

Use spot instances for batch jobs, data analysis, and optional tasks. Consider aws_spot_instance_request or spot_price in launch templates.

Where

Medium Ensure AWS API gateway request is validated Security · 5 places
Medium Ensure Secrets Manager secrets should have automatic rotation enabled Security · 5 places
Medium Ensure that RDS clusters has backup plan of AWS Backup Reliability · 5 places
Medium Ensure that AWS Lambda function is configured inside a VPC Security · 5 places
Medium Ensure that Secrets Manager secret is encrypted using KMS CMK Security · 5 places
Medium Ensure that CloudWatch Log Group is encrypted by KMS Security · 5 places

and 73 more groups with 140 findings

Low 19

Low Unassociated Elastic IP Cost · 18 places
Low Large Root Volume Cost · 1 place

Oversized root block device. Many workloads don't require large root volumes.

How to fix

Reduce root volume size to minimum required (typically 8-20 GB for most Linux instances).

Where

Grades use InfraScan Cloud's current formula, so they can differ from the ones first shown for this scan. Findings reflect the repository on 25 Jun 2026; it may have changed since.

Scan your own repository

InfraScan Cloud scans your repositories and AWS accounts, keeps the history and shows how to fix each finding.