Skip to main content
AWS Multi-Resource Optimizer

AWS Orphaned NetworkIngredient Bisque

Professional AWS cost optimization tool that identifies orphaned EBS volumes, Elastic IPs, Load Balancers, and NAT Gateways. Save $200-$24,000+ annually by eliminating forgotten cloud ingredients bleeding your budget.

$200-$24K+ Annual Savings
4 Resource Types
Multi-Region Scanning
Quick Ingredient Hunt
# Basic scan of all AWS regions
.\AWS-Orphaned-Network-Ingredient-Bisque.ps1

# Custom output location
.\AWS-Orphaned-Network-Ingredient-Bisque.ps1 -OutputPath"C:\Reports\AWS_Waste.html"

# Specific regions only
.\AWS-Orphaned-Network-Ingredient-Bisque.ps1 \
 -AllRegions:$false \
 -RegionNames @("us-east-1","us-west-2")

# Custom AWS profile
.\AWS-Orphaned-Network-Ingredient-Bisque.ps1 -AwsProfile"production"
Blaze
Blaze says:NAT Gateways are the sneakiest cost on this list -- $32/month each and they love to hide in forgotten VPCs. If this script finds even two orphaned NATs, it's already saved you $775/year. Run it across all regions, not just your primary one.

Ingredient hunt quick start

Structured quick-reference sections for prerequisites, installation, usage, and troubleshooting.

Prerequisites

  • PowerShell 5.1+ or PowerShell Core
  • AWS CLI installed and authenticated (`aws configure` or profile-based auth)
  • Read-only IAM permissions for EBS, Elastic IPs, Load Balancers, and NAT Gateways
  • Local report output path for HTML/CSV files

Standard ingredient hunt workflow

  1. 1Run an all-region baseline scan to capture hidden waste outside your primary region.
  2. 2Review findings by resource type and annualized savings, starting with NAT Gateways and idle load balancers.
  3. 3Use region scoping or AWS profile selection for targeted follow-up in specific accounts/environments.
  4. 4Validate dependencies before deleting resources (EBS attachments, LB targets, networking paths).
PowerShell
.\\AWS-Orphaned-Network-Ingredient-Bisque.ps1
PowerShell
.\\AWS-Orphaned-Network-Ingredient-Bisque.ps1 -OutputPath "C:\\Reports\\AWS_Waste.html"
PowerShell
.\\AWS-Orphaned-Network-Ingredient-Bisque.ps1 -AllRegions:$false -RegionNames @("us-east-1","us-west-2") -AwsProfile "production"

Resource types and cost signals

ResourceWaste signalTypical cost signal
EBS volumesUnattached volumes$0.08-$0.10/GB/month
Elastic IPsUnassociated static IPs$3.65/month each
Load BalancersNo targets / idle balancers$16.20-$18.00/month
NAT GatewaysForgotten gateways in unused VPCs$32.40/month each

Report output usage

OutputUse casePrimary audience
HTML reportExecutive/stakeholder reviewEngineering managers / FinOps
CSV dataSorting, filtering, dashboardsAnalysts / ops
  • Scan all regions first; orphaned resources often hide in old migration/test regions.

Troubleshooting

  • If AWS CLI is missing, install it and verify with `aws --version`.
  • If authentication fails, verify the active profile and test with `aws sts get-caller-identity`.
  • If permissions fail, confirm describe/list access for EC2, ELB, and NAT Gateway APIs.
  • If no resources appear, validate region scope and test specific regions manually.

Deletion safety

Use the report for discovery and prioritization only. Confirm resource dependencies and owner intent before cleanup.

Ingredient Categories We Hunt

Four types of forgotten AWS ingredients costing you money every month

Storage Carrots

EBS Volumes

$0.08-$0.10/GB/month

Unattached EBS volumes sitting unused in your AWS pantry

Lonely Grapes

Elastic IPs

$3.65/month each

Unassociated Elastic IPs making your wallet weep

Idle Mushrooms

Load Balancers

$16.20-$18.00/month

Load balancers with no targets to balance

Lonely Herbs

NAT Gateways

$32.40/month each

NAT Gateways routing to nowhere

Professional Ingredient Detection Features

Everything you need to identify and eliminate AWS resource waste

Multi-Resource Detection

Scans 4 types of AWS resources in a single comprehensive hunt

Multi-Region Scanning

Covers all AWS regions or your selected regional pantries

Real-time Cost Calculation

Accurate monthly and annual savings with current AWS pricing

Beautiful HTML Reports

Professional chef-themed reports perfect for executives

AWS CLI Integration

Uses native AWS CLI for reliable resource discovery

Safe Detection Logic

Intelligent filtering to identify truly orphaned resources

Detailed Breakdowns

Per-resource type analysis with size and cost details

Fast Execution

Quick scans with parallel region processing

Ingredient Hunting Recipes

Professional usage examples for different AWS management scenarios

Basic AWS Pantry Scan

Simple hunt across all your AWS regional pantries

# Quick ingredient hunt
.\AWS-Orphaned-Network-Ingredient-Bisque.ps1

# Results auto-open in browser
# Report saved as AWS_Unattached_Resources_Report.html

Custom Regional Hunt

Target specific AWS regions for focused optimization

# Hunt in specific regions
.\AWS-Orphaned-Network-Ingredient-Bisque.ps1 \
 -AllRegions:$false \
 -RegionNames @("us-east-1","us-west-2","eu-west-1")

Production Environment Audit

Professional audit with custom AWS profile

# Production environment scan
.\AWS-Orphaned-Network-Ingredient-Bisque.ps1 \
 -AwsProfile"production" \
 -OutputPath"C:\Audits\Production_Waste_$(Get-Date -Format 'yyyy-MM-dd').html"

Enterprise Multi-Account Hunt

Comprehensive scanning across multiple AWS accounts

# Multi-account enterprise scan
$accounts = @("prod","staging","dev")
foreach ($account in $accounts) {
 .\AWS-Orphaned-Network-Ingredient-Bisque.ps1 \
 -AwsProfile $account \
 -OutputPath"C:\Reports\$account-waste-report.html"
}

Savings Potential by Ingredient Type

Real cost impact of forgotten AWS ingredients

Storage Carrots (EBS Volumes)

  • 10 unused 100GB GP3 volumes = $80/month
  • 5 unused 500GB GP2 volumes = $250/month
  • 1 unused 1TB GP3 volume = $81.92/month

$411.92/month potential

Lonely Grapes (Elastic IPs)

  • 15 unassociated Elastic IPs = $54.75/month
  • 25 forgotten IPs = $91.25/month
  • 50 orphaned IPs = $182.50/month

$328.50/month potential

Idle Mushrooms (Load Balancers)

  • 3 unused ALBs = $48.60/month
  • 2 idle Classic LBs = $36.00/month
  • 1 forgotten NLB = $16.20/month

$100.80/month potential

Lonely Herbs (NAT Gateways)

  • 2 unused NAT Gateways = $64.80/month
  • 4 orphaned NATs = $129.60/month
  • 1 forgotten NAT = $32.40/month

$226.80/month potential

Total Monthly Savings Potential

$1,067.02

Monthly Savings

$12,804.24

Annual Savings

*Based on typical enterprise findings - your savings may vary

Shopping List (Requirements)

Everything you need to start your AWS ingredient hunt

Required Kitchen Tools

  • PowerShell 5.1+ or PowerShell Core 6.0+
  • AWS CLI installed and configured
  • AWS account with appropriate permissions
  • EC2, ELB, and VPC read permissions
  • Multi-region access (if scanning all regions)

Quick Installation Recipe

# Install AWS CLI
# Download from: https://aws.amazon.com/cli/

# Configure AWS credentials
aws configure

# Download the ingredient hunter
git clone https://github.com/cloudcostchefs/Private-Endpoint-Purge-SousChef.git

# Navigate to the kitchen
cd Private-Endpoint-Purge-SousChef

# Start your first hunt
.\AWS-Orphaned-Network-Ingredient-Bisque.ps1

Kitchen Troubleshooting

Common issues and their solutions

AWS CLI not found

Install AWS CLI from official source

# Download and install AWS CLI
# https://aws.amazon.com/cli/
# Then configure: aws configure

Authentication failed

Configure AWS credentials properly

# Set up AWS credentials
aws configure
# Or use environment variables:
# AWS_ACCESS_KEY_ID
# AWS_SECRET_ACCESS_KEY

Permission denied errors

Ensure proper AWS IAM permissions

# Required permissions:
# - ec2:DescribeVolumes
# - ec2:DescribeAddresses
# - elasticloadbalancing:DescribeLoadBalancers
# - ec2:DescribeNatGateways

No resources found (when expected)

Check region selection and permissions

# Verify region access:
aws ec2 describe-regions
# Check specific region:
aws ec2 describe-volumes --region us-east-1

Ready to Hunt Your AWS Ingredients?

Start identifying orphaned resources and reclaiming your AWS budget today. Join thousands of cloud chefs saving money with CloudCostChefs tools.

Average Savings: $200-$24,000+ annually

Setup Time: 5 minutes

Resource Types: EBS, Elastic IPs, Load Balancers, NAT Gateways

What to do next

Pick the path that fits where you are right now.

Trust & run-safety metadata

Key execution details for AWS Orphaned Network Ingredient Bisque so users know what they are downloading or running before they act.

Need verification guidance? See Security & Trust and Responsible Disclosure.

Read-only / reportingGitHub sourceExplicit + inferred metadata

Maintainer

CloudCostChefs

Last Updated

August 15, 2025

Last Tested

February 23, 2026

Minimum Access

Read-only EC2/ELB/VPC visibility across target AWS accounts and regions

Execution Type

GitHub-hosted PowerShell reporting script (AWS orphaned network resource analysis)

Version

2025-08-15

SHA256 Checksum

Not published yet (recommend adding checksum for downloadable files)

Verification Notes

GitHub-hosted AWS network cost analysis workflow. Review AWS CLI profile/role usage, region selection, and generated report paths before scheduled execution.

Safe Usage Checklist

  • Treat EIPs, NAT gateways, and load balancers as cleanup candidates only after confirming active dependencies.
  • Pilot in one account/region first to validate data completeness and report format.
  • Run in a non-production subscription/account/tenancy first and capture sample output before broader rollout.
  • Use least-privilege access. Current best hint from docs: Read-only EC2/ELB/VPC visibility across target AWS accounts and regions.

Quick start (fast path)

Minimal steps to safely get value from this tool without reading the entire page first.

Estimated time: 10 minutes setup + automated monthly inspectionsDifficulty: IntermediateAccess: Review / read-only
  1. 1. Confirm scope and permissions

    Use least privilege and test in a non-production scope first. Minimum access hint: Read-only EC2/ELB/VPC visibility across target AWS accounts and regions.

  2. 2. Get the tool package / source

    View on GitHub and review the files before running.

    GitHub
  3. 3. Check prerequisites

    • ✅ PowerShell 5.1+ or PowerShell Core 6.0+ for running the cloud optimization recipes
    • ✅ AWS CLI installed and configured with proper credentials for resource discovery
    • ✅ AWS account with EC2, ELB, and VPC read permissions for comprehensive scanning
  4. 4. Run safely and review output

    GitHub-hosted AWS network cost analysis workflow. Review AWS CLI profile/role usage, region selection, and generated report paths before scheduled execution. Start with a small sample scope, then expand once results look correct.