For CloudOps and FinOps leads, this video demonstrates how to set project-level limits on emma. The workflow shows how to define guardrails for costs, resources (CPU count, RAM, storage), and cloud providers, so they can maintain control over cloud usage and enforce consistent governance across projects.
What’s shown in the demo
Navigating to project limits: How to access the project settings and open the limits section.
Managing cloud provider limits: How to enable or disable specific cloud providers and restrict them by region. For example, disabling AWS or limiting available locations for a provider.
Setting resource limits: How to define maximums for cost, CPU count, RAM, and storage to prevent projects from exceeding allocated resources.
Applying and verifying limits: How to save changes and confirm that virtual machines or other resources now respect the configured project limits.
Key takeaway
The workflow provides a clear and structured way to enforce project-level guardrails, ensuring infra teams, project leaders, and admins can control costs, allocate resources efficiently, and manage cloud usage consistently across projects.
.png){kind=small}
