PromptBase
PromptBase SelectGet Select
Close icon
General
Home
Marketplace
Create
Hire
Login
Chat
Sell
Explore

Prompt Details

Model
Chat - (gpt-5.6)
Token size
2,319
Example input
[APPLICATION_ARCHITECTURE]: AWS-based e-commerce platform with React frontend, Node.js microservices, PostgreSQL database, Redis cache, SQS workers, and S3 storage. [CLOUD_INFRASTRUCTURE_DETAILS]: 12 EC2 application instances 2 PostgreSQL RDS instances 3 Redis nodes Application Load Balancer CloudFront CDN S3 SQS NAT Gateway CloudWatch Multi-AZ production deployment Separate staging environment [MONTHLY_CLOUD_COST]: $28,000/month [RESOURCE_USAGE_AND_PERFORMANCE_DATA]: EC2 average CPU: 22-35% RDS CPU: 25% Redis utilization: 30% S3 growth: 2.5 TB/month Large volume of application logs No major latency issues Peak traffic is approximately 4x normal traffic [WORKLOAD_AND_TRAFFIC_PATTERN]: Normal traffic during weekdays Major peaks during weekends and promotional campaigns Approximately 70% of traffic is predictable Staging environment is used only during business hours
Example output
PHASE 1 — ARCHITECTURE & WORKLOAD RECONSTRUCTION Reconstructed Architecture The platform consists of: 1. React frontend 2. CloudFront CDN 3. Application Load Balancer 4. Node.js microservices 5. EC2 compute layer 6. PostgreSQL RDS database 7. Redis caching layer 8. SQS asynchronous processing 9. S3 object storage 10. NAT Gateway 11. CloudWatch monitoring and logging Workload Flow User → CloudFront → Application Load Balancer → EC2 microservices → Redis / PostgreSQL Background operations: EC2 → SQS → Worker processes Object operations: Application → S3 Likely Major Cost Drivers The most likely cost drivers are: - EC2 compute - RDS - NAT Gateway/data processing - CloudWatch logs - S3 storage - Redis - Data transfer Initial Assessment The architecture is reasonably mature and highly available. However, average compute utilization of only 22-35% suggests potential overprovisioning. The biggest optimization opportunity is likely capacity alignment, not removing reliability mechanisms. --- PHASE 2 — INFRASTRUCTURE COST MAPPING Category| Resources| Cost Risk Compute| EC2 instances| 🔴 High Database| RDS PostgreSQL| 🟠 High Cache| Redis| 🟡 Moderate Storage| S3 + volumes| 🟡 Moderate Network| NAT + transfer| 🔴 High CDN| CloudFront| 🟢 Efficient Queue| SQS| 🟢 Efficient Observability| CloudWatch| 🟠 High Backup| RDS/S3 backups| 🟡 Moderate Cost Driver Map 🔴 Primary - EC2 - NAT/data transfer - RDS 🟠 Secondary - CloudWatch - Redis 🟡 Potentially Optimizable - S3 - Backups - EBS volumes 🟢 Likely Efficient - CloudFront - SQS --- PHASE 3 — EXPENSIVE RESOURCE DETECTION 1. EC2 Compute Classification: 🔴 Critical Cost Driver Current utilization is only 22-35%. This indicates that the fleet may have more baseline capacity than required. However, peak traffic is 4x normal traffic, so blindly reducing instances would create availability and performance risk. Opportunity: Use autoscaling instead of maintaining excessive baseline capacity. Risk: Medium --- 2. RDS PostgreSQL Classification: 🟠 High Optimization Potential CPU utilization is approximately 25%. Potential opportunities: - Right-size database instances - Analyze memory utilization - Review read replicas - Optimize expensive queries - Review storage allocation - Review backup retention Database downsizing should only happen after checking memory, IOPS, connections and peak utilization. --- 3. Redis Classification: 🟡 Moderate Cost Opportunity 30% utilization suggests possible overcapacity. Before reducing nodes, validate: - Memory utilization - Eviction rate - Connection count - Failover requirements - Peak traffic behavior --- 4. CloudWatch Classification: 🟠 High Optimization Potential Large log volumes can produce recurring costs. Potential improvements: - Reduce unnecessary DEBUG logs - Shorten high-cost log retention - Move historical logs to cheaper storage - Apply lifecycle policies --- PHASE 4 — UTILIZATION & OVERPROVISIONING AUDIT EC2 Average CPU: 22-35%. Potential issue: Allocated capacity > normal workload requirement Recommended approach: - Keep sufficient production baseline - Enable autoscaling - Define minimum capacity - Define maximum capacity - Scale based on CPU + request count + latency Do not use CPU alone if request volume or memory is the actual bottleneck. --- RDS 25% CPU indicates potential excess compute capacity. But CPU alone is insufficient. Validate: - Memory - IOPS - Connections - Query latency - Storage throughput - Peak-hour utilization --- Redis 30% utilization indicates possible overprovisioning. But because Redis may provide availability and low latency, downsizing should be validated during peak traffic. --- Storage Search for: - Unattached EBS volumes - Old snapshots - Duplicate backups - Old objects - Temporary files - Unused database storage These are generally low-risk cleanup opportunities. --- PHASE 5 — COST VS PERFORMANCE ANALYSIS Optimization| Cost Impact| Performance Impact| Risk EC2 right-sizing| High savings| Potentially negative if excessive| Medium Autoscaling| High savings| Positive if configured correctly| Medium RDS right-sizing| Moderate savings| Possible latency impact| Medium Log retention reduction| Moderate savings| Minimal| Low S3 lifecycle| Moderate savings| Retrieval may become slower| Low/Medium Redis downsizing| Moderate savings| Possible cache pressure| Medium NAT optimization| Moderate savings| Can improve architecture| Medium Key Trade-off Reducing EC2 from 12 instances to a much smaller fixed fleet may lower costs but could make 4x promotional traffic difficult to handle. Therefore: Autoscaling is preferable to aggressive fixed-capacity reduction. --- PHASE 6 — SCALABILITY & ELASTICITY AUDIT Current architecture appears capable of horizontal scaling. However, the key question is whether scaling is dynamic. Recommended Scaling Model Normal traffic: 6-8 instances Peak traffic: 12+ instances Low traffic: 4-6 instances These numbers are illustrative and must be validated against actual performance data. Recommended Controls Minimum: 4-6 instances Maximum: 12-20 instances depending on load testing Scale-out signals: - CPU - Request count - Response latency - Queue depth Scale-in should be slower than scale-out to avoid oscillation. Main Finding The platform appears to be paying for peak capacity during periods when demand is substantially lower. Elasticity is therefore the major architectural cost opportunity. --- PHASE 7 — STORAGE & DATA COST ANALYSIS S3 S3 usage grows approximately 2.5 TB/month. Recommended lifecycle strategy: Hot data → Standard storage Less frequently accessed data → Infrequent-access tier Old data → Archive tier Expired data → Automatic deletion where legally permitted Logs Application logs should have tiered retention. Example strategy: - Recent operational logs: short-term searchable retention - Historical logs: compressed cheaper storage - Compliance logs: retention according to policy - Debug logs: short retention Backups Review: - Snapshot age - Backup retention - Duplicate backup copies - Cross-region backup requirements Do not reduce backups below the RPO/RTO requirements. --- PHASE 8 — NETWORK & DATA TRANSFER COST AUDIT This is potentially one of the largest hidden cost areas. NAT Gateway Investigate: - Which workloads access the internet through NAT? - Can AWS service traffic use private endpoints? - Is large S3 traffic unnecessarily passing through NAT? - Is cross-AZ traffic occurring unnecessarily? Potential Optimization If workloads frequently communicate with S3 and other supported cloud services, private connectivity can reduce unnecessary network paths and potentially reduce NAT-related processing. Cross-AZ Traffic Microservices should avoid unnecessarily chatty cross-AZ communication. Do not sacrifice Multi-AZ availability simply to eliminate cross-AZ traffic. Availability requirement remains higher priority. --- PHASE 9 — DATABASE COST OPTIMIZATION Current Situation PostgreSQL RDS CPU: approximately 25%. Potential optimization areas: Instance Size Investigate whether the current instance is oversized. Read Replicas Determine whether every replica is genuinely required. Queries Identify: - Slow queries - Missing indexes - Repeated queries - Excessive joins - Inefficient pagination Connection Management Use connection pooling to prevent excessive database connections. Caching Move repeatedly requested read-heavy data into Redis where appropriate. Important Warning Do not downsize RDS based only on CPU. A database with 25% CPU but high memory or IOPS utilization may still be correctly sized. --- PHASE 10 — APPLICATION ARCHITECTURE COST ANALYSIS Potential application-level cost sources: 1. Excessive API Calls Repeated frontend API requests increase: - EC2 usage - Database load - Network transfer - Cache activity 2. Chatty Microservices Service A → Service B → Service C → Service D can create unnecessary network and compute overhead. 3. Poor Caching Frequently requested immutable or slowly changing data should be cached where appropriate. 4. Polling Replace excessive polling with event-driven mechanisms where practical. 5. Background Processing SQS should be used to decouple expensive asynchronous work from synchronous user requests. Highest-value Application Optimization Measure the most expensive API endpoints and database queries first. Reducing unnecessary requests can produce infrastructure savings without reducing capacity. --- PHASE 11 — AUTOMATION & RESOURCE EFFICIENCY ANALYSIS Recommended Automations Development/Staging Automatically stop non-production resources outside working hours. This is a high-confidence optimization if the environment does not need 24/7 availability. Storage Automatic lifecycle policies. Cleanup Automatically detect: - Unattached volumes - Old snapshots - Unused IP resources - Temporary resources Compute Autoscaling based on actual workload. Cost Monitoring Create budget alerts for abnormal spending. Priority 1. Staging scheduling 2. EC2 autoscaling 3. Storage lifecycle 4. Unused resource cleanup 5. Cost anomaly detection --- PHASE 12 — PRICING & PURCHASING STRATEGY Approximately 70% of traffic is predictable. This makes the stable baseline potentially suitable for commitment-based pricing. Recommended Strategy Do not commit the entire infrastructure immediately. Instead: 1. Determine stable baseline usage 2. Use on-demand for variable capacity 3. Consider Savings Plans/reserved capacity for stable compute 4. Consider Spot capacity for interruption-tolerant background workers Example Architecture Stable production workload: Commitment pricing Variable application capacity: On-demand Background workers: Spot/preemptible where safe This creates a balance between savings and elasticity. --- PHASE 13 — SAVINGS ESTIMATION Exact savings cannot be confirmed because resource-level billing data and provider pricing are not provided. Therefore, the following figures are illustrative estimates, not confirmed savings. Recommendation| Estimated Monthly Savings| Effort| Risk EC2 autoscaling/right-sizing| $2,500-$4,500| Medium| Medium Staging scheduling| $800-$1,500| Low| Low CloudWatch optimization| $700-$1,500| Low| Low S3 lifecycle policies| $400-$900| Low| Low NAT/network optimization| $600-$1,500| Medium| Medium RDS optimization| $700-$1,500| Medium| Medium Redis optimization| $300-$700| Medium| Medium Potential Combined Opportunity Estimated opportunity: $6,000-$12,100/month Potential annualized opportunity: $72,000-$145,200/year However, these values should not be added mechanically because savings may overlap. A realistic validated target would be approximately: 20-30% of the current $28,000/month bill, subject to actual billing analysis. --- PHASE 14 — OPTIMIZATION PRIORITY MATRIX 🔥 Immediate 1. Staging environment scheduling - Savings: Medium - Effort: Low - Risk: Low - Speed: Very fast 2. Log retention optimization - Savings: Medium - Effort: Low - Risk: Low 3. Unused resource cleanup - Savings: Low/Medium - Effort: Low - Risk: Low --- 🚀 High Priority 4. EC2 autoscaling - Savings: High - Effort: Medium - Risk: Medium 5. NAT/network optimization - Savings: Medium/High - Effort: Medium - Risk: Medium 6. RDS right-sizing - Savings: Medium - Effort: Medium - Risk: Medium --- 📌 Medium Priority 7. Redis optimization 8. S3 lifecycle optimization 9. Database query optimization 10. API request optimization --- 🕐 Long-Term 11. Architecture simplification 12. Greater event-driven processing 13. Serverless evaluation 14. Advanced workload placement optimization --- PHASE 15 — OPTIMIZATION ROADMAP 0-30 DAYS Action| Savings| Owner| Risk| Success Metric Schedule staging shutdown| Medium| DevOps| Low| Staging runtime reduced Remove unused resources| Low/Medium| CloudOps| Low| Zero orphaned resources Optimize log retention| Medium| SRE| Low| Log cost reduced Analyze EC2 utilization| None initially| FinOps| Low| Baseline established Analyze NAT traffic| None initially| Network team| Low| Traffic sources identified --- 31-90 DAYS Action| Savings| Owner| Risk| Success Metric Deploy EC2 autoscaling| High| DevOps| Medium| Capacity follows demand Right-size RDS| Medium| DBA| Medium| Cost reduced without latency increase Optimize Redis| Medium| Platform team| Medium| No cache degradation Implement S3 lifecycle| Medium| CloudOps| Low| Storage cost/TB reduced Optimize database queries| Medium| Engineering| Low/Medium| Query latency improved --- 3-6 MONTHS Focus on architecture-level optimization. Actions: - Reduce unnecessary service-to-service calls - Improve caching - Move suitable background workloads to Spot - Improve event-driven processing - Optimize network topology - Improve workload scheduling Expected outcome: Lower baseline infrastructure cost without sacrificing scalability. --- 6-12 MONTHS Strategic optimization: - Evaluate serverless for suitable workloads - Reassess microservice boundaries - Optimize database architecture - Improve workload placement - Introduce advanced FinOps governance - Implement automated cost anomaly detection - Establish unit economics such as cost per order/API request --- PHASE 16 — FINAL CLOUD OPTIMIZATION REPORT Executive Summary The architecture is fundamentally sound and supports high availability and traffic spikes. The primary issue is capacity utilization versus provisioned capacity. The strongest opportunities appear to be: 1. EC2 elasticity 2. Staging environment scheduling 3. Network/NAT optimization 4. Database right-sizing 5. Observability cost control 6. Storage lifecycle management The objective should not be to simply reduce infrastructure. The recommended strategy is: Keep the reliability architecture while making capacity elastic and removing recurring waste. --- 💰 Top Cost Drivers 1. 🔴 EC2 compute 2. 🔴 Network/NAT/data transfer 3. 🟠 RDS PostgreSQL 4. 🟠 CloudWatch/logging 5. 🟡 Redis 6. 🟡 S3/storage 7. 🟢 CloudFront/SQS --- 🔴 Critical Waste Findings Finding 1 EC2 utilization of 22-35% suggests possible overprovisioning. Finding 2 Staging runs outside its likely required operating window. Finding 3 Large log volumes may be creating unnecessary recurring observability costs. Finding 4 NAT/data-transfer architecture may be generating avoidable network charges. Finding 5 RDS and Redis utilization suggests that capacity should be investigated. --- ⚡ Quick Wins 1. Schedule staging shutdown. 2. Remove unused storage/resources. 3. Reduce unnecessary DEBUG logging. 4. Apply S3 lifecycle rules. 5. Review old snapshots. 6. Enable cost anomaly alerts. 7. Identify high-cost API/database operations. These changes are relatively reversible and should be implemented before aggressive infrastructure downsizing. --- 🏗️ Architecture Improvements The highest-value architecture improvement is elastic infrastructure. Instead of: Fixed large capacity → Pay for peak capacity continuously move toward: Baseline capacity → Autoscaling → Peak capacity only when required → Scale-in after demand falls For asynchronous workloads: Application → SQS → Elastic workers This allows background processing capacity to follow queue demand. --- ⚖️ Cost vs Scalability Trade-offs Decision| Cost| Scalability| Risk Fixed EC2 fleet| High| Good| Low Aggressive downsizing| Low| Poor| High Autoscaling| Lower| Excellent| Medium Remove Multi-AZ| Lower| Worse| High Optimize network path| Lower| Good| Medium Reduce backups| Lower| Worse recovery| High Optimize logging| Lower| Same| Low Do not reduce Multi-AZ production architecture merely to save money. --- 📊 Savings Projection Current monthly cost: $28,000 Illustrative optimization target: 20-30% Potential monthly reduction: $5,600-$8,400 Potential annual reduction: $67,200-$100,800 These are planning estimates only. Actual savings must be validated using: - Detailed billing data - Resource-level costs - Usage metrics - Peak utilization - Data-transfer volume - Contract/discount pricing --- 🛣️ Optimization Roadmap Priority 1 Staging scheduling + unused-resource cleanup Priority 2 CloudWatch/log optimization Priority 3 EC2 autoscaling Priority 4 NAT/network optimization Priority 5 RDS and Redis right-sizing Priority 6 Application/database efficiency Priority 7 Long-term architecture modernization --- ⚠️ Risk Register Risk| Mitigation Autoscaling too slowly| Load testing + proactive scale-out Excessive scale-in| Conservative scale-in policy Database downsizing| Validate memory/IOPS/latency Cache downsizing| Monitor eviction rate Log reduction| Preserve required audit logs Storage tiering| Validate retrieval requirements Network redesign| Test before production rollout Commitment purchase| Commit only stable baseline Spot interruption| Use only interruption-tolerant workloads --- ✅ Final Recommendation The highest-value strategy is not aggressive resource reduction. The recommended blueprint is: 1. Eliminate obvious waste → unused resources + staging scheduling 2. Control observability costs → log retention + log-volume optimization 3. Make compute elastic → autoscaling instead of permanently provisioning for peak demand 4. Optimize network architecture → reduce unnecessary NAT/data movement while preserving availability 5. Right-size databases carefully → use CPU + memory + IOPS + latency rather than CPU alone 6. Optimize application behavior → caching + query optimization + fewer unnecessary API calls 7. Apply commitment discounts only to stable baseline workloads The expected result is a cloud platform that is cheaper during normal traffic, elastic during peaks, and still compliant with the 99.95% availability and disaster-recovery requirements. Missing Data That Would Be Required for Production-Grade Validation The analysis would become significantly more accurate with: - Resource-level monthly costs - EC2 instance types - RDS instance types - Redis node types - NAT Gateway monthly/data-processing costs - Data-transfer volume - CloudWatch log ingestion/retention - S3 storage classes - Peak CPU/memory/IOPS - Database connection metrics - Autoscaling configuration - Backup retention - Exact production/staging resource counts Test Verdict: PASS The architecture has meaningful optimization potential, but the safest strategy is elasticity + right-sizing + automation + network optimization, rather than indiscriminate resource deletion or aggressive downsizing.
GPT

Cloud Cost Architecture Advisor

Add to Cart
Instant accessInstant access
Usage rightsCommercial use
Money-back guaranteeMoney‑back
By purchasing this prompt, you agree to our terms of service
GPT-5.6
Tested icon
Guide icon
4 examples icon
Free credits icon
Cloud bills keep rising because expensive resources, overprovisioning, and poor architecture trade-offs are hard to identify. 🔍 Analyze application + infrastructure architecture 💰 Detect expensive and underutilized resources ⚖️ Evaluate cost vs scalability trade-offs 🧠 Find architecture-level savings opportunities 🛠️ Build a prioritized optimization roadmap 📊 Estimate potential cost impact 🚀 Improve efficiency without sacrificing reliability Turn complex cloud infrastructure into a clear,
...more
Added over 1 month ago
Report
Browse Marketplace