Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Run ECS/EKS AMI monitoring script #8886

Open
3 tasks
Khatraf opened this issue Jan 9, 2025 · 0 comments
Open
3 tasks

Run ECS/EKS AMI monitoring script #8886

Khatraf opened this issue Jan 9, 2025 · 0 comments

Comments

@Khatraf
Copy link
Contributor

Khatraf commented Jan 9, 2025

User Story

As a MP engineer
I want to monitor the versions of ECS/EKS-optimised AMIs in use by members' clusters
So that I can notify members when their AMIs are outdated

Value / Purpose

Following on #8329, this issue is to run the ECS/EKS AMI script. Any accounts found using outdated AMIs should be flagged, and the relevant teams should be notified. Analytical Platform and data-platform-apps-and-tools can be ignored.
Additionally, it can be recommended that teams consider using the SSM Parameter resolve syntax to automatically reference the latest ECS/EKS AMI. This approach ensures that instances always launch with the latest AMI, eliminating the need to manually update or re-apply Terraform when using a data call.

Context / Background

#6317 - requirement originated from this spike ticket.

Useful Contacts

No response

Additional Information

No response

Definition of Done

  • The ECS/EKS outdated AMI monitoring script is successfully executed across all accounts
  • Accounts that are found to have outdated AMIs contacted for remediation
  • Raise another follow on ticket for script to be run again in 2-3 months if needed
@Khatraf Khatraf changed the title Second Phase: Running ECS/EKS AMI monitoring script Run ECS/EKS AMI monitoring script Jan 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: To Do
Development

No branches or pull requests

1 participant