Qovery now supports AWS STS: Protect your resources with temporary access keys
Using STS is a great way to enhance the security of your AWS account and protect your resources. STS enables you to grant trusted users with temporary access to your resources rather than giving them long-term access keys. This is especially useful when you have a large number of users or when you want to grant access to third-party applications.
To set up STS with Qovery, follow this tutorial. This tutorial will walk you through the process of creating an IAM role and granting permissions to access your managed resources by Qovery.
Once you have set up STS with Qovery's Kubernetes management solution, you can use it to grant temporary access to all your Qovery services (applications, containers, cronjob, lifecycle jobs...) This will allow you to control and monitor access to your resources more effectively, ensuring that only authorized services can access them.
This new feature is available to all our customers, regardless of their plan. If you have any questions or need help with setting up STS with Qovery, don't hesitate to reach out to our support team. We hope that this new feature will help you to manage better and secure your AWS resources.
Tutorial: https://hub.qovery.com/guides/tutorial/use-aws-iam-roles-with-qovery/
.svg)
.svg)
.svg)
Suggested articles
The cluster coming up is the easy part. What catches teams off guard is what happens six months later: certificates expire without a single alert, node pools run at 40% over-provisioned because nobody revisited the initial resource requests, and a manual kubectl patch applied during a 2am incident is now permanent state. Agentic control planes enforce declared state continuously. Monitoring tools just report the problem.
The instinct when setting up Kubernetes observability is to instrument everything and send it all to your APM vendor. That works fine at ten nodes. At a hundred, the bill becomes a board-level conversation. The less obvious problem is the fix most teams reach for: aggressive sampling. That is how intermittent failures affecting 1% of requests disappear from your monitoring entirely.
Scaling your deployments to zero is only half the battle. If your cluster autoscaler does not aggressively bin-pack and terminate the underlying worker nodes, you are still paying for idle metal. True environment sleeping requires tight integration between your ingress layer and your node provisioner to actually realize FinOps savings.
The structure, table, tool list, and code blocks are all worth keeping. The main work is fixing AI-isms in the prose, updating the case study to real metrics, correcting the FAQ format, and replacing the CTAs with the proper HTML blocks. The tool descriptions need the "Core strengths / Potential weaknesses" headers made less template-y, and the intro needs a sharper human voice.
For years, Red Hat OpenShift has been the safe choice for heavily regulated, on-premise environments. It operates as a secure fortress. But in the public cloud, that fortress acts as an expensive prison. Paying proprietary per-core licensing fees on top of your standard AWS or GCP compute bill is a redundant "middleware tax." Escaping OpenShift requires decoupling your infrastructure from your developer experience by running standard, vanilla Kubernetes paired with an agentic control plane.
Agentic Kubernetes resource reclamation is the practice of using an autonomous control plane to continuously identify, suspend, and delete idle infrastructure across a multi-cloud Kubernetes fleet. It replaces manual cleanup and reactive autoscaling with intent-based policies that act on business state, eliminating the configuration drift and cloud waste typical of unmanaged fleets.
Kubernetes focuses on container orchestration, but the reality on the ground is far less forgiving. Provisioning a single cluster is a trivial Day-1 exercise. The true operational nightmare begins on Day 2. Teams that treat multi-cloud fleets like isolated pets inevitably face crushing YAML configuration drift, runaway AWS bills, and severe scaling bottlenecks.
.webp)