InfraScan Cloud

Repository scan

artemis

WarnerMedia/artemis · branch main · scanned 18 Feb 2026 · 461 resources

DOverall
FSecurity
–Reliability · N/A
CCost
474findings · 0 critical, 13 high
—no cost findings with a savings estimate

High 13

High Missing AWS Budget Cost · 11 places
High Expensive NAT Gateway Cost · 2 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 459

Medium Ensure that AWS Lambda function is configured for function-level concurrent execution limit Security · 42 places
Medium Ensure that AWS Lambda function is configured for a Dead Letter Queue(DLQ) Security · 42 places
Medium Check encryption settings for Lambda environmental variable Security · 42 places
Medium Ensure AWS Lambda function is configured to validate code-signing Security · 42 places
Medium X-Ray tracing is enabled for Lambda Security · 42 places
Medium Ensure AWS API gateway request is validated Security · 37 places
Medium Ensure Secrets Manager secrets should have automatic rotation enabled Security · 25 places
Medium Ensure that Secrets Manager secret is encrypted using KMS CMK Security · 24 places
Medium Ensure all data stored in the SQS queue is encrypted Security · 15 places
Medium Ensure that ECR repositories are encrypted using KMS Security · 11 places
Medium Ensure ECR image scanning on push is enabled Security · 11 places
Medium Ensure ECR Image Tags are immutable Security · 11 places
Medium Missing Cost and Usage Report Cost · 11 places
Medium Ensure every security group and rule has a description Security · 7 places
Medium Ensure that AWS Lambda function is configured inside a VPC Security · 6 places
Medium Ensure that an S3 bucket has a lifecycle configuration Security · 5 places
Medium Ensure S3 buckets should have event notifications enabled Security · 5 places
Medium Ensure that S3 bucket has cross-region replication enabled Security · 5 places
Medium Ensure that S3 buckets are encrypted with KMS by default Security · 4 places
Medium Ensure that CloudWatch Log Group is encrypted by KMS Security · 4 places
Medium Ensure the S3 bucket has access logging enabled Security · 4 places
Medium Ensure CloudWatch log groups retains logs for at least 1 year Security · 4 places
Medium Missing S3 Lifecycle Policy Cost · 4 places

S3 bucket without lifecycle rules. Objects are retained indefinitely, increasing storage costs.

How to fix

Define lifecycle rules to transition objects to cheaper storage classes (e.g., Glacier) or delete them after a retention period.

Where

Medium Ensure WAF2 has a Logging Configuration Security · 3 places
Medium Ensure access control lists for S3 buckets are disabled Security · 3 places
Medium Ensure WAF prevents message lookup in Log4j2. See CVE-2021-44228 aka log4jshell Security · 3 places
Medium Ensure no IAM policies documents allow "*" as a statement's resource for restrictable actions Security · 3 places
Medium Ensure VPC flow logging is enabled in all VPCs Security · 2 places
Medium Ensure the default security group of every VPC restricts all traffic Security · 2 places
Medium Ensure API Gateway stage have logging level defined as appropriate Security · 2 places
Medium Ensure AWS API Gateway endpoints uses client certificate authentication Security · 2 places
Medium Ensure that S3 bucket has a Public Access block Security · 2 places
Medium Ensure AWS API Gateway Rest API attached WAFv2 WebACL is configured with AMR for Log4j Vulnerability Security · 2 places

Ensure AWS API Gateway Rest API attached WAFv2 WebACL is configured with AMR for Log4j Vulnerability

How to fix

See Checkov documentation for remediation guidance.

Where

Medium Ensure API Gateway caching is enabled Security · 2 places
Medium Ensure API Gateway Domain uses a modern security Policy Security · 2 places
Medium Ensure Create before destroy for API deployments Security · 2 places
Medium Ensure Create before destroy for API Gateway Security · 2 places
Medium Ensure Launch template should not have a metadata response hop limit greater than 1 Security · 2 places
Medium Ensure API Gateway has X-Ray Tracing enabled Security · 2 places
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

and 18 more groups with 18 findings

Low 2

Low Elastic IP Usage Cost · 2 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 18 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.