Amazon WorkSpaces is a desktop computing service that runs in the cloud, and now offers GPU configurations to support design and engineering applications and three-dimensional modeling. We show you how running these applications on Amazon WorkSpaces graphics bundles, in close proximity to data you already store on AWS, can help you process and visualize the results you need. We discuss the economics of running Amazon WorkSpaces graphics bundles, and demonstrate the experience of running a graphics-intensive application on a GPU-enabled Amazon WorkSpace. We also invite Autodesk (or TRC or ESRi) to discuss how they are using Amazon WorkSpaces graphics bundles in their business.

1. © 2016, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Salman Paracha – Product Manager – AWS
Prakash Kota, VP of IT, Autodesk
Joel St-Pierre - Event Systems & Support Manager, Autodesk
Jason Cradit, Sr. Director of Technology, TRC Companies
November 30, 2016
GPU Amazon WorkSpaces
Hardware-Accelerating Graphics Desktop
Workloads with Amazon WorkSpaces

2. What to Expect from the Session
1. Why GPU desktops in the AWS cloud?
2. Specs
3. Key benefits
4. The Autodesk University 2016 Story
5. Customer case study – TRC Solutions
6. Recap

3. Why GPU Desktops in the AWS Cloud?
Data security AgilityData proximity & enhanced
user productivity
Project based work

4. Graphics Bundle (CAD, CAM, CAE, Media)
1. Display: NVIDIA GPU, each with 1,536 CUDA cores and 4GB of video memory
2. Processors: 8 vCPUs - High Frequency Intel Xeon E5-2670 (Sandy Bridge) Processors
3. Memory:15 Gb of system memory
4. System Volume: 100GB root volume
5. User Volume: 100GB user volume

5. Key Benefits
Secure Pay-as-you-go Simple Consistent performance

6. The Autodesk vision is to help people
imagine, design, and create a better world.

7. 5.4M 200M
Professional
Users
Consumer Users
680M
Students and
educators with
access to free
Autodesk software

8. $2.5B 2.58M
FY16 Revenue Subscriptions
8,575
Employees
worldwide

10. Image courtesy of Tesla Motors, Inc. Image courtesy of Gensler.
The Martian © 2015 Twentieth Century Fox. All rights reserved.

11. Autodesk University Story
1. What is Autodesk University?
2. Challenges for AU16
3. Before AWS
4. AU16: 2 years in the making
5. After AWS
6. Software demo on Graphics Workspaces
7. Insights & learnings
How the Desktop PC and its Infrastructure disappeared at AU16

12. Autodesk University Story
What is Autodesk University?
“AU is a chance for designers, architects, and engineers to come
together and learn from the best in their industries, share practical tips
for getting the most from the software, compare notes, and rub elbows
with their peers.”

13. Autodesk University Story
What is Autodesk University?
“AU is a chance for designers, architects, and engineers to come
together and learn from the best in their industries, share practical tips
for getting the most from the software, compare notes, and rub elbows
with their peers.”

14. Autodesk University Story
AU16: Challenges
Setup from weeks to days Complexity of Setup

15. Autodesk University Story
Before AWS
1. 10 Physical Servers
2. Imaging using SCCM
3. Prep time 3 months
4. Push software for 7 days straight on-site
5. Troubleshooting hardware

16. Autodesk University Story
A Video Is Worth a Million Words http://autode.sk/hol2015

17. Autodesk University Story
Physics Problem: Cloud Doesn’t Happen Overnight!
AU14 AU15
AU16
7 Labs + 1 Certification Lab ~500 Units
Amazon Workspaces
1 Lab - 50 Units
EC2 g2.2xlarge
Teradici PCoIP
1 Labs of 100 Units
EC2 g2.2xlarge
Teradici PCoIP

18. Autodesk University Story
Cloud is the new normal: Move all AU workstations to Amazon WorkSpaces!
1. Autodesk is moving it’s software to the Cloud
2. Pioneering: AU in the Cloud
3. Multiple pilots
4. Low-risk profile
5. Scale and simplicity of WorkSpaces

19. Autodesk University Story
With AWS – AU Infrastructure = Single Laptop with access to AWS Console
10 Servers vs 1 Laptop to manage

20. Autodesk University Story
What about devices that connect to Amazon WorkSpaces?
PCoIP zero clients
Low cost devices that are hard to break and easy to fix
$5K vs $300

21. Autodesk University Story
Stats: Network bandwidth usage
• Average 185 Mb/s
overall
• Average 0.4 Mb/s
per workspace

22. Autodesk University Story
Insights & Learnings
1. Scalability
2. Simple to deploy and manage
3. Certification Lab: Consistent performance
4. Only moving forward from here

23. Customer Success Story: TRC

24. About TRC
A pioneer in groundbreaking scientific and engineering developments since 1969, TRC
is a national engineering, environmental consulting and construction management
firm that provides integrated services to four primary markets:
Energy | Environmental | Infrastructure | Oil and Gas
 Expert problem solvers
 120+ U.S. offices; London office
 4100+ employees
 NYSE: TRR
 www.trcsolutions.com

25. Typical TRC Project

26. Challenges

27. Elastic Market
• Drivers
• Supply/demand
• Geopolitical
• Regulatory
• Place your bets!

28. Business Challenges
• Software consistency
• Distributed skills
• Maximize exposure
• Availability
• Data accessibility
• Subcontractors
• Regions/OOO
• Customer

29. Journey

30. Alternate Solutions
Copying files
• Status-quo
• Working ad-hoc based on project requirements
• Data management nightmare

31. Alternate Solutions
Replication
• Localize all data everywhere
• Fixes accessibility, introduces unnecessary costs
• Little room for improved efficiency

32. Alternate Solutions
Virtual Desktop Infrastructure

33. Pilot Project
Collaboration Environment
• 3 Projects
• 25 Users
• 1 week

34. Outcomes

35. Results
Generating Alignment Sheets
• Cloud – 20 Minutes
• Local – 1.5 Hours
• 4.5x faster
Separating Layouts
• Cloud – 24 Minutes
• Local – 55 Minutes
• 2.3x faster
Attributed Block Updates
• Cloud– 1 Second
• Local – 15 Minutes
• 900x faster
Sketch Generation
• 4-6 Hours of preparation time
eliminated per deliverable

36. Cost Graph

37. Solution Benefits
• Performance
• Quality/Consistency
• Collaboration
• Alignment
• Elastic costs

38. Moving Forward
• Menu driven deployments
• Bundles
• Directory Integration
• No more Workstations
• RDS
• Hourly
• Remove VPN - add MFA
• Project Archive to S3/Glacier

39. Closing
• Elasticity for an elastic market
• Elasticity for elastic projects
• “Can’t imagine going back”
• Collaboration
• Still work to do

40. Thank you!

41. Remember to complete
your evaluations!