If your company already pays for AWS Support, it is reasonable to ask a simple question:
Why would we need another AWS management service on top of it?
It is a particularly relevant question right now. AWS has introduced a new generation of Support plans, while several plans customers have used for years are approaching end of support.
But AWS Support and a managed AWS service are not necessarily competing products. They approach cloud operations from different angles.
Below, we’ll look at what is changing with AWS Support and how the new plans compare with Cloudvisor Managed Service (CMS).
What is changing with AWS Support?
AWS now offers three premium Support plans: Business Support+, Enterprise Support and Unified Operations. Basic Support continues to be included for all AWS customers.
At the same time, Developer Support, the previous Business Support plan and Enterprise On-Ramp will all be discontinued on January 1, 2027.
Developer Support and Business Support customers can continue using their existing plans until then or move to Business Support+ before the end-of-support date. Enterprise On-Ramp customers are being automatically upgraded to Enterprise Support during 2026, with AWS notifying customers before the upgrade.
The three premium plans have very different starting prices:
- Business Support+: $29/month minimum per account
- Enterprise Support: $5,000/month minimum
- Unified Operations: $50,000/month minimum
For the highest-severity incidents, AWS lists initial human response targets of under 30 minutes with Business Support+, under 15 minutes with Enterprise Support, and under 5 minutes from an Incident Management Engineer with Unified Operations. AWS notes that these are response targets for which it makes every reasonable effort.
The newer plans also place considerable emphasis on AI-assisted operations.
Business Support+ combines AI-powered troubleshooting with 24/7 access to AWS experts, Trusted Advisor, AWS Health and AWS DevOps Agent capabilities. Enterprise Support adds a designated Technical Account Manager and broader proactive guidance, while Unified Operations includes additional specialist expertise and 24/7 workload monitoring.
These are meaningful capabilities.
But they also raise a broader question:
How should AWS Support fit into the way your team manages its cloud environment day to day?
AWS Support vs Cloudvisor CMS: What’s the difference?
AWS Support provides tools, troubleshooting capabilities and access to AWS expertise.
Depending on the plan, this can include AI-powered investigations, AWS Support Engineers, Trusted Advisor, AWS Health, architectural guidance, cost optimisation recommendations, proactive reviews and Technical Account Managers.
Cloudvisor Managed Service (CMS) is positioned differently.
Cloudvisor’sCMS as a fully managed AWS DevOps service and an outsourced DevOps function. It includes proactive monitoring and alerts, infrastructure checks, ongoing improvements, security audits, continuous FinOps work and what’s most important – direct access to AWS-certified DevOps engineers.
So rather than viewing them simply as competing support products, it is more useful to compare their service models.
| AWS Support | Cloudvisor Managed Service | |
| Service model | AWS Support plans combining tools, AI-powered troubleshooting and access to AWS experts | Fully managed AWS DevOps service |
| Expert support | 24/7 technical support with all three premium plans (no hands-on work included!) | Direct access to AWS-certified DevOps engineers |
| Monitoring | AWS Health, Trusted Advisor and DevOps Agent capabilities; 24/7 workload monitoring with Unified Operations | Continuous monitoring, alerts and ongoing maintenance |
| Cost optimisation | Trusted Advisor and AI-powered cost optimisation recommendations | Continuous AWS cost optimisation and FinOps work done by a human Engineer |
| Security | Security recommendations and proactive services depending on the Support plan | Security audits, monitoring and compliance support |
| Ongoing infrastructure work | Support tooling, troubleshooting, automation and expert guidance | Ongoing maintenance and continuous infrastructure improvements |
| 24/7 support | Included with premium AWS Support plans | Available as an add-on to CMS |
AWS Support is becoming increasingly proactive and automated, particularly with the introduction of AWS DevOps Agent and the capabilities available in the higher Support tiers.
Cloudvisor CMS, meanwhile, explicitly focuses on continuous infrastructure management. Cloudvisor states that its engineers take over daily monitoring and maintenance, conduct recurring reviews and provide ongoing recommendations and improvements.
That is the key distinction.
Where does a managed AWS service add value?
Consider a common situation: your AWS tools identify an opportunity to improve cost, security, reliability or performance.
Modern AWS Support can help investigate issues, provide contextual recommendations and, through services such as AWS DevOps Agent, generate remediation plans and help resolve incidents.
Cloudvisor CMS approaches the same environment from the perspective of continuous management.
Its service begins with an assessment of the AWS infrastructure, followed by onboarding of monitoring and alerts. Cloudvisor then provides ongoing maintenance, including bi-weekly infrastructure checks, security work, cost optimisation and monthly improvement recommendations.
For companies without dedicated AWS or cloud operations capacity, a managed service can provide the most immediate value by adding continuous attention and clear ownership around the environment.
But CMS can also strengthen teams that already have internal DevOps or technical resources. General DevOps expertise does not always mean deep AWS-specific knowledge, and CMS can add an extra layer of AWS expertise around architecture, security, cost optimisation and ongoing infrastructure improvements.
In that setup, Cloudvisor works alongside the existing team rather than replacing it, providing additional AWS-focused expertise and capacity where needed.
There is also a cost angle
AWS Support pricing is partly linked to AWS usage.
For Business Support+, AWS currently charges whichever is greater: the $29 monthly minimum per account or a tiered percentage of monthly AWS charges:
- 9% up to $10,000
- 7% from $10,000 to $80,000
- 5% from $80,000 to $250,000
- 3% above $250,000
Enterprise Support starts at a $5,000 monthly minimum and uses separate percentage bands, beginning at 10% of monthly AWS charges up to $150,000. Unified Operations similarly uses a $50,000 monthly minimum or its applicable percentage-based calculation.
AWS states that Support fees are calculated using monthly gross AWS charges before discounts or credits, while certain AWS services are excluded from the calculation.
This makes ongoing cost management relevant not only to your underlying AWS bill but, in cases where percentage-based Support pricing applies, potentially to the Support fee calculation as well.
Cloudvisor Managed Service uses a different pricing model. Instead of charging a percentage-based AWS Support fee, CMS pricing scales with your monthly AWS spend and starts from €650 per month. There is no long-term commitment, and the service can be cancelled monthly. For teams that need round-the-clock coverage, 24/7 support is also available as an add-on.
This means the cost of CMS is tied to the level of AWS infrastructure being managed, while the service itself includes continuous monitoring, maintenance, security reviews, FinOps and access to AWS-certified DevOps engineers.
Why Cloudvisor CMS adds more than AWS Support alone
AWS Support is valuable for getting direct access to AWS expertise, troubleshooting and escalation when you need it. But it is not designed to become an extension of your team that continuously manages and improves your AWS environment.
That is where Cloudvisor Managed Service adds value.
CMS gives you an ongoing AWS-focused DevOps function that works proactively across monitoring, maintenance, security, cost optimisation and infrastructure improvements. Instead of only helping when an issue appears, Cloudvisor’s engineers continuously look for ways to keep your AWS environment more reliable, secure and cost-efficient.
For teams without dedicated cloud expertise, CMS can effectively provide that missing AWS operations layer. For companies that already have DevOps or technical resources in-house, it adds an extra layer of AWS-specific expertise and capacity without the need to hire another specialist internally.
AWS Support and CMS can work alongside each other, but they solve different needs. AWS gives you access to the platform and its support ecosystem, while Cloudvisor CMS gives you a team focused on the ongoing work required to keep your AWS environment performing at its best.
For companies that want more than support tickets and recommendations, CMS provides the hands-on AWS expertise needed to turn those insights into continuous improvements.
When does a managed AWS service make sense?
Whether a managed service makes sense depends heavily on the resources and expertise already available inside your team.
Cloudvisor positions CMS particularly for companies that run on AWS but do not have a dedicated DevOps team, are experiencing growing infrastructure costs or performance challenges, or want more proactive maintenance and security.
If your organisation already has a mature DevOps function continuously monitoring, maintaining and optimising AWS, an appropriate AWS Support plan may provide much of the additional AWS-specific expertise you need.
If AWS operations regularly compete with product development for your team’s attention, a managed service can provide additional operational capacity.
Cloudvisor CMS is built around that model: ongoing monitoring, maintenance, security and FinOps work carried out by AWS-certified engineers while the customer’s internal team stays focused on its own priorities.
Situations Cloudvisor CMS is designed for
Cloudvisor Managed Service is designed for AWS environments where ongoing monitoring, optimisation, security and operational support need more structured attention. Typical situations include:
| Situation | Relevant parts of the service |
| A growing SaaS platform on AWS hitting performance bottlenecks and unplanned downtime, with the internal team occupied by reactive fixes | Bi-weekly checks, continuous monitoring, and scaling guidance covering Graviton, serverless, and Kubernetes |
| A completed migration with no defined maintenance strategy, where configuration drift and security gaps are a concern | Drift detection, continuous configuration monitoring, and scheduled best-practice updates |
| A requirement for continuous security monitoring and compliance adherence (PCI DSS, SOC 2, GDPR) | Periodic security audits, conformance monitoring, and IAM and security group review |
| AWS spend increasing without a structured efficiency process | FinOps dashboards, ongoing rightsizing, reserved instance and savings plan review, and analysis of serverless, spot, and autoscaling options |
| A mission-critical application where downtime is not acceptable | Real-time monitoring, 30-minute Tier 2 response, and reliability planning including multi-region failover and disaster recovery |
The AWS Support changes are a good time to review your setup
With Developer Support, Business Support and Enterprise On-Ramp reaching end of support on January 1, 2027, many AWS customers now have a natural reason to review their Support setup.
But choosing the right AWS Support plan is only one part of the picture.
It is also worth asking:
Do we have the right people and processes in place to continuously manage, secure and optimise our AWS environment?
For some companies, the answer will be an internal DevOps team supported by AWS.
For others, adding an ongoing managed AWS service can provide the operational capacity they are missing.
Want to see whether Cloudvisor CMS fits your AWS setup?
If your team wants more continuous AWS monitoring, maintenance, security and cost optimisation without building a dedicated DevOps function internally, Cloudvisor Managed Service may be worth exploring.
Talk to Cloudvisor about your AWS environment and find out whether CMS is the right fit for your team.
Frequently asked questions
- How does CMS compare to an in-house DevOps team?
CMS provides AWS-certified engineers, monitoring tooling, and continuous improvement work at a lower total cost than a full in-house team, without recruitment or management overhead. It is not a substitute for engineering ownership of the product itself.
- Can the audit be purchased on its own?
Yes. The WAFR and improvement roadmap are self-contained deliverables, and the engagement can end there. Most customers continue into maintenance.
- How is the environment monitored?
Grafana-based dashboards, AWS-native monitoring services, and conformance packs covering security, performance, and cost. Alerts route to a dedicated Slack channel, and the assigned engineer reviews the data as part of the bi-weekly checks.
- Is 24/7 support included?
24/7 support is available as an add-on. Tier 2 business-critical response (30 minutes) applies within the agreed coverage hours.
- Who is the day-to-day contact?
An assigned DevOps Engineer and a Project Manager, reachable in the dedicated Slack channels. The same engineer performs the bi-weekly reviews, so context carries across requests.
- What is the timeline to get started?
Two weeks for the audit and assessment, one week for activation, then continuous maintenance with bi-weekly reviews. Full onboarding takes approximately one month.


