Fully Control Your Project’s Resource Limits and Regional Restrictions with emma

In today’s multi-cloud and hybrid environments, cloud costs can quickly spiral out of control. With development teams often provisioning the resources they need for their projects, platform engineers, cloud architects, and IT admins face challenges in curbing cost overruns and preventing resource wastage. Project managers also struggle to restrict deployment regions based on compliance and performance needs. Without the right controls, workloads can end up in regions or on providers that don’t meet regulatory, security, or performance requirements.

This is where emma’s Project Limits feature steps in. By providing powerful controls in two key areas – resources and costs and providers and regions – the emma cloud management platform helps you maintain proactive control over your cloud projects, ensuring costs remain within budget and deployments are secure and compliant.

Introducing emma’s Project Limits

The emma platform’s Project Limits feature allows users to place boundaries on two critical aspects of cloud-based projects:

• Projects’ resource consumption and costs.
• Providers and regions across which projects can be deployed.

These controls help organizations ensure that each project stays within budget and adheres to organizational policies.

1. Project Limits for Resources and Costs

This feature allows users to set boundaries on their cloud resources and project costs.

What you can do

For each project, you can:  

• Set Limits on Monthly Project Costs and Resources: You can place limits on how much your team can spend per project and how much storage, vCPUs, and vRAM the project’s virtual machines (VMs) can use.
• Track Utilization: The emma platform’s dashboard displays bar indicators showing how much of the set limits have been used, helping you identify when resources are approaching critical levels.
• Project Resource Consumption Report: Teams can see a real-time summary of the current costs and resource usage. The parameters covered are: some text
  • Cost of all services per month
  • Number of vCPUs used across your project services
  • Memory (vRAM) used across your project services in GBs
  • Storage used across your project services in GBs

Who is this for?

This feature is especially useful for companies managing multiple projects across different cloud environments. With emma's Project Limits for resources and costs, they can set a monthly cost cap to avoid unexpected cloud bills and make sure each project stays within budget.

Additionally, they can set limits on storage, vRAM, and the number of vCPUs per virtual machine, preventing over-provisioning of resources. With the emma platform’s real-time visibility into cost and resource consumption, each team can proactively monitor and optimize their resource usage, so projects can run more efficiently over time.

How-to Guide

1. To set or change project limits:
2. Navigate to “All Projects.”
3. Select your project and, by default, land on the “Summary” link in the sidebar.
4. Go to “Settings” and then select the “Limits” tab under the “General” settings.

*All limits are initially set to Unlimited. You can manually adjust these values as needed.

2. Project Limits for Providers and Regions

The emma Platform’s Project Limits feature for providers and regions gives teams control over where their virtual machines can be deployed, ensuring that project deployments align with compliance requirements and performance needs.

What You Can Do

For each project, you can place restrictions on:

• Cloud Providers: Block or allow cloud providers for virtual machine operations.
• Regions: For each provider, specify which regions are approved for creating, transferring, or cloning VMs.

Who is it for?

Organizations handling sensitive data must ensure it is processed in secure and compliant platforms and regions. With emma’s Project Limits for providers and regions, they can block the deployment of sensitive workloads on cloud providers and regions that do not meet specific compliance requirements. For instance, for projects processing sensitive data, organizations can restrict deployments to local providers or specific AWS and Azure regions that are fully GDPR compliant.

This feature is also useful for projects with specific performance needs. DevOps can restrict cloud regions based on proximity to their user base to minimize latency and improve application responsiveness.

How-to Guide

1. Navigate to “All Projects.”
2. Select your project and click the “Summary” link in the sidebar.
3. Go to “Settings” > “Limits.”
4. Click the “Providers” tab, and under “Allowed Locations,” manage your approved providers and regions.

*These controls do not apply to spot instances, application nodes, or Kubernetes cluster nodes.

Take control of your cloud projects. Request a free demo to try emma’s Project Limits feature today and start managing your resources and providers with ease!