Moving Enterprise Apps to AWS - VDI

This blog is specifically tailored for customers who have their applications or backend infrastructure residing in AWS, or are planning to migrate their business-critical workloads to AWS.

Migrating infrastructure and/or modernising applications to AWS is a very well-trodden path. If you’re exploring alternative hosting methods that could enhance the end-user experience and reduce operational overheads, then you’ve come to the right place. AWS offers plenty of publicly available advice and guidance with many built-in tools to help you move servers, data and applications. But what are the additional considerations, pitfalls and general guidance for moving enterprise-specific workloads such as VDI, Oracle and SAP? We’ve created this multi-part blog to explore advantages, considerations and pitfalls when migrating/modernising such enterprise apps.

Virtual Desktop Infrastructure (VDI)

Customers choose a VDI solution for many reasons, and moving these workloads to the cloud offers additional benefits. Some of the most common reasons to use VDI are listed below:

What VDI options are there in AWS?

One of the biggest advantages of adopting VDI in AWS is the choice of native cloud services such as AWS Workspaces, Amazon AppStream 2.0, or solutions from other vendors. Citrix offers Virtual Desktop and Application solutions, Citrix DaaS (Desktop as a Service), and Microsoft offers Remote Desktop Services (RDS).

Why migrate VDI to AWS?

As organisations expand or refine their digital transformation strategies, migrating VDI workloads to AWS can address numerous challenges. For instance, a company might be struggling with system performance due to outdated hardware. By migrating to AWS, they can leverage the latest cloud technology to improve speed and efficiency.

Another example could be a business facing compatibility issues with other applications. AWS supports a wide range of applications, making it easier to integrate systems and streamline operations. A company using a legacy CRM system might find it doesn’t integrate well with its current VDI solution. By moving to AWS, they can take advantage of AWS’ extensive integration options to ensure smooth interoperability.

Preparing for end-of-life hardware or software is another common challenge. For example, a company might be using a version of their current VDI solution that’s nearing its end-of-life. Rather than investing in new hardware and software, they could migrate to AWS and ensure they’re always using the most up-to-date versions.

Unlike standard business applications, VDI environments are integral to the virtual desktop infrastructure and application delivery, often requiring sophisticated integration with business processes across departments, including IT, HR, Finance, and Operations. For example, an HR department might use VDI to deliver a virtual desktop environment for remote workers. If the underlying VDI infrastructure isn’t performing well, it could impact HR’s ability to support remote workers. By migrating to AWS, the company can improve the performance and reliability of these critical HR services.

Advantages of migrating third-party VDI to AWS

· Scalability and flexibility: AWS provides scalable infrastructure that can dynamically adjust based on the demand. This is crucial for third-party VDI environments where load balancing and resource allocation can directly impact user experience. It scales in and out by adding/removing instances.

This scalability and flexibility is a key advantage of migrating third-party VDI to AWS, enhancing user experience through efficient resource allocation and load balancing.

· Cost efficiency: By leveraging AWS, organisations can move from a capital expenditure model to an operational expenditure model. This shift can result in significant cost savings, as resources are utilised more efficiently and can be scaled down when not in use.

· AWS organisations help manage costs and optimise resource usage across multiple AWS accounts. They allow for centralised management of all your AWS accounts, making it easier to track usage and costs.

· AWS organisations provide tools to organise and track cost and usage data, enhance control through access permission and cost monitoring, enable better planning through budgeting and forecasts, and further lower costs with resources and pricing optimisations.

· AWS Organisations support FinOps practices by providing shared access to cost data, allowing teams to collaborate in real-time and make informed decisions based on financial insights. This can be particularly useful when managing AWS WorkSpaces, as it allows for more granular control over costs.

· AWS Budgets is a service that lets you set custom budgets to track your costs and usage. Once you set this up, you can get alerts if your AWS costs or usage exceeds or is forecasted to exceed your budgeted amount. This can help you keep a close eye on your AWS WorkSpaces costs and ensure you're staying within your budget.

· Enhanced security: AWS offers robust security features that comply with industry standards, ensuring that data and applications are protected in a highly secure cloud environment.

· AWS offers robust security features like AWS Config and CIS conformance packs. AWS Config allows for continuous monitoring and assessment of your AWS environment, helping to ensure compliance with industry standards. CIS conformance packs are collections of AWS Config rules that can be easily deployed across an organisation for compliance posture management.

· Additionally, AWS Security Hub provides a comprehensive view of your security state across all AWS accounts, aggregating and prioritising security alerts from various AWS services and third-party products for holistic security monitoring. This helps identify and manage potential security issues effectively.

Key considerations when migrating VDI to AWS

· Application and data compatibility: before migrating, it’s important to ensure that all applications and data are compatible with AWS services. For example, you might need to update certain applications or modify data formats to ensure they work correctly in the AWS environment.

· Networking and connectivity: AWS provides various connectivity options like AWS Direct Connect and VPNs to ensure reliable and secure connections between on-premises environments and the cloud. For instance, you might set up a VPN to securely connect your on-premises network to your AWS VPC, or use AWS Direct Connect for a dedicated network connection from your premises to AWS.

· Licensing and compliance: when moving VDI to the cloud, it’s crucial to understand the licensing implications. AWS supports bring-your-own-license (BYOL) models, but you’ll need to review your VDI and third-party software agreements to ensure compliance. For example, some software licenses may not allow for cloud-based usage, so you’ll need to check this before migrating.

Pitfalls to avoid

· Underestimating complexity: VDI environments are complex, and migrations can involve unexpected challenges. For instance, a company might underestimate the time and resources needed to migrate their applications and data to AWS. This could lead to delays and increased costs. Comprehensive pre-migration testing is essential to identify potential issues and ensure a smooth transition.

· Neglecting user experience: the impact on the end user should always be considered. For example, if a company migrates their VDI environment to AWS without carefully planning for network connectivity, users might experience performance issues post-migration. This could lead to dissatisfaction among users. It’s vital to maintain or improve the user experience during and after the transition.

· Improper cost management: while AWS can be cost-effective, mismanagement of resources can lead to higher costs. For example, a company might leave unused EC2 instances running, which could lead to unnecessary costs. Effective management tools and practices, such as setting up alerts for high usage or using AWS Budgets to track costs, are necessary to monitor and control spending.

Considering AWS WorkSpaces as an alternative to VDI

For organisations contemplating a migration to AWS, AWS WorkSpaces presents a compelling alternative, offering a managed, secure Desktop-as-a-Service (DaaS) solution. This is especially true if your client and server workloads are hosted in AWS. AWS WorkSpaces enables businesses to provision virtual, cloud-based Microsoft Windows or Amazon Linux desktops for their users, providing access to the documents, applications, and resources they need with the benefit of a pay-as-you-go pricing model.

The pay-as-you-go model is a pricing strategy that allows businesses to pay only for the actual usage of a service. Instead of purchasing a fixed amount of resources upfront, costs are incurred based on the actual consumption of resources. This model provides flexibility and scalability, as businesses can adjust their usage based on their needs and only pay for what they use.

For example, let’s consider a company using AWS WorkSpaces. In a traditional IT setup, the company might need to estimate the maximum number of desktops they’ll need for the year and purchase hardware and software licenses accordingly. This could lead to over-provisioning and unnecessary costs if the actual usage is less than the estimate.

This can be particularly advantageous for companies looking to streamline operations and reduce the overhead associated with maintaining physical desktop infrastructure, on-premises and complex deployments.

AWS WorkSpaces integrates with a variety of AWS services, each providing unique benefits. Here are a few examples:

· AWS Identity and Access Management (IAM) and Amazon S3: these services work together with WorkSpaces to manage access and storage, respectively.

· Amazon RDS: this service provides database services, which can be crucial for applications running on WorkSpaces.

· AWS Lambda: this serverless computing service can be used to run your code without provisioning or managing servers.

· AWS Directory Service: WorkSpaces is tightly integrated with AWS Directory Service, allowing Active Directory users, groups, and permissions to easily manage access.

· Amazon Virtual Private Network (VPC): WorkSpaces is distributed within an Amazon VPC, providing users with access to persistent, encrypted storage volumes via the AWS Cloud.

· Amazon CloudWatch: CloudWatch is used for logging and monitoring. It keeps track of operational data, provides insights for optimisation, and initiates automated actions for troubleshooting when pre-configured alarms are detected. For example, with CloudWatch, organisations can retrieve, monitor, and analyse WorkSpaces data and insights. This information can be used to uncover ways to improve AWS app and system performance and resource utilisation.

These integrations allow businesses to create a customised and comprehensive IT infrastructure in the AWS cloud, tailored to their specific needs and requirements.

Transitioning to WorkSpaces from third-party VDI can lead to potentially lower costs and improved end-user experiences, especially for remote and distributed workforces. Be aware that WorkSpaces does not offer the same level of IT management functionality as the popular VDI platforms on the market today, such as Citrix, Omnissa and others. This is especially true for automation of common tasks, such as app and image management, so this needs to be considered before making the jump to WorkSpaces and removing them from the picture.

To help plug this IT management gap, AWS WorkSpaces can be deployed with Liquit (part of Recast Software), which provides app management, deployment and automation capabilities to enhance what AWS natively provides in this space.

Conclusion

Migrating VDI to AWS can transform the virtual desktop experience for enterprises, making it more scalable, secure, and cost-effective. This offers great benefits to end-users if your applications and the services that power them are deployed in AWS. However, it requires careful planning and execution. Enterprises considering this move should start with a detailed assessment of their current VDI environment and seek advice from experts to ensure a smooth transition.

For more insights on migrating your VDI workloads to AWS or to speak with our team, contact us at aws@softcat.com.