InfraScan Cloud

Repository scan

sequin

sequinstream/sequin · branch main · scanned 17 Feb 2026 · 156 resources

FOverall
FSecurity
–Reliability · N/A
DCost
154findings · 0 critical, 9 high
—no cost findings with a savings estimate

High 9

High Missing AWS Budget Cost · 6 places
High Expensive NAT Gateway Cost · 3 places

NAT Gateways are expensive managed services. Ensure they are strictly necessary.

How to fix

Consider using VPC Endpoints, NAT Instances for non-critical workloads, or share a single NAT Gateway across multiple subnets.

Where

Medium 142

Medium Ensure every security group and rule has a description Security · 14 places
Medium Ensure no security groups allow egress from 0.0.0.0:0 to port -1 Security · 14 places
Medium Ensure that load balancer is using at least TLS 1.2 Security · 6 places
Medium Ensure VPC subnets do not assign public IP by default Security · 6 places
Medium Missing Cost and Usage Report Cost · 6 places

No AWS Cost and Usage Report (CUR) configured. CUR provides detailed cost tracking and analysis.

How to fix

Enable AWS Cost and Usage Reports to track spending patterns and identify optimization opportunities.

Where

Medium Ensure no security groups allow ingress from 0.0.0.0:0 to port 22 Security · 4 places
Medium Ensure VPC flow logging is enabled in all VPCs Security · 3 places
Medium Ensure the default security group of every VPC restricts all traffic Security · 3 places
Medium Ensure that all EIP addresses allocated to a VPC are attached to EC2 instances Security · 3 places
Medium Ensure that ALB redirects HTTP requests into HTTPS ones Security · 3 places
Medium Ensure public facing ALB are protected by WAF Security · 3 places
Medium Ensure Secrets Manager secrets should have automatic rotation enabled Security · 3 places
Medium Ensure KMS key Policy is defined Security · 3 places
Medium Ensure AWS RDS database instance configured with encryption in transit Security · 3 places
Medium Ensure AWS Load Balancers use strong ciphers Security · 3 places
Medium Ensure that enhanced monitoring is enabled for Amazon RDS instances Security · 3 places
Medium Ensure that respective logs of Amazon Relational Database Service (Amazon RDS) are enabled Security · 3 places
Medium Ensure that ALB drops HTTP headers Security · 3 places
Medium Ensure that Secrets Manager secret is encrypted using KMS CMK Security · 3 places
Medium Ensure that Load Balancer has deletion protection enabled Reliability · 3 places
Medium Ensure that RDS instances have Multi-AZ enabled Reliability · 3 places
Medium Ensure that CloudWatch Log Group is encrypted by KMS Security · 3 places
Medium Ensure RDS database has IAM authentication enabled Security · 3 places
Medium Ensure ALB protocol is HTTPS Security · 3 places
Medium Ensure no security groups allow ingress from 0.0.0.0:0 to port 80 Security · 3 places
Medium Ensure all data stored in the SQS queue is encrypted Security · 3 places
Medium Ensure CloudWatch log groups retains logs for at least 1 year Security · 3 places
Medium Ensure AWS Load Balancer doesn't use HTTP protocol Security · 3 places
Medium Ensure container insights are enabled on ECS cluster Security · 3 places
Medium Ensure the ELBv2 (Application/Network) has access logging enabled Security · 3 places
Medium Load Balancer for Single Instance Cost · 3 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 an IAM role is attached to EC2 instance Security · 2 places
Medium Ensure that detailed monitoring is enabled for EC2 instances Security · 2 places
Medium Ensure that EC2 is EBS optimized Security · 2 places
Medium Ensure all data stored in the Launch configuration or instance Elastic Blocks Store is securely encrypted Security · 2 places

Ensure all data stored in the Launch configuration or instance Elastic Blocks Store is securely encrypted

Documentation

Where

Medium EC2 instance should not have public IP. Security · 2 places
Medium Old Generation Storage (gp2) Cost · 2 places

Using gp2 EBS volumes when gp3 provides better performance at lower cost.

How to fix

Migrate from gp2 to gp3 volumes. gp3 offers 20% cost savings and better baseline performance.

Where

Medium Missing Spot Instance Usage Cost · 2 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 that Security Groups are attached to another resource Security · 1 place

Ensure that Security Groups are attached to another resource

Documentation

Where

Medium Ensure access is controlled through SSO and not AWS IAM defined users Security · 1 place

Ensure access is controlled through SSO and not AWS IAM defined users

Documentation

Where

and 1 more groups with 1 findings

Low 3

Low Elastic IP Usage Cost · 3 places

Elastic IPs are charged if not attached to a running instance or if you have more than one per instance.

How to fix

Release unattached Elastic IPs.

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 17 Feb 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.