Now when we have all instances and volumes tagged. I can say who is using what resources. Below you will find the aggregated overview of resources we are using in AWS.
If you will not mind, I plan to send this overview every month. My intention is to be able to see the overview of long-term provisioned resources across regions. This is just snapshot of one moment. This report does not catch how long the resource has been provisioned.
This report does not include:
* snapshots - this is something I want to focus in next step in near future
* CloudFront - this is actualy biggest item on our invoice. But there is nothing we can do about it. There is no cheaper option and no way to optimize it further. I have no intention to report our usage of CloudFront.
* price of instances - this report does not differ if the instance is spot, reserved one, or on demand. I am not sure if I want to report it as my main goal is to catch forgotten resources rather than aiming for lowering the total cost.
If you have ideas how to improve this report, let me know.
Here is the report.
= Volumes
FedoraGroup: centos Region: ap-south-1 Volume Type: gp3 - Total Size: 4570 GiB Region: eu-central-1 Volume Type: gp3 - Total Size: 13200 GiB Region: us-west-2 Volume Type: gp3 - Total Size: 13145 GiB Region: af-south-1 Volume Type: gp3 - Total Size: 4050 GiB Region: eu-west-3 Volume Type: gp3 - Total Size: 2917 GiB Region: eu-west-2 Volume Type: gp3 - Total Size: 21420 GiB Region: eu-west-1 Volume Type: gp3 - Total Size: 584 GiB Region: ap-northeast-1 Volume Type: gp3 - Total Size: 8070 GiB Region: sa-east-1 Volume Type: gp3 - Total Size: 4250 GiB Region: ap-southeast-1 Volume Type: gp3 - Total Size: 4050 GiB Region: ap-southeast-2 Volume Type: gp3 - Total Size: 8100 GiB Region: us-east-1 Volume Type: gp3 - Total Size: 24350 GiB Region: us-east-2 Volume Type: gp3 - Total Size: 44890 GiB Volume Type: io1 - Total Size: 200 GiB FedoraGroup: infra Region: ap-south-1 Volume Type: gp3 - Total Size: 8 GiB Region: eu-central-1 Volume Type: gp3 - Total Size: 16223 GiB Region: us-west-1 Volume Type: gp3 - Total Size: 40 GiB Region: us-west-2 Volume Type: standard - Total Size: 100 GiB Volume Type: gp3 - Total Size: 900 GiB Region: af-south-1 Volume Type: gp3 - Total Size: 25 GiB Region: eu-west-2 Volume Type: gp3 - Total Size: 20 GiB Region: ap-northeast-2 Volume Type: gp3 - Total Size: 196 GiB Region: sa-east-1 Volume Type: gp3 - Total Size: 200 GiB Region: ap-southeast-1 Volume Type: gp3 - Total Size: 108 GiB Region: us-east-1 Volume Type: gp3 - Total Size: 330 GiB Region: us-east-2 Volume Type: gp3 - Total Size: 113 GiB FedoraGroup: min Region: eu-central-1 Volume Type: gp3 - Total Size: 1000 GiB FedoraGroup: garbage-collector Region: ap-southeast-1 Volume Type: standard - Total Size: 6 GiB FedoraGroup: copr Region: us-east-1 Volume Type: st1 - Total Size: 5500 GiB Volume Type: gp3 - Total Size: 3468 GiB Volume Type: standard - Total Size: 500 GiB Volume Type: io2 - Total Size: 20 GiB Volume Type: sc1 - Total Size: 49652 GiB FedoraGroup: ci Region: us-east-1 Volume Type: gp3 - Total Size: 3056 GiB Region: us-east-2 Volume Type: gp3 - Total Size: 12488 GiB Volume Type: gp2 - Total Size: 516 GiB FedoraGroup: respins Region: us-east-1 Volume Type: gp3 - Total Size: 500 GiB FedoraGroup: abrt Region: us-east-1 Volume Type: gp3 - Total Size: 10 GiB
= Instances
FedoraGroup: centos Region: ap-south-1 Instance Type: t3.2xlarge - Count: 3 Instance Type: t3.large - Count: 1 Instance Type: m6i.2xlarge - Count: 1 Region: eu-central-1 Instance Type: t2.small - Count: 1 Instance Type: t2.large - Count: 2 Instance Type: r5b.8xlarge - Count: 1 Instance Type: m6i.2xlarge - Count: 1 Instance Type: t3.xlarge - Count: 1 Region: us-west-2 Instance Type: m6i.2xlarge - Count: 2 Instance Type: t3.small - Count: 1 Instance Type: t3.xlarge - Count: 1 Region: af-south-1 Instance Type: m6i.2xlarge - Count: 1 Region: eu-west-3 Instance Type: t2.large - Count: 2 Instance Type: t2.2xlarge - Count: 1 Instance Type: t3a.xlarge - Count: 1 Instance Type: t2.small - Count: 2 Instance Type: t3.xlarge - Count: 1 Instance Type: t3.large - Count: 1 Region: eu-west-2 Instance Type: t2.small - Count: 1 Instance Type: t2.large - Count: 1 Instance Type: t3a.large - Count: 2 Instance Type: r5a.8xlarge - Count: 1 Instance Type: t3.large - Count: 2 Instance Type: t3.xlarge - Count: 1 Instance Type: t2.medium - Count: 1 Instance Type: m6i.2xlarge - Count: 1 Region: eu-west-1 Instance Type: t2.medium - Count: 4 Instance Type: t2.xlarge - Count: 3 Instance Type: t2.large - Count: 1 Instance Type: t2.small - Count: 2 Instance Type: t3.large - Count: 1 Instance Type: t3.medium - Count: 2 Region: ap-northeast-1 Instance Type: c6g.2xlarge - Count: 1 Instance Type: m6i.2xlarge - Count: 1 Region: sa-east-1 Instance Type: c6g.4xlarge - Count: 1 Instance Type: m6i.2xlarge - Count: 1 Region: ap-southeast-1 Instance Type: m6i.2xlarge - Count: 1 Region: ap-southeast-2 Instance Type: m6i.2xlarge - Count: 2 Region: us-east-1 Instance Type: t3.xlarge - Count: 2 Region: us-east-2 Instance Type: t2.2xlarge - Count: 1 Instance Type: m5a.2xlarge - Count: 1 Instance Type: t3.xlarge - Count: 4 Instance Type: t3a.large - Count: 1 Instance Type: m6i.2xlarge - Count: 2 Instance Type: t2.large - Count: 2 Instance Type: t3.large - Count: 1 Instance Type: m4.2xlarge - Count: 1 Instance Type: t3.small - Count: 1 Instance Type: t3.medium - Count: 1 FedoraGroup: infra Region: ap-south-1 Instance Type: c5d.xlarge - Count: 1 Region: eu-central-1 Instance Type: c5d.xlarge - Count: 1 Instance Type: c5n.2xlarge - Count: 1 Instance Type: m5.xlarge - Count: 1 Instance Type: m6gd.4xlarge - Count: 1 Region: us-west-1 Instance Type: t3.medium - Count: 1 Region: us-west-2 Instance Type: m5.large - Count: 4 Instance Type: m6g.large - Count: 1 Instance Type: t3.large - Count: 1 Instance Type: c5n.2xlarge - Count: 1 Instance Type: c6gd.xlarge - Count: 1 Region: af-south-1 Instance Type: c5d.xlarge - Count: 2 Region: eu-west-2 Instance Type: c5d.xlarge - Count: 1 Region: ap-northeast-2 Instance Type: c5n.2xlarge - Count: 1 Region: sa-east-1 Instance Type: c5.2xlarge - Count: 1 Instance Type: c5n.2xlarge - Count: 1 Region: ap-southeast-1 Instance Type: c5d.xlarge - Count: 1 Instance Type: c5n.2xlarge - Count: 1 Region: us-east-1 Instance Type: t3.medium - Count: 1 Instance Type: t3.small - Count: 1 Instance Type: c5.xlarge - Count: 2 Instance Type: t2.medium - Count: 2 Instance Type: c5.2xlarge - Count: 1 Region: us-east-2 Instance Type: c5d.large - Count: 2 Instance Type: t2.micro - Count: 1 Instance Type: t3.medium - Count: 1 FedoraGroup: centos-stream-osci Region: ca-central-1 Instance Type: m5d.large - Count: 5 Instance Type: t2.micro - Count: 1 FedoraGroup: min Region: eu-central-1 Instance Type: t3.2xlarge - Count: 1 FedoraGroup: abrt Region: us-east-1 Instance Type: t3a.2xlarge - Count: 1 FedoraGroup: ci Region: us-east-1 Instance Type: c5.2xlarge - Count: 6 Region: us-east-2 Instance Type: m5a.4xlarge - Count: 1 Instance Type: r5.large - Count: 4 Instance Type: i3.2xlarge - Count: 6 Instance Type: c5.2xlarge - Count: 3 Instance Type: r5.xlarge - Count: 2 Instance Type: c6a.large - Count: 19 Instance Type: c6g.large - Count: 15 Instance Type: c6g.xlarge - Count: 1 FedoraGroup: copr Region: us-east-1 Instance Type: t3a.small - Count: 1 Instance Type: t3a.medium - Count: 5 Instance Type: t3a.xlarge - Count: 3 Instance Type: m5a.4xlarge - Count: 1 Instance Type: i4i.large - Count: 23 Instance Type: c7g.xlarge - Count: 64 Instance Type: t2.medium - Count: 1 FedoraGroup: centos-stream-build Region: us-east-2 Instance Type: t2.micro - Count: 1
On Mon, Sep 25, 2023 at 05:38:44AM +0200, Miroslav Suchý wrote:
Now when we have all instances and volumes tagged. I can say who is using what resources. Below you will find the aggregated overview of resources we are using in AWS.
If you will not mind, I plan to send this overview every month. My intention is to be able to see the overview of long-term provisioned resources across regions. This is just snapshot of one moment. This report does not catch how long the resource has been provisioned.
This report does not include:
* snapshots - this is something I want to focus in next step in near future
* CloudFront - this is actualy biggest item on our invoice. But there is nothing we can do about it. There is no cheaper option and no way to optimize it further. I have no intention to report our usage of CloudFront.
* price of instances - this report does not differ if the instance is spot, reserved one, or on demand. I am not sure if I want to report it as my main goal is to catch forgotten resources rather than aiming for lowering the total cost.
If you have ideas how to improve this report, let me know.
Might it be possible to put all the resources under the same tag, ie,
FedoraGroup: infra volumes: ... instances: ...
That way it's easier if you are looking at only one group. Or, perhaps a more csv type thing?
Group,region,kind,size/type/count
infra,us-west-2,volume,gp3,500GB infra,us-west-2,instance,t2.large,3
But in any case, thanks, this will be helpful over time.
I think monthly is about right.
kevin
infrastructure@lists.fedoraproject.org
-
Kevin Fenzi -
Miroslav Suchý