On most occasions, the round-trip-time (RTT) from the user desktop to his/her workspace is what matters the most. Latency Sensitiveīy far the biggest complaint with Workspaces will evidently be one not in your control - latency issues and lag. Workspaces land has some cons that you should be aware of before going all in. I'd recommend to at least allow the ability to restart / rebuild the Workspace for attempting self-repairs. Depending on how much freedom is warranted, you may even give permissions to change the type (performance) of the instance. Workspaces allow a decent set of self-service options.
AMAZON WORKSPACES WINDOWS
If your poison of choice is Windows, AWS also includes the Workspaces Application Manager ( WAM ) that enables you to push Windows applications to Workspaces.
However, do note that the base image is Amazon Linux 2 (which I find to be quite stable) and some users may prefer Ubuntu flavors. Custom ImagesĪs with other VDI solutions, you can create your own images (AMI equivalents) including your favorite development tools etc.
Because, like EC2 instances, your Workspaces are still isolated units, you can be reasonably confident that developers won't / cannot mess with other shared resources. While it is possible to do a lot these days without it, true-blue Linux developers always appreciate having the ability to run services as root - and this has helped folks learn more about Linux, systemd, docker etc. With a configuration switch, it is possible to enable root access for Workspaces users. here) and representative of the class of machines you select while setting up your workspace (Standard / Power / Performance etc.). Decent Performanceįor both Linux and Windows workspaces, I've found the performance to be good enough (not talking about network latency etc.
For example, I've added an extra group that allows developers to access webapps of each other on certain HTTP ports. You can also add extra security groups to your Workspaces. Not just that, you can choose to have workspaces in the same VPC that hosts your dev infrastructure - meaning workspaces can access other EC2 instances, your DNS, private Route53 hosted zones and all other infrastructure conveniently. That is, workspaces can live within your private VPC, and be exposed to the internet via usual NAT gateways. When you set up your workspaces infrastructure, you can host workspaces exactly as you would with EC2 instances. This is IMO the killer feature especially if you're already on AWS for the most part. Especially for the Windows world, although you have BYOL options, I'm sure you'd appreciate not having to worry about Windows licensing. Although there is a user directory underneath (via AWS Directory Service ), the quick setup offered sets up this directory automatically. All you need is an email address of the end user. The point-and-click (or API / CLI driven) interface to create a new workspace for users is dead simple.
AMAZON WORKSPACES HOW TO
I've included a section on how to get started with a free workspace for experiments towards the end of this article, but let's jump straight to the pros of Workspaces. Our primary use case was with Linux, though we've tried Windows based workspaces as well for certain use cases. Remote work is touted as one of the main benefits on the homepage, and I would agree.Īmazon offers both Linux and Windows workspaces. With all of us working from home, it made sense to try out Workspaces, as we were an AWS shop otherwise as well. Launched in 2014, this service was useful to us as we were looking for a replacement to traditional desktops as we were bootstrapping ourselves in the midst of the pandemic (early/mid 2020). Workspaces is the Amazon / AWS answer to Citrix, VMWare and other VDI solutions. I've used Workspaces as my primary desktop at work for over 1.5 years and you can consider this post as a long-term review / list of pros-cons. Welcome to my blog again, and this article will focus on the pros and cons of Amazon's DAAS platform: Amazon (AWS) Workspaces.
0 kommentar(er)
