AWS usage per group (June)

2024-07-01 Thread Miroslav Suchý

Here comes June edition of resources running in AWS. It's a snapshot of 
resources running today.

I see some gp2 usage there so I want to remind you that gp2 is slower **and** expensive compared to gp3. So unless it is 
rootfs it does not make sense to allocate it.




FedoraGroup: qa
 Region: us-east-1
   Service Name:
   Instance Type: c5n.metal - Count: 6
   Instance Type: c6a.8xlarge - Count: 1
   Instance Type: i4i.32xlarge - Count: 2
   Instance Type: c6in.metal - Count: 4
   Volume Type: gp3 - Total Size: 7000 GiB
   Volume Type: io1 - Total Size: 5000 GiB

FedoraGroup: coreos
 Region: ap-south-2
   Service Name:
   # of AMIs: 280
 Region: ap-south-1
   Service Name:
   # of AMIs: 700
 Region: eu-south-1
   Service Name:
   # of AMIs: 659
 Region: eu-south-2
   Service Name:
   # of AMIs: 280
 Region: me-central-1
   Service Name:
   # of AMIs: 336
 Region: il-central-1
   Service Name:
   # of AMIs: 172
 Region: ca-central-1
   Service Name:
   # of AMIs: 700
 Region: eu-central-1
   Service Name:
   # of AMIs: 700
 Region: eu-central-2
   Service Name:
   # of AMIs: 280
 Region: us-west-1
   Service Name:
   # of AMIs: 700
 Region: us-west-2
   Service Name:
   # of AMIs: 700
 Region: af-south-1
   Service Name:
   # of AMIs: 672
 Region: eu-north-1
   Service Name:
   # of AMIs: 700
 Region: eu-west-3
   Service Name:
   # of AMIs: 700
 Region: eu-west-2
   Service Name:
   # of AMIs: 700
 Region: eu-west-1
   Service Name:
   # of AMIs: 700
 Region: ap-northeast-3
   Service Name:
   # of AMIs: 589
 Region: ap-northeast-2
   Service Name:
   # of AMIs: 700
 Region: me-south-1
   Service Name:
   # of AMIs: 696
 Region: ap-northeast-1
   Service Name:
   # of AMIs: 700
 Region: sa-east-1
   Service Name:
   # of AMIs: 700
 Region: ap-east-1
   Service Name:
   # of AMIs: 696
 Region: ca-west-1
   Service Name:
   # of AMIs: 86
 Region: ap-southeast-1
   Service Name:
   # of AMIs: 700
 Region: ap-southeast-2
   Service Name:
   # of AMIs: 700
 Region: ap-southeast-3
   Service Name:
   # of AMIs: 478
 Region: ap-southeast-4
   Service Name:
   # of AMIs: 172
 Region: us-east-1
   Service Name:
   # of AMIs: 4502
 Region: us-east-2
   Service Name:
   # of AMIs: 700

FedoraGroup: copr
 Region: us-east-1
   Service Name:
   Instance Type: t3a.medium - Count: 3
   Instance Type: r5a.large - Count: 1
   Instance Type: t3a.small - Count: 1
   Instance Type: r7a.xlarge - Count: 1
   Instance Type: c7a.4xlarge - Count: 1
   Instance Type: m5a.4xlarge - Count: 1
   Instance Type: t3a.2xlarge - Count: 1
   Instance Type: c7i.xlarge - Count: 51
   Instance Type: c7g.xlarge - Count: 112
   Instance Type: c7a.large - Count: 1
   Volume Type: gp3 - Total Size: 10160 GiB
   Volume Type: sc1 - Total Size: 81652 GiB
   Volume Type: st1 - Total Size: 7500 GiB
   Volume Type: io2 - Total Size: 20 GiB
   # of AMIs: 5

FedoraGroup: abrt
 Region: us-east-1
   Service Name:
   Instance Type: t3a.2xlarge - Count: 1
   Volume Type: gp3 - Total Size: 10 GiB

FedoraGroup: pyai
 Region: us-east-1
   Service Name:
   Instance Type: t2.large - Count: 1
   Instance Type: i3.16xlarge - Count: 1

FedoraGroup: Not tagged
 Region: ap-south-1
   Service Name:
   # of AMIs: 328
 Region: eu-south-1
   Service Name:
   # of AMIs: 90
 Region: il-central-1
   Service Name:
   # of AMIs: 87
 Region: ca-central-1
   Service Name:
   # of AMIs: 326
 Region: eu-central-1
   Service Name:
   # of AMIs: 336
 Region: us-west-1
   Service Name:
   # of AMIs: 339
 Region: us-west-2
   Service Name:
   # of AMIs: 341
 Region: af-south-1
   Service Name:
   # of AMIs: 90
 Region: eu-north-1
   Service Name:
   # of AMIs: 90
 Region: eu-west-3
   Service Name:
   # of AMIs: 90
 Region: eu-west-2
   Service Name:
   # of AMIs: 340
 Region: eu-west-1
   Service Name:
   # of AMIs: 333
 Region: ap-northeast-2
   Service Name:
   # of AMIs: 328
 Region: me-south-1
   Service Name:
   # of AMIs: 90
 Region: ap-northeast-1
   Service Name:
   # of AMIs: 328
 Region: sa-east-1
   Service Name:
   # of AMIs: 333
 Region: ap-east-1
   Service Name:
   # of AMIs: 90
 Region: ap-southeast-1
   Service Name:
   # of AMIs: 334
 Region: ap-southeast-2
   Service Name:
   # of AMIs: 331
 Region: us-east-1
   Service Name:
   Instance Type: c6a.2xlarge - Count: 4
   Volume Type: gp3 - Total Size: 2288 GiB
   Volume Type: gp2 - Total Size: 1000 GiB
   Volume Type: io1 - Total Size: 1000 GiB
   # of AMIs: 419
 Region: us-east-2
   Service Name:
   Instance Type: c5.2xlarge - Count: 9
   Instance Type: p3.2xlarge - Count: 1
   Instance Type: m5.2xlarge - Count: 1
   Volume Type: gp3 - Total Size: 1088 GiB
   Volume Type: gp2 - Total Size:

Re: Deleting old AMIs in AWS

2024-07-01 Thread Kevin Fenzi
On Sun, Jun 30, 2024 at 06:52:53PM GMT, Miroslav Suchý wrote:
> Dne 26. 06. 24 v 11:43 odp. Miroslav Suchý napsal(a):
> > > I deregister all AMIs without FedoraGroup tag that are older than
> > > 2020-01-01. This was in all regions. Snapshots are still there.
> > 
> > I continued with all older than 2021-01-01.
> 
> I continued with all older than 2022-01-01.
> 
> 797 AMIs deregistered.
> 
> The log is here: https://k00.fr/a5oqhiho
> 
> 
> FYI - My next intent. Do one more run for AMIs older than 2023 in few days.
> Then I will pause (because PTOs. In August start deleting snapshots that
> were left behind AMIs.
> And in September continue with deleting most recent AMIs.

ok. Sounds good!

kevin


signature.asc
Description: PGP signature
-- 
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue