road2reinvent-hi-viz/spending_analysis.json at main · masterpointio/road2reinvent-hi-viz · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
{
  "total_amount": "$15000",
  "timeline_days": 45,
  "efficiency_level": "Brain damage",
  "architecture_type": "kubernetes",
  "burning_style": "horizontal",
  "services_deployed": [
    {
      "service_name": "EKS",
      "instance_type": "m5.2xlarge",
      "quantity": 10,
      "unit_cost": 0.408,
      "total_cost": 734.4,
      "start_day": 0,
      "end_day": 45,
      "duration_used": "entire timeline",
      "usage_pattern": "Running 24/7",
      "waste_factor": "Over-provisioned instances for a simple microservice"
    },
    {
      "service_name": "AWS Fargate",
      "instance_type": "FARGATE_SPOT",
      "quantity": 50,
      "unit_cost": 0.0408,
      "total_cost": 1836.0,
      "start_day": 0,
      "end_day": 45,
      "duration_used": "entire timeline",
      "usage_pattern": "Running 24/7",
      "waste_factor": "Using Fargate Spot for a simple cron job"
    },
    {
      "service_name": "AWS Outposts",
      "instance_type": "outpost-server",
      "quantity": 2,
      "unit_cost": 1.0,
      "total_cost": 450.0,
      "start_day": 0,
      "end_day": 45,
      "duration_used": "entire timeline",
      "usage_pattern": "Running 24/7",
      "waste_factor": "Using AWS Outposts for a cloud-native application"
    },
    {
      "service_name": "AWS Batch",
      "instance_type": "c6g.2xlarge",
      "quantity": 10,
      "unit_cost": 0.408,
      "total_cost": 1836.0,
      "start_day": 0,
      "end_day": 45,
      "duration_used": "entire timeline",
      "usage_pattern": "Running 24/7",
      "waste_factor": "Using Batch for minimal workloads"
    },
    {
      "service_name": "AWS Transfer Family",
      "instance_type": "transfer-server",
      "quantity": 10,
      "unit_cost": 0.05,
      "total_cost": 225.0,
      "start_day": 0,
      "end_day": 45,
      "duration_used": "entire timeline",
      "usage_pattern": "Running 24/7",
      "waste_factor": "Using Transfer Family when S3 would suffice"
    },
    {
      "service_name": "AWS Elemental MediaLive",
      "instance_type": "medialive-server",
      "quantity": 5,
      "unit_cost": 1.0,
      "total_cost": 500.0,
      "start_day": 0,
      "end_day": 45,
      "duration_used": "entire timeline",
      "usage_pattern": "Running 24/7",
      "waste_factor": "Running MediaLive for static content"
    }
  ],
  "total_calculated_cost": 7251.0,
  "deployment_scenario": "The deployment scenario likely involves a team that has taken a 'Brain damage' approach to cloud architecture. They have deployed a Kubernetes cluster using EKS with over-provisioned m5.2xlarge instances, running Fargate Spot for a simple cron job, using AWS Outposts for a cloud-native application, running AWS Batch for minimal workloads, using AWS Transfer Family when S3 would suffice, and running AWS Elemental MediaLive for static content. This setup is indicative of a team that has misunderstood the requirements and is using the most expensive and complex services available for basic tasks.",
  "key_mistakes": [
    "Over-provisioning instances for a simple microservice",
    "Using Fargate Spot for a simple cron job",
    "Using AWS Outposts for a cloud-native application",
    "Using AWS Batch for minimal workloads",
    "Using AWS Transfer Family when S3 would suffice",
    "Running AWS Elemental MediaLive for static content"
  ],
  "recommendations": [
    "Right-size instances based on actual workload requirements",
    "Use EC2 instances instead of Fargate Spot for simple cron jobs",
    "Avoid using AWS Outposts for cloud-native applications",
    "Use simpler and more cost-effective services for minimal workloads",
    "Use S3 instead of AWS Transfer Family for file transfers",
    "Avoid using AWS Elemental MediaLive for static content"
  ],
  "roast": "You've taken 'Brain damage' to a whole new level. Over-provisioning instances, using Fargate Spot for a cron job, deploying Outposts for a cloud-native app, and running MediaLive for static content? It's like using a sledgehammer to crack a nut. Your cloud bill is a testament to your lack of understanding of cost-effective cloud architecture. Maybe next time, try to match the complexity of your services to the actual needs of your applications."
}