Best ‘Freeze and Thaw’ Strategy for Pausing unnecessary services While Minimizing AWS Costs

While AWS doesn't offer a specific "parking" or "inactivation" feature for entire accounts, you can implement several strategies to significantly reduce costs while preserving your ability to quickly restore services when needed:

EC2 Instances:

• Stop (don't terminate) your EC2 instances to eliminate compute charges
• Be aware that you'll still incur costs for attached EBS volumes
• Consider automating instance shutdown/startup with AWS Lambda and EventBridge if you need periodic access
• For development environments, you can schedule automatic shutdown after hours and restart before working hours

Relational Database Service:

• Stop your RDS instances when not in use (you'll still pay for storage)
• Consider taking a final snapshot before stopping for added protection

CloudWatch:

• Reduce log retention periods
• Stop writing debug logs to reduce ingestion fees
• Keep essential monitoring in place to detect any issues

EC2-Other (likely EBS volumes):

• Review and delete unnecessary EBS volumes
• Consider changing volume types to more cost-effective options (like gp3)
• Delete unnecessary snapshots while keeping essential recovery points

Elastic Load Balancing:

• Delete load balancers if not needed as they incur hourly charges even when idle
• Document your configuration for easy recreation

VPC:

• VPC itself is free, but associated resources like NAT Gateways incur charges
• Consider removing NAT Gateways and other paid VPC components
• Document your network configuration for restoration

WAF:

• WAF rules incur charges even when traffic isn't flowing
• Consider removing WAF configurations if not needed during the pause period
• Export and document your rule sets for future restoration

Key Management Service:

• KMS keys have a monthly fee
• Maintain essential keys for encrypted data but review if all are necessary

General Best Practices:

• Document your entire environment before freezing (consider using AWS Config)
• Use resource tagging to track what belongs to the paused environment
• Set up AWS Budgets to alert you if costs unexpectedly increase
• Regularly check your AWS bill to ensure you're not incurring unexpected charges

This approach allows you to significantly reduce costs while maintaining the ability to quickly restore your environment when needed. The key is finding the right balance between cost savings and the effort required to rebuild when you need to "thaw" your environment.
Sources
Parking or inactivating an AWS account. | AWS re:Post
AWS Cost Optimization | AWS re:Post
Unexpected Billing | AWS re:Post
(8) EC2 instances in stopped state, is there any cost footprint when in this state? | AWS re:Post
Tech-savvy savings: innovative ways to cut costs in your small business | AWS Smart Business Blog