Generated: June 2026
What’s a Why-Not Report?
It hearkens back to the days of old. When we could read about the downside of vendors, instead of regurgitating marketing. A whynot report is a negative intelligence report focused on historical vendor events, weaknesses, failure patterns, and competitive disadvantages, essentially answering “why not” this vendor as a curiosity of thought and conjecture.
Sources: Reddit, Medium, Oracle, Qualys, SentinelOne, Gigamon, Ridge Security, Clarifai, RightSpend
1. SUPPORT QUALITY DEGRADATION (2024-2025)
Enterprise Support Breakdown
- Reddit (Oct 2025): “Most tickets go unassigned, responses take days/weeks even for production-impacting issues” – users on Enterprise Support report escalating delays
- Reddit (Feb 2025): “We’re on EDP with Enterprise support and really frustrated with the level of support we’ve gotten in the last half a year” – account reps increasingly unresponsive
- Reddit (July 2025): “AWS tech support shockingly bad these days. Most of the time when I hop on support chat lately, it doesn’t really feel helpful” – chat support quality degraded
- Reddit (Mar 2024): “They always take days or weeks to answer, even for issues that have impact on production and in majority of the cases provide no useful feedback or help”
Support Model Shift Warning
- Reddit (Dec 2025): “By 2028 Enterprise Support will get you the premium LLM access instead of human experts” – early signals of support quality degradation
- Quota requests frequently go nowhere despite billions in support plan revenue
- Account representatives increasingly automated and unresponsive to complex technical issues
2. SECURITY MISCONFIGURATIONS & EXPLOITATION RISK
S3 Bucket Vulnerabilities
- 31% of S3 buckets are currently open to the public (Qualys, February 2026) – highest percentage among major cloud providers
- Misconfigured S3 buckets remain the #1 security issue on AWS (SentinelOne, Gigamon)
- 8-minute countdown to admin compromise via public S3 buckets (Ridge Security) – minimal misconfiguration leads to rapid compromise
- Small misconfigurations create mountainous liability for enterprises
IAM & Access Control Issues
- Shadow IT resources launched without proper oversight due to complex IAM hierarchy
- Misconfigured IAM policies – highly prevalent issue across customer environments
- Stolen credentials remain the primary attack vector (86% of data breaches) – IAM complexity exacerbates this
- Customer security incidents catalog shows ongoing issues with third-party integration permissions
Compared to Competitors
- Azure: Better security posture with Microsoft’s enterprise security integrations and built-in compliance
- GCP: More transparent security model with fewer configuration pitfalls
- Oracle: Despite catastrophic breach, Oracle’s security documentation is more straightforward
3. HIDDEN COSTS & COMPLEX PRICING
Surprise Billing Incidents
- Reddit (Mar 2024): “We chose AWS CloudWatch for our new small project. Fast forward, and our next bill almost doubles” – unexpected cost spikes
- LinkedIn (Jan 2026): Multiple users warning about “hidden costs” and “AWS billing surprises” – recurring theme in 2025-2026
- Oracle whitepaper: “Data transfer costs amounted to upwards of 30% of total AWS cost. Enterprise support costs came as a surprise”
Hidden Fee Ecosystem
- Medium (Sept 2025): “The Hidden Fee Ecosystem: Every AWS service has 3–5 associated charges that aren’t mentioned in the main pricing”
- S3 storage costs $0.023/GB but request fees, data retrieval fees, lifecycle transition fees, and cross-region replication charges add 200-400% to base costs
- AWS X-Ray, CloudWatch, Lambda logging, NAT gateway fees – all frequently overlooked by cost-conscious teams
- Data egress costs among the highest in the industry at $0.09/GB minimum
Cost Management Complexity
- Companies losing $50K+ monthly to billing mistakes (RightSpend, January 2025)
- Cost management tools lag behind Azure and GCP (Clarifai) – Azure Cost Management and GCP’s Cost Management Console are more intuitive
- SMBs find AWS particularly unfriendly due to pricing complexity and lack of clear cost visibility
4. FEATURE GAPS & LIMITATIONS
Compared to Azure:
- Enterprise Database Integration: AWS lacks seamless Microsoft SQL Server/SSIS/SSRS/SSAS integration that Azure provides out-of-the-box
- On-Premises Hybrid: Azure Arc and Azure Stack integrate better with existing enterprise systems – AWS Outposts has steeper learning curve
- Compliance: Azure has stronger compliance for financial services and government workloads – AWS requires more manual configuration
- Microsoft 365 Integration: Azure AD (Entra ID) integration is native; AWS SSO requires additional configuration
Compared to GCP:
- AI/ML: GCP’s Vertex AI is more mature and integrated than AWS SageMaker – easier to get started with production ML
- Data Analytics: GCP Dataflow and BigQuery often outperform AWS Glue and Redshift in cost-efficiency
- Simplicity: GCP’s simpler service catalog appeals to teams frustrated by AWS’s 200+ services
Compared to Oracle:
- Security Transparency: Oracle’s 2025 breach was catastrophic but well-documented; AWS’s misconfigurations are systemic
- Support Quality: Oracle’s Enterprise Support remains more responsive despite the breach
- Pricing Simplicity: Oracle’s pricing model is more straightforward than AWS’s complex service catalog
5. COMPLEXITY & LEARNING CURVE
Service Proliferation
- 200+ AWS services – overwhelming for teams without dedicated cloud architects
- Service names are cryptic: EC2, Lambda, ECS, EKS, App Runner, App Mesh – requires significant learning
- Deprecation notices – constant churn with services being retired and replaced
Documentation Gaps
- Regional differences – documentation often doesn’t reflect actual regional service availability
- Service-specific quirks – each service has its own unique behavior that’s rarely documented
- Third-party integrations – complex and poorly documented for many services
6. FINAL VERDICT: WHEN TO AVOID AWS
DO NOT use AWS if:
- You lack dedicated cloud architects (complexity is prohibitive)
- You need predictable, transparent pricing (hidden fees are rampant)
- You require high-touch enterprise support (quality has degraded)
- You work heavily with Microsoft technologies (Azure is superior)
- You’re a small team without cloud expertise (steep learning curve)
CONSIDER AWS if:
- You already have significant AWS investment (switching costs are high)
- You need the most extensive serverless offerings (no competitor matches)
- You’re building at massive scale (AWS’s infrastructure is unmatched)
- You require global multi-region availability (AWS’s geographic coverage is best)
Recommendation: For new projects, consider Azure (better enterprise integration, simpler pricing) or GCP (better AI/ML, more intuitive). For existing AWS investments, invest in cost management tools and support plan optimization.
