I have used AWS Workspace and its really good as a VDI tool but don’t expect it to be a cost-effective solution. AWS workspace prevents your organization's data from being compromised.It also provides greater security and easier management which may be difficult for you to handle yourself.It’s a great solution if you need to move consistently. With AWS workspace, the same machine from anywhere.My point is that VDI is not the only solution to use computers temporarily as it has many other advantages.įor example, If you use an AWS workspace, you get the following benefits too. There is no doubt that you need to use VDI solution considering you only use developers temporarily but don’t expect it to be very cost-effective. As a matter of fact the guy who opened the bridge and declared this a crisis, he owns them. I don't own any of those facilities or circuits. We no longer have to be woken up at 3am to join a crisis bridge to try to explain that a circuit outage between Hyderabad and the Philippines that is causing high network latency is not a problem that I can fix. Getting this cancerous monkey off our back was a well & truly welcomed operational change. While I applaud all the new security enhancements and magic & wonder of the new automations. We made them understand, and our business understand that the external developers were exclusively on the hook for maintaining their own connectivity to Amazon, and we were not going to help them do it. We promise the developers guaranteed performance from Amazon to our Data Centers. The adoption of this architecture forced my business to embrace the concept of contracted responsibility of connectivity. But it has caused me a very great deal of frustration over the past decade or two.Īnd I'll admit I am carrying around a sack of resentment and lingering bitterness about it. The experience is not so much dreadful as it is frustrating. This is much simpler for them, and blissfully removes our team from being asked to troubleshoot & diagnose their network connectivity. Now, all they need to do is route their users out to the internet to hit the WorkSpaces entry point. This new architecture relieves them of the responsibility to try to maintain a simple IPSec or MPLS connection from their network to ours. They are generally quite rather awful at managing their own network connectivity. They are generally quite good at writing code. We have several external software development organizations under contract. The amount of CYA and "your problem" make your workplace seem beyond dreadful from that description. Leverage as many Amazon-provided resources as you can. If you do this right, you'll end up with far more control & security over these systems then ever before.ĭon't try to make a traditional desktop image that you squirt onto new virtual systems.įocus on automations to install or slipstream your business applications onto an automatically-created OS. Once you build out your automatons, you can spin up 100 virtual systems in an hour, and possibly less.įocus on the security & controllership benefits. You probably won't save money with the migration or adoption.įocus on the speed of response/spin-up. Meet your contracted obligations or prepare for work-performance-penalties.ĭO NOT approach AWS WorkSpaces as a cost saving exercise.
0 Comments
Leave a Reply. |