
Overview

Product video
Pulse Secure® Virtual Traffic Manager is a high-performance Layer 7 load balancer & application delivery controller that enables you to offer High Availability through active-active deployment as well as create & manage & deliver services more quickly & flexibly. Highly portable, it can be deployed in any major cloud or hybrid environment. It controls & optimizes end-user services by inspecting, transforming, prioritizing & routing application traffic. Pulse vTM inspects & processes application traffic with full payload inspection & streaming. It applies a range of optimization techniques to ensure that incoming requests are presented in the most appropriate manner to the web & application servers. Responses from the application can be compressed, cached & returned to the client at optimum speed, freeing up resources on the server. Built-in TrafficScript language gives you full control over how individual requests are optimized, routed & transformed. Traffic management rules may also be created using Java™ Extensions. Pulse vTM includes a web-based admin interface to display powerful real-time analysis & history for all traffic across Traffic Manager clusters. Alternatively, you can integrate into remote management & event monitoring frameworks using SOAP APIs & SNMP. A Web Application Firewall module is available via other Pulse Secure AMIs. Only the 18.3 version (or later) can be deployed on the nitro instance types.
Highlights
- Speed: Accelerate services, increase capacity, and reduce costs by offloading performance-draining tasks such as SSL and compression onto Virtual Traffic Manager's optimized implementations.
- Reliability: Improve application availability by intelligently distributing traffic, avoiding failed or degraded servers, monitoring performance problems, and shaping traffic spikes. Provide HA via active-active deployment.
- Ease of management: Virtual Traffic Manager makes it easy to manage how users interact with applications and the infrastructure those applications depend on.
Details
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Financing for AWS Marketplace purchases
Pricing
Free trial
Dimension | Cost/hour |
|---|---|
c4.xlarge Recommended | $0.76 |
c5.4xlarge | $0.76 |
c4.4xlarge | $0.76 |
z1d.large | $0.76 |
x1e.8xlarge | $0.76 |
c5.2xlarge | $0.76 |
c4.2xlarge | $0.76 |
z1d.6xlarge | $0.76 |
c5.large | $0.76 |
c5.xlarge | $0.76 |
Vendor refund policy
Cancel hourly AMIs at any time - there is no long term commitment. Please contact AWS regarding annual subscriptions.
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
64-bit (x86) Amazon Machine Image (AMI)
Amazon Machine Image (AMI)
An AMI is a virtual image that provides the information required to launch an instance. Amazon EC2 (Elastic Compute Cloud) instances are virtual servers on which you can run your applications and workloads, offering varying combinations of CPU, memory, storage, and networking resources. You can launch as many instances from as many different AMIs as you need.
Version release notes
Release notes are published at https://help.ivanti.com/ps/help/en_US/VTM/22.x/ps-vtm-relnotes.pdf and in the web administration interface
Additional details
Usage instructions
In order to access the Pulse Secure Virtual Traffic Manager please enter https://<public dns>:9090 into your web browser. For instructions on using this product, please visit:
https://help.ivanti.com/ps/help/en_US/VTM/22.x/cloudgs/default.htm for the Cloud Services Installation and Getting Started Guide
Note: In order to locate the randomly generated password required during the initial setup process, please right-click the AMI in the AWS console, select 'Get System Log' and scroll to the bottom of the resulting System Log screen. You will find the password there. Upon connecting to the instance via https://<publicDNS>:9090 if you cannot get the password via the command line, please go to the EC2 dashboard for the instance and right click on the instance you are connecting to and slide over instance setting and click Get System Log. If you scroll to the bottom, the password will be there.
Support
Vendor support
Pulse Secure provides 24x7 technical support over telephone and email. Please click on the support link below for contact details. You can also take advantage of the Pulse Secure Community as an additional channel.
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.
Standard contract
Customer reviews
Strict security has protected virtual desktops and now blocks untrusted executables and files
What is our primary use case?
My main use case for Ivanti Virtual Application Delivery Controller (vADC) is for security. I have essentially secured all the Citrix Virtual Desktop environment by isolating each single process that was launched by all applications and desktops in order to deny the executable, the DLL, or every single file that could be used by a hacker inside a virtual desktop or a virtual app environment.
What is most valuable?
The best features that Ivanti Virtual Application Delivery Controller (vADC) offers are security. From my point of view, if you need really strict security, this could be a really good solution.
The strict security features of Ivanti Virtual Application Delivery Controller (vADC) stand out for me because essentially, you can have the hashing of all the programs that you can launch, the signature to check, the very deep analysis of the project, and the very deep log that helps you develop and analyze security. I treat the application as a firewall, and I block all and then begin to allow the passage for all the executables they need, especially for Java, since it's a big problem because when you enable Java, you can launch some Java programs that can destroy or scan your network. With Ivanti Virtual Application Delivery Controller (vADC), you can do this.
Ivanti Virtual Application Delivery Controller (vADC) has positively impacted my organization from the point of view of security. From the point of view of the usage of users, this is not a problem of Ivanti Virtual Application Delivery Controller (vADC). Sometimes, I get a lot of help desk returns because I don't know how users use the application. If you use, for example, an email and from the email you launch a Doc, the Doc will open Word and maybe the user needs also PowerPoint or other applications, and if you block, the problem is that you never know very well what users use. This is not the problem of Ivanti Virtual Application Delivery Controller (vADC), but the problem of the time of configuration in the project. Overall, you have to match security with usability of the application. If you block all the processes, this could be a little bit of a problem.
What needs improvement?
From my point of view, Ivanti Virtual Application Delivery Controller (vADC) could be improved with an agent, for example.
Something specific I would want to see in future versions of Ivanti Virtual Application Delivery Controller (vADC) is something that could automatically analyze the log and the sample of the usage of the user. Something that can analyze instead of a human being the behavior of the usage and then record the behavior or the usage, creating a template of the application. This is exactly what I do, for example, in some web application firewalls where I use a learning phase, and I track all user behavior to know how users can launch applications. I don't know if they have already done it, but at the time I used Ivanti Virtual Application Delivery Controller (vADC), there was not this feature.
For how long have I used the solution?
I have been using Ivanti Virtual Application Delivery Controller (vADC) for about two years and I was working in Axa in Milano.
What do I think about the stability of the solution?
Ivanti Virtual Application Delivery Controller (vADC) is stable.
What do I think about the scalability of the solution?
The scalability of Ivanti Virtual Application Delivery Controller (vADC) is positive because essentially it's an agent that you can put on each machine, and you can scale it. Then there is a backend to configure, but it's scalable.
How are customer service and support?
The customer support for Ivanti Virtual Application Delivery Controller (vADC) is good and responsive.
Which solution did I use previously and why did I switch?
The previous solution I used was to work with the group policy, registry keys on the machine, etc., but it's not consistent work because after that you have tons of keys on all the machines, and the policies applied don't apply. There might be changes, and you don't know where to find the security you had put on Active Directory, so it becomes a mess. In this case, with Ivanti Virtual Application Delivery Controller (vADC), with a single click, if something doesn't go, it's not a problem. You disable the block, leave the log phase, etc. In Active Directory, you have to wait about ten minutes for the propagation of the delivery controller, and you have a latency. When the production is blocked, you cannot wait a lot of time. You have to unlock the people as soon as possible.
Which other solutions did I evaluate?
Before choosing Ivanti Virtual Application Delivery Controller (vADC), I evaluated other options such as working also at the Citrix level to do all this work, but the problem is that the Citrix level is a layer on top of Windows. If you have some security problems in Windows, also with Citrix, you cannot reduce the surface of attack because you can publish one application and not all desktops. There was also a mechanism in Citrix called WEM that could do something similar, and there was also something based on Microsoft to avoid users launching some executables, but I found that the solution of Ivanti Virtual Application Delivery Controller (vADC) was, from my point of view, the best option.
What other advice do I have?
On a scale of one to ten, I would rate Ivanti Virtual Application Delivery Controller (vADC) an eight.
I chose eight out of ten for Ivanti Virtual Application Delivery Controller (vADC) because from the point of view of the configuration, it took so much time on the security side to configure. This is a thing that could be really improved.
The reason I chose eight out of ten for Ivanti Virtual Application Delivery Controller (vADC) is because of the problem of taking a lot of time to make a very deep configuration.
The advice I would give to others looking into using Ivanti Virtual Application Delivery Controller (vADC) is that if you begin a project, you have to have a person that is in charge of following the project all day, which means a technical person, at least one or two. A project manager is also essential because you cannot block all the applications. You have to make all the phases: the test, reproduction, pilot, and production, so you have to split the team into multiple governance and prepare a really good team. Otherwise, the problem is that you might not achieve success. You have to speak with the application person, with the users, with the support, with the manager, and others.
Patch automation has boosted compliance and saves hours in global server maintenance
What is our primary use case?
My main use case for Ivanti Virtual Application Delivery Controller (vADC) is to deliver patches in all our servers, and it is helpful for making our servers compliant.
I use Ivanti Virtual Application Delivery Controller (vADC) to get the updates from Microsoft and push them into the Ivanti software, and then through that Ivanti server, we deploy them in all the servers that have the Ivanti agent.
Currently, we are using Ivanti Virtual Application Delivery Controller (vADC) just for delivering patches and updating patches in all the servers in our environment.
What is most valuable?
The best features that Ivanti Virtual Application Delivery Controller (vADC) offers include its ability to help make us compliant at 95%, which is a big win if you are able to comply with 95% of devices, and it is also helpful for providing exact error codes, allowing us to troubleshoot accordingly.
The features of Ivanti Virtual Application Delivery Controller (vADC) impact my daily workflow by saving time and helping in troubleshooting as well.
Ivanti Virtual Application Delivery Controller (vADC) is very helpful, and I have nothing else to add about its features.
Ivanti Virtual Application Delivery Controller (vADC) has positively impacted my organization by allowing us to comply with all the servers with security patches, which include many bug fixes and do so in no time.
With Ivanti Virtual Application Delivery Controller (vADC), we are able to patch servers faster than we used to do via SCCM, and we save at least two to three hours in our global patching.
What needs improvement?
To improve Ivanti Virtual Application Delivery Controller (vADC), I would suggest integrating something to fix the registry of a server, as including any steps that fix the registry or any DLL files causing issues where patches did not install properly would be beneficial.
This is our current pain point with Ivanti Virtual Application Delivery Controller (vADC), and if that is fulfilled, it will be a great help.
For how long have I used the solution?
I have been using Ivanti Virtual Application Delivery Controller (vADC) for more than three years.
What do I think about the stability of the solution?
In my experience, Ivanti Virtual Application Delivery Controller (vADC) is stable.
What do I think about the scalability of the solution?
Regarding the scalability of Ivanti Virtual Application Delivery Controller (vADC), whenever we install the Ivanti agent in any server, it works smoothly, and we never struggle with scaling it as much as we want without any issues.
How are customer service and support?
I reached out to customer support for Ivanti Virtual Application Delivery Controller (vADC) recently when we were unable to get updates on our server, and they were very helpful, allowing us to resolve the issue.
Which solution did I use previously and why did I switch?
Before using Ivanti Virtual Application Delivery Controller (vADC), we used SCCM, which was very slow, and the output of the data did not match all the time, leading us to struggle a lot with that software.
Which other solutions did I evaluate?
I evaluated other options before choosing Ivanti Virtual Application Delivery Controller (vADC), including Tanium and BigPanda, but Ivanti stands out to me.
What other advice do I have?
My advice to others looking into using Ivanti Virtual Application Delivery Controller (vADC) is that you can trust it based on your needs, as it is very reliable, very fast, and allows you more time to work on other cases because Ivanti handles everything smoothly.
Ivanti Virtual Application Delivery Controller (vADC) is a very good tool that companies should use, and I have provided enough feedback on this product. I would rate this review a 9.