Overview
Cisco Application Services Engine is a unified platform designed to run Day 2 operations applications such as Cisco Network Insights , Cisco Network Assurance Engine and Cisco ACI Multi-Site Orchestrator (MSO). With this offering, Cisco is extending the capabilities of the Cisco Application Services Engine to the AWS cloud. Running natively on AWS infrastructure the Cisco Application Services Engine is now able to run the Cisco ACI Multi-Site Orchestrator (MSO) in the cloud allowing customers to run a cloud-only Cisco ACI infrastructure. The Cisco Application Services Engine is deployed as a 3 -node EC2 cluster via a Cloud Formation template. The Cisco Application Services Engine will also run the various Day 2 Operations applications such as Cisco Network Insights and Cisco Network Assurance Engine in the future.
Highlights
- Cloud-only ACI support: Customers can now run their Cisco ACI Multi-Site Orchestrator (MSO) in a cloud-only Cisco ACI model to support their multi-cloud deployment.
- Modern microservices architecture: Applications running on the Cisco Application Services Engine can take advantage of a modern microservices architecture and re-usable platform services such as ElasticSearch and Kafka for a modular maintenance approach. Kubernetes orchestration is used for lifecycle management of the applications running on the Cisco Application Services Engine.
- Scale-out architecture: As the application needs for compute and storage grow, the cluster can scale horizontally to fit these needs.
Details
Features and programs
Buyer guide

Financing for AWS Marketplace purchases
Pricing
Vendor refund policy
The Cisco Application Services Engine AMI utilizes subscription base licenses purchased directly from Cisco or Cisco partners. Please contact your Cisco sales team or partner for refund information.
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
Cisco Application Services Engine for Cloud
Cisco Application Services Engine is a unified platform designed to run day 2 ops applications such as CIsco Network Insights ,Cisco Network Assurance Engine and Cisco ACI Multi-Site Orchestrator (MSO). With this offering Cisco is extending the capabilities of the Cisco Application Services Engine to the AWS cloud.Running natively on AWS infrastruture the Cisco Application Services Engine is now able to run the Multi-site orchestrator in the cloud allowing customers to run a cloud-only ACI infrastructure. The Cisco Application Services Engine will also run the various Day 2 ops such as Network Insights and assurance in the future. https://www.cisco.com/c/en/us/products/collateral/data-center-analytics/network-insights-data-center/datasheet-c78-742892.html
CloudFormation Template (CFT)
AWS CloudFormation templates are JSON or YAML-formatted text files that simplify provisioning and management on AWS. The templates describe the service or application architecture you want to deploy, and AWS CloudFormation uses those templates to provision and configure the required services (such as Amazon EC2 instances or Amazon RDS DB instances). The deployed application and associated resources are called a "stack."
Version release notes
First Release
Additional details
Usage instructions
Complete the following steps to launch a Cisco Application Services Engine : After the Cloud formation deployment, access the Cisco Application Services Engine cluster via a browser at https://<public_dns_name>. To connect to the CLI use SSH and the username admin.
Resources
Support
Vendor support
Cisco TAC supports BYOL AMI customer's only after a license is purchased from Cisco or a reseller. To set up Cisco Application Services Engine read the Installation guide at :- https://www.cisco.com/c/en/us/td/docs/data-center-analytics/service-engine/APIC/1-1-2/installation-guide/b-cisco-application-services-engine-installation-guide-release-1-1-2/m-deploying-the-cisco-application-services-engine-in-aws.html
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
Similar products
Customer reviews
Template-based automation has reduced outages and now improves daily network operations
What is our primary use case?
My main use case for Cisco Nexus Dashboard involves using NDFC fabric. We have onboarded an EVPN VXLAN based NDFC fabric, and we use Cisco Nexus Dashboard to monitor switch performance, connectivity, topology, and configure policies.
Using Cisco Nexus Dashboard for monitoring and configuring policies helps my team on a daily basis because we use template-based deployment, making it easy to follow the same template for similar kinds of deployment. This speeds up the process, is efficient, and reduces the chance of getting an error.
We coordinate firmware upgrades, maintenance windows, and policy synchronization across disparate ACI fabrics and NX-OS environments using Cisco Nexus Dashboard by taking a maintenance window where we update the devices. We do not maintain much policy on the ACI itself. It is mainly version upgrades, software updates, or any other patching required that we do in a maintenance window when we get an outage approved by the customer.
We don't do micro-segmentation on Cisco Nexus Dashboard.
We haven't operationalized the AI-assisted predictive analytics and anomaly detection features within Cisco Nexus Dashboard for daily capacity planning and root cause analysis yet; that is in the pipeline.
What is most valuable?
The best features Cisco Nexus Dashboard offers are template-based deployment and extensive automation capabilities.
Regarding Cisco Nexus Dashboard's AI capabilities, its accuracy and reliability of output have met my expectations.
Cisco Nexus Dashboard has positively impacted my organization by improving customer experience and resiliency. Because we do template-based deployment and have high visibility on the products, it has improved performance for the workload that we host for our customers, and downtime has been low.
In terms of specific outcomes related to improved customer experience or reduced downtime, the number of Severity 1 incidents we had due to network unavailability has reduced significantly. We experience far fewer Severity 1 and Severity 2 network-related incidents since the Cisco Nexus Dashboard deployment.
What needs improvement?
I think Cisco Nexus Dashboard could be improved if I could see it onboard some of the other switching capabilities so we have a central pane of glass to monitor all the different kinds of Cisco devices we manage. I would also appreciate the possibility to onboard some third-party devices.
Regarding needed improvements, it would be beneficial if Cisco Nexus Dashboard comes with out-of-band support integrated with the deployment because the pain point is that we have to deploy an out-of-band network before we can start provisioning the actual device. If that capability were integrated, I wouldn't have to build a separate out-of-band network before provisioning Cisco Nexus Dashboard-based network. That would be helpful.
Some of the features, such as the user experience and graphical user interface for Cisco Nexus Dashboard, can be improved. Sometimes I find it difficult to navigate and find a specific feature. Even if I want to put a route policy on a device, I have to do quite a bit of clicking to figure out where I need to go to find that feature. There is room for improvement in the graphical user interface perspective to make it easier for users to find features.
Regarding Cisco Nexus Dashboard's AI capabilities, I think we need to have guardrails in place, and the guardrails should be deployed based on organizational policy. If there is a way to provision guardrails that the AI capability of Cisco Nexus Dashboard follows those policies and boundaries, that would be valuable. In that way, we can govern it while maintaining the security posture approved by the organization.
For how long have I used the solution?
I have been using Cisco Nexus Dashboard for about a year.
What was our ROI?
I have seen a return on investment with Cisco Nexus Dashboard, specifically in terms of time saved. My team has saved roughly 30% of our time since using Cisco Nexus Dashboard.
What other advice do I have?
My advice for others looking into using Cisco Nexus Dashboard is to go for it. It is a centrally managed platform that is good for visibility, automation, and template-based deployment.
Unified network monitoring has improved change control while AI features still need deeper use
What is our primary use case?
My main use cases for Cisco Nexus Dashboard are monitoring and network monitoring.
My operations teams coordinate firmware upgrades, maintenance windows, and policy synchronization across disparate ACI fabrics and NX-OS environments using Cisco Nexus Dashboard, which aligns with our change policy, which is quite strict considering that we are a critical capability across our organization. I not only use the requirements for firmware upgrades, but also address the policy requirements with embargoes and how it integrates with other products in the space.
The operational trade-offs I have encountered when managing micro-segmentation policies and role-based access control across multi-site fabrics through Cisco Nexus Dashboard center on customer impact and the nature of outages that will occur during changes. The key factor is understanding the end-user impact and what it means for the business.
My teams are operationalizing the AI-assisted predictive analytics and anomaly detection features within Cisco Nexus Dashboard for daily capacity planning and root cause analysis. This breaks down to what is on the roadmap at the moment. We are still in early stages with our AI processes, so that is part of the vision in terms of moving forward with our road mapping.
I still need to review the adjustments required in Cisco Nexus Dashboard's Fabric Controller configurations to accommodate the latency, buffer management, and bandwidth demands of AI training or high-performance compute workloads.
What is most valuable?
The features of Cisco Nexus Dashboard that I like the most are end-user usability and ease of use for monitoring the network.
The end use cases are straightforward to use with the network and my network team and group.
In terms of managing across the board, it has been straightforward and simple, so it is not a significant issue.
What needs improvement?
The areas where Cisco Nexus Dashboard can improve involve better understanding of the product and utilization of the AI features and copilot features. As part of our current road mapping with AI, we are still reviewing these capabilities, so improvements will definitely emerge as we continue to use the product.
At this stage, I have no pain points with the product that I would request Cisco to fix.
For how long have I used the solution?
I have been using Cisco Nexus Dashboard for the last 12 months.
What do I think about the stability of the solution?
At this stage, I have no issues with the reliability of Cisco Nexus Dashboard.
What do I think about the scalability of the solution?
I would describe the scalability of Cisco Nexus Dashboard as a work in progress, as we are going through a transformation at the moment in our old DNS network space. As we start growing it, I will discover more about its scalability capabilities.
How are customer service and support?
At this stage, I have no issues with Cisco support. On a scale of one to ten, I rate it a seven or eight at the moment.
What would make Cisco Nexus Dashboard a 10 for me? Ideally, the best scenarios are when I have professional teams on site, but that is not possible because of the cost factors involved, and that would definitely make it a 10. At the moment I have a good account manager from Cisco that I work with, so I have no issues there.
Which solution did I use previously and why did I switch?
Prior to Cisco Nexus Dashboard, I was not using a similar solution to address similar needs, as the solutions were very much manual and involved a lot of automation activity to get the dashboarding right. Using Cisco Nexus Dashboard as a product has facilitated and improved that and also reduced the lag or downtime, which is a significant feature.
How was the initial setup?
My team manages the transition of configuration state and operational tooling when consolidating disparate data center management utilities into a single Cisco Nexus Dashboard cluster, and it is still a work in progress at the moment.
My experience with deploying Cisco Nexus Dashboard shows that there are no major issues that would cause any problem with using the product.
What was our ROI?
I have not seen return on my investment so far from using Cisco Nexus Dashboard, as we are still familiarizing ourselves with it.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing of Cisco Nexus Dashboard is that it is still in review at the moment because we review our licensing year on year. I will provide feedback in terms of how we are using it and what the per-unit cost is for the organization.
Which other solutions did I evaluate?
I considered many solutions before selecting Cisco Nexus Dashboard, and most of them were manual-based, with Power BI being a good example. Much of it had been created by the teams themselves and customized, but when teams move on, that changes.
What other advice do I have?
From my understanding of the product, I rate Cisco Nexus Dashboard between seven and eight.
The reason I rate it seven and eight and not 10 is the full familiarization with the product and having it on site as to what we have at the moment. That would actually change the way we use the product. If we had been using it for a few years, my response would be different than as we are actually bringing it on board.
Automation has simplified daily VRF and VLAN deployments but GUI and CLI alignment needs work
What is our primary use case?
My main use case for Cisco Nexus Dashboard is automation. A specific example of a workflow I automate with Cisco Nexus Dashboard is creating a VRF and a VLAN associated with that VRF.
This workflow functions effectively for my team on a day-to-day basis as it requires only a screen click and deploy. Previously, my team had to manage a thousand lines of command lines in configuration, which is prone to human error.
In addition to my main use case, upgrading software iOS is very fast as well.
What is most valuable?
The best features Cisco Nexus Dashboard offers are mainly all GUI based, which is beneficial for junior network engineers, and at the same time, automation capabilities such as click to deploy a VLAN.
The GUI and click to deploy automation have reduced half of the resource time of the network, allowing my team to accomplish more work. Since Cisco Nexus Dashboard was newly deployed, I haven't really seen all the benefits yet.
Looking ahead, I am watching specific outcomes or metrics such as deployment time, configuration errors, and team capacity. I am looking to automate how the monitoring works for Cisco Nexus Dashboard, particularly if it is easy to monitor the switches inside Cisco Nexus Dashboard.
What needs improvement?
Cisco Nexus Dashboard could be improved in terms of the flexibility of using the CLI and the GUI because there are instances where it becomes unsynced due to CLI configurations that someone made separately.
For how long have I used the solution?
I have been using Cisco Nexus Dashboard for less than a year.
What other advice do I have?
I rate Cisco Nexus Dashboard a seven out of ten. I give Cisco Nexus Dashboard a seven out of ten because my current operation usage of the product is less than a year, so I cannot really make any recommendation.
There is no current policy in regards to coordinating firmware upgrades, maintenance windows, and policy synchronization across disparate ACI fabrics and NX-OS environments using Cisco Nexus Dashboard. However, I need to think about how to deploy or process the changes that I plan inside Cisco Nexus Dashboard.
My advice to others looking into using Cisco Nexus Dashboard is to plan ahead.
Troubleshooting has improved with deeper telemetry while integration and flexibility still need work
What is our primary use case?
Cisco Nexus Dashboard is primarily used for analytics on ACI. For upgrades, we perform them more as standalone operations on individual nodes rather than through coordinated firmware upgrades, maintenance windows, and policy synchronization across disparate ACI fabrics and NX-OS environments using Cisco Nexus Dashboard.
I should verify whether AI features are available within Cisco Nexus Dashboard and if they are included as a standard license.
What is most valuable?
The feature of Cisco Nexus Dashboard that I value most is the troubleshooting capability, which is our main use case.
We were running with single points of failure on a couple of leaf nodes and endpoints, and I gained good insight from Cisco Nexus Dashboard. While we have access to ACI where we can check independently, Cisco Nexus Dashboard provides us with better overall telemetry.
What needs improvement?
Operational trade-offs when managing micro-segmentation policies and role-based access control across multi-site fabrics through Cisco Nexus Dashboard is something we have yet to develop. Currently, we have things spread out across ICE, ACI, and different identities that we use. We would prefer to have one identity and integrate across end-to-end, but it does not seem to be that straightforward. We will need to first address segmentation before we can pursue this option, so this may be on our horizon in approximately a year.
At this point, Cisco Nexus Dashboard is either functional or non-functional for us. If it incorporated more security products, then it could serve as a single point of dashboard that we could use.
For how long have I used the solution?
I have been using Cisco Nexus Dashboard for around three years.
What do I think about the stability of the solution?
I assess Cisco Nexus Dashboard as stable and reliable. There has been no downtime.
What do I think about the scalability of the solution?
I do not think we will need to scale Cisco Nexus Dashboard because our ACI environment is sufficient for us at this point.
How are customer service and support?
I have used the customer service and technical support, and they were adequate. I would rate them on a scale of one to ten, with one being worst and ten being best, as seven or eight.
Which solution did I use previously and why did I switch?
Prior to adopting Cisco Nexus Dashboard, we were using another solution that was more of a network performance monitoring platform rather than this one because it provides all products rather than just this.
How was the initial setup?
I would describe my experience deploying Cisco Nexus Dashboard as follows: we received it ready-made, so I did not really do anything initially. However, we upgraded it, and the process was smooth with no issues encountered. Operation-wise, the experience was acceptable.
What about the implementation team?
We managed the transition of configuration state and operational tooling when consolidating disparate data center management utilities into a single Cisco Nexus Dashboard cluster through an integrator when we installed our new big leaf and spine. It was a ready-made solution for us, and we did not implement it ourselves.
What was our ROI?
If I had to purchase Cisco Nexus Dashboard independently, I would not necessarily do so because it was part of a bundle, and we are using it. That is the reality of our situation.
What's my experience with pricing, setup cost, and licensing?
I think the pricing, setup, and licensing for Cisco Nexus Dashboard were handled as a bundle. It has been in place for a couple of years, and then we will revisit.
What other advice do I have?
On a scale of one to ten, with one being worst and ten being best, I would rate Cisco Nexus Dashboard overall as a six or seven. I would say a six because it does not give me the flexibility to check other vendors.
Centralized automation has accelerated multi-site changes but still needs fewer bugs and better security
What is our primary use case?
My main use case for Cisco Nexus Dashboard is managing Nexus 9K for a customer environment.
A specific example of what I manage through Cisco Nexus Dashboard day-to-day is the multi-site fabric, pushing configs such as adding new VRFs and VLANs.
Using Cisco Nexus Dashboard has changed the way I roll out deployments by simplifying multi-site management because I can push to different data centers simultaneously.
What is most valuable?
The best features Cisco Nexus Dashboard offers include automation at a high level for Nexus spine-and-leaf architecture.
That high-level automation helps my team tremendously in the day-to-day management of Nexus fabric by saving time.
I am specifically interested to see Hypershield and integration with Cisco Nexus Dashboard.
Cisco Nexus Dashboard has impacted my organization positively, particularly for customers.
For our customers, I have seen specific outcomes such as faster changes, and software versions continue to improve as we move to version 4.3.
Customers save significant time when rolling out a change across multiple data centers; for example, a six-hour change requiring configuration of approximately twenty Nexus 9K devices can be completed in less than an hour by deploying the config.
What needs improvement?
Cisco Nexus Dashboard can be improved by having fewer bugs and fewer vulnerabilities, and regarding multicast functionality.
The operational trade-offs I have encountered when managing micro-segmentation policies and role-based access control across multi-site fabrics through Cisco Nexus Dashboard represent areas for improvement; rather than going with individual ACLs, I would prefer something similar to Hypershield for automated micro-segmentation.
For how long have I used the solution?
I have been using Cisco Nexus Dashboard for approximately three years.
What do I think about the stability of the solution?
I would say Cisco Nexus Dashboard is sixty percent stable.
Upgrade processes are always complex with Cisco NDFC, and transitioning from one version to another is too time-consuming and requires coordination.
What do I think about the scalability of the solution?
Cisco Nexus Dashboard is scalable to a good level.
How are customer service and support?
Customer support is good.
Which solution did I use previously and why did I switch?
I did not previously use a different solution; this tool is primarily used to manage Nexus or Cisco products.
What was our ROI?
The time saved is significant, but I cannot disclose additional details.
What other advice do I have?
On a scale of one to ten, I would rate Cisco Nexus Dashboard overall as a seven.
I rate it seven because there is still room for improvements; however, I have an automated tool from Cisco to manage Nexus 9K.
Regarding Cisco Nexus Dashboard's AI capabilities, I am new to the security portion of NDFC AI.
I am mainly referring to governance policies when discussing access controls, data protection, or governance policies.
When it comes to AI output, some manual intervention is needed, especially when changes are made to the environment.
Cisco Nexus Dashboard is deployed in my organization on-premises.
My operations teams coordinate firmware upgrades, maintenance windows, and policy synchronization across disparate ACI fabrics and NX-OS environments using Cisco Nexus Dashboard through manual coordination.
My teams have operationalized the AI-assisted predictive analytics and anomaly detection features in Cisco Nexus Dashboard for daily capacity planning and root cause analysis, though I cannot provide extensive details due to the criticality and privacy of my customers' environments.
No adjustments were needed in Cisco Nexus Dashboard to support those workloads.
The advice I would give to others looking into using Cisco Nexus Dashboard is that it is the only tool available from Cisco's platform for Nexus switches, but I am mostly interested in the next phase of NDFC with hyper-scale capabilities.