Now you can check which AWS services will definitely never appear (Not Expanding) in your desired region:
https://builder.aws.com/build/capabilities/explore?tab=service-feature
And which ones are only in the backlog (Planning) or are already in development and have release dates (2026 Q3).
#aws #cloud
https://builder.aws.com/build/capabilities/explore?tab=service-feature
And which ones are only in the backlog (Planning) or are already in development and have release dates (2026 Q3).
#aws #cloud
Forwarded from CatOps
An interesting lab for an overengineered solution from AWS for Kubernetes workloads right sizing.
Should you implement it this way? I don't know. But maybe, you want to play with GitOps, AWS Bedrock and all that stuff.
Also, it's funny how they say in the beginning that having VPA and Goldilocks inside a cluster is an overhead and additional management burden and then propose to create a cluster in GHA runtime and use generative AI to address that.
#aws #kubernetes
Should you implement it this way? I don't know. But maybe, you want to play with GitOps, AWS Bedrock and all that stuff.
Also, it's funny how they say in the beginning that having VPA and Goldilocks inside a cluster is an overhead and additional management burden and then propose to create a cluster in GHA runtime and use generative AI to address that.
#aws #kubernetes
Amazon
Kubernetes right-sizing with metrics-driven GitOps automation | Amazon Web Services
In this post, we introduce an automated, GitOps-driven approach to resource optimization in Amazon EKS using AWS services such as Amazon Managed Service for Prometheus and Amazon Bedrock. The solution helps optimize Kubernetes resource allocation through…