Getting Started with Amazon WorkDocs

Aug 16, 2023

Getting Started with Amazon WorkDocs

Amazon WorkDocs is a fully managed, secure content creation, storage, and collaboration service. With Amazon WorkDocs, you can easily create, edit, and share content, and because it’s stored centrally on AWS, access it from anywhere on any device. In this session, learn how to set up a WorkDocs environment and enable users and third parties to securely collaborate.

Learn more about WorkDocs at http://amzn.to/3bUVuPm

Subscribe:
More AWS videos http://bit.ly/2O3zS75
More AWS events videos http://bit.ly/316g9t4

#AWS #AWSWebinar

Content

4.838 -> Welcome! My name is Andrew,

6.715 -> I'm a EUC Specialist Solutions Architect at AWS

10.51 -> and today we're going to walk through,

12.512 -> talk through what Amazon WorkDocs is,

15.557 -> how it can help you as a solution

17.726 -> and ultimately why use Amazon WorkDocs in your environment.

23.857 -> So impressed will you be with Amazon WorkDocs

26.109 -> and how it can be used to help your users,

28.903 -> help your customers collaborate, store documents securely,

32.657 -> that you're going to be bound to want to understand

35.952 -> how to deploy Amazon WorkDocs.

38.079 -> So we'll talk through how you can get started,

40.957 -> we'll give a demo of making use of Amazon WorkDocs

44.21 -> and then leave with getting started tips and tricks

47.422 -> so that you can bring Amazon WorkDocs into your environment.

52.469 -> We see a number of different business drivers for companies,

54.971 -> such as yours, seeking to migrate to the cloud.

58.266 -> The cloud use case, years ago,

61.352 -> was primarily driven by savings leveraging cloud technologies.

65.482 -> We see a lot of data center consolidation projects,

68.026 -> especially in companies that have been active in acquisitions

71.112 -> or experienced infrastructure sprawl over the years.

74.157 -> Any cost-conscious organizations

76.201 -> are looking for ways to improve the bottom line

78.328 -> by reducing their technical debt.

80.705 -> Moving from CapEx to OPEX, and taking advantage

83.541 -> of the elasticity of compute in the cloud

86.294 -> and a more DevOps approach with automation.

89.38 -> Increasing business agility is now driving the move to the cloud.

93.76 -> Some of our customers are creating business cases

96.513 -> where they believe their workforce can be 30 to 70% more productive

100.6 -> and deliver features, deliver content,

103.228 -> deliver services much faster,

105.063 -> as a result of migrating their skills,

106.981 -> and applications to the cloud.

108.858 -> We are increasingly seeing companies

110.693 -> looking to completely reimagine their business,

113.196 -> using modern technology

114.781 -> as part of a larger digital transformation project

117.826 -> and innovation.

119.953 -> And while there are a lot of reasons enterprises are motivated

122.872 -> to migrate legacy systems to the cloud,

125.041 -> often times comprising tens of thousands of servers,

128.586 -> or dozens of data centers, or petabytes of data,

132.549 -> they're asking a lot of questions about how they can do it quickly.

137.178 -> So is Amazon WorkDocs handy? Where does that fit in?

139.681 -> Amazon WorkDocs is a secure, easy to use, cloud storage service

143.059 -> that lets you store content, files, documents

145.979 -> across teams and collaborate on projects.

149.44 -> WorkDocs is a secure content store

151.734 -> where you own and control your files.

154.821 -> You can specify which AWS region stores user files

159.159 -> to help maintain data locality.

161.828 -> WorkDocs runs on one of the world's largest cloud infrastructures,

165.54 -> built to satisfy

166.833 -> the requirements of our most security-sensitive customers.

170.044 -> WorkDocs is HIPAA eligible,

172.422 -> PCI eligible, meets ISO compliance requirements.

175.592 -> And in addition, files on WorkDocs are encrypted in transit and at rest.

181.514 -> You can manage access to your existing IT resources

184.267 -> such as Active Directory

185.852 -> to take advantage of security groups,

188.104 -> single sign on, multi-factor authentication

190.44 -> and track user and file activity in near real time.

195.153 -> Users can use the WorkDocs web client,

198.072 -> mobile applications, WorkDocs Drive or indeed

200.617 -> third-party apps that are compliant to manage the files.

204.913 -> And WorkDocs integrates easily with WorkSpaces and AppStream,

208.291 -> so your content is available from any environment,

210.835 -> any device, anywhere.

212.754 -> And WorkDocs also comes

213.963 -> with an extensive software development

216.007 -> that helps you customize your collaboration

218.176 -> and management capabilities

219.552 -> into your solutions, into your applications.

222.639 -> Using admin API actions,

224.807 -> you can integrate WorkDocs with your existing solutions,

227.518 -> such as auditing, eDiscovery, maybe even data loss prevention.

232.649 -> Using user API actions can allow you to build third-party apps

236.527 -> so you can programmatically manage files,

238.821 -> comments, notifications, sharing.

241.491 -> The WorkDocs SDK is part

243.159 -> of the AWS SDK software development kit

245.912 -> and integrates with other AWS services,

248.122 -> so you can easily take advantage of the power of AWS for security,

252.502 -> for monitoring, business logic,

254.254 -> analytics, storage, artificial intelligence,

256.714 -> app development and at some point in time,

258.8 -> possibly even making the tea.

260.677 -> You can get started in minutes

262.553 -> with the same AWS tools you are already familiar with.

266.015 -> Amazon WorkDocs customers frequently tell us

268.184 -> that they actively use Amazon WorkDocs

270.645 -> for a range of use cases.

273.564 -> Our customers want to discover cost savings,

276.734 -> they want to have better resource efficiency

279.195 -> and increase their operational resilience

281.281 -> and improved business agility.

283.866 -> With WorkDocs you've a secure, fully managed file system.

289.664 -> WorkDocs customers frequently tell us they actively use Amazon WorkDocs

293.001 -> for the reasons that you can see on the screen.

298.047 -> Our customers want to discover cost savings,

300.383 -> have better resource efficiency

302.218 -> and increase their operational resilience,

304.47 -> improved business agility.

306.347 -> With WorkDocs, you have a secure,

308.057 -> Fully-managed file storage, with an extensible SDK service.

311.853 -> Key for many of our customers

313.229 -> is to move for a more efficient, agile way

315.273 -> to share data within an organization

317.9 -> and from an organization to customers, to partners,

320.987 -> by moving from a legacy network file stores to cloud-based,

325.158 -> searchable, securely accessible servers.

327.66 -> With the WorkDocs client drive for Windows and Mac users,

331.289 -> cloud-based files are viewable in action

332.999 -> as part of their Explorer or Finder view.

336.21 -> The WorkDocs Drive retrieves files from the cloud on-demand,

339.672 -> reducing the storage required on our end device

342.133 -> and automatically syncing saved files from that end-device to the cloud.

346.596 -> So keeping documents secure and accessible,

348.973 -> this reduces the impact of laptop users

352.018 -> who forget to copy that important doc before they leave the laptop at home.

356.314 -> They can create and edit files in Drive,

358.816 -> lock files to prevent overwrite,

361.611 -> changes are automatically saved to the cloud.

364.572 -> This allows for an almost unchanged desktop experience

366.949 -> either in Windows file Explorer or Mac Finder.

369.702 -> User home drives, team drives

371.954 -> replace traditional network and shared drives.

375.583 -> This enables more mobile working

379.67 -> by allowing access to files when needed,

381.714 -> without having to download the files.

383.174 -> Save the files on local storage.

384.884 -> Right click on files,

386.135 -> before you leave for the office, before you leave home.

388.137 -> You can now share files with co-workers and teams

390.348 -> using your Active Directory credentials,

392.225 -> their Active Directory credentials.

393.351 -> Collaboration's improved not just by allowing ready access

397.897 -> to the source files

399.065 -> but allowing it to interact with that source file

401.234 -> like document in real time.

403.152 -> You can edit the document together with your team, using Hancom,

406.197 -> or you can provide comments and feedback

408.199 -> on your teammates' documents

409.659 -> or have them provide feedback on yours.

411.786 -> User centric SDKs, admin SDKs

414.497 -> are available as part of the AWS SDK.

417.708 -> You can add WorkDocs features to web or mobile applications,

421.379 -> integrating your business tools

424.382 -> with WorkDocs or enhance WorkDocs capability

427.218 -> with your applications, with your business processes.

429.929 -> Admin controls.

432.432 -> Now, admin controls allow your administrators

436.394 -> the policy and configuration of the WorkDocs environment.

439.313 -> So there's user controls.

441.065 -> User controls and sharing site controls

443.192 -> are available in the WorkDocs admin console,

445.278 -> which we'll see in the upcoming demo.

447.321 -> The WorkDocs admin console

448.489 -> is separate from your AWS admin console.

451.742 -> Once a WorkDocs site has been created

454.245 -> and associated with your Active Directory,

455.955 -> you can assign admins

457.457 -> and they can control the environment for WorkDocs,

460.46 -> using the WorkDocs admin console.

462.837 -> We'll talk about real-time site-wide activity,

466.09 -> with real time auditing.

467.884 -> You can also have diagnostic logging

470.178 -> for client components at WorkDocs Drives,

472.096 -> and WorkDocs Companion.

473.848 -> If you want to dive deeper

474.849 -> to understand AWS compliance controls,

477.226 -> there are a number of compliance white papers

479.02 -> on the AWS compliance website.

481.147 -> If you need NDA agreements or business associated addendums,

484.692 -> these are available through AWS Artifact.

488.196 -> Security is key. You want to maintain a flexible, scalable user experience,

492.825 -> but what assurance to organizations do you have

496.037 -> that your data is secure in the cloud?

498.789 -> Now, WorkDocs relies on Active Directory integration.

502.043 -> That AD could be a manufactured directory

504.045 -> that you've created in AWS for your cloud users.

507.798 -> You can reference your own Active Directory,

510.301 -> using your Active Directory connector.

512.136 -> That could be on your existing on-prem environment via VPN,

515.64 -> or you could have extended your AD into AWS

519.143 -> to allow direct access from the AWS environment.

522.73 -> For users authenticating remotely,

524.273 -> you can enable multi-factor authentication

526.943 -> using Radius to add an additional layer of user security.

531.364 -> WorkDocs docs are encrypted at rest

534.033 -> and when they're transferred to and from the end device.

537.286 -> So that could be a Windows device, could be Mac, Android, iOS,

541.082 -> or a device running a supported browser.

544.252 -> The WorkDocs service is HIPAA eligible,

546.837 -> PCI DSS compliant.

549.84 -> We talked about cloud migration

551.842 -> being driven by operational resilience.

553.97 -> So the AWS global infrastructure is built around AWS regions

557.098 -> and availability zones.

558.558 -> AWS regions provide multiple physically-separated

561.936 -> and isolated availability zones, which are connected with low latency,

565.898 -> high throughput and highly redundant networking.

569.026 -> With availability zones you can design and operate

571.404 -> applications and databases

573.155 -> that automatically fail over between availability zones

575.658 -> without interruption.

577.326 -> Availability zones are more highly available,

579.745 -> fault tolerant and scalable

581.831 -> than traditional single or multiple data center infrastructures.

585.459 -> With WorkDocs you've six regions that you can select from

588.337 -> to help match the data residency requirements

591.507 -> that you might have.

592.717 -> These are North Virginia, Oregon, Singapore,

595.678 -> Sydney, Tokyo and Ireland.

598.264 -> To answer that resiliency, you've got auditing and reporting

601.225 -> and unlimited versions of files.

603.352 -> When files are deleted, you control the retention policy,

606.022 -> which has a default of 60, but can go up to 365 days.

610.526 -> You're in control of how users share the documents.

613.279 -> You can control from which IP location users

615.74 -> can connect from.

616.699 -> You can control how users join the site,

619.577 -> how to allow external accesses to be able to join as guests,

623.08 -> or as full active users that can also save files.

626.751 -> Do you allow users to do that automatically,

629.754 -> or you must force it through for a request?

631.881 -> You're in control.

633.716 -> Users can view their own WorkDocs activity feed

636.302 -> to keep track of changes of their files and folders

638.721 -> and just see who made changes.

640.222 -> See what files have you downloaded, commented on,

642.975 -> shared, locked, deleted.

644.769 -> They can search for specific files, folders, or users.

648.272 -> Activity feed searches can be filtered by activity type

651.317 -> and date modified.

652.902 -> Within WorkDocs, WorkDocs admins

654.779 -> have near real-time feed on all of the activity within the site.

658.658 -> Retention for those feeds is up to 90 days.

661.786 -> Admins can view and export the activity feed

664.205 -> for an entire site.

665.164 -> To use this feature, you must first install the WorkDocs Companion.

670.753 -> You create search parameter folders that you need, maybe activity type,

674.757 -> maybe date and then you export that to either a JSON or a CSV file.

679.178 -> Users who aren't administrators can view and explore

681.389 -> the activity feed for their content only.

684.6 -> Amazon WorkDocs is integrated with AWS CloudTrail,

687.978 -> a service that provides a record of actions taken by a user,

690.731 -> role, or an AWS service in Amazon WorkDocs.

693.693 -> CloudTrail captures all the API calls for Amazon WorkDocs as events,

698.239 -> including calls from the WorkDocs console

700.449 -> and from code calls from the APIs.

702.868 -> If you create a trail, you can enable

705.329 -> continuous delivery of CloudTrail events

708.708 -> to an Amazon S3 bucket, including events for Amazon WorkDocs.

712.253 -> If you don't configure a trail,

713.462 -> you can still view the most recent events

715.464 -> in the CloudTrail console in event history.

718.676 -> Using the information collected by CloudTrail,

721.053 -> you can determine the request that was made to Amazon WorkDocs,

723.597 -> the IP that request was made from,

727.393 -> who made the request, when it was made

729.103 -> and additional details.

730.771 -> Simply sign in using the AWS console for CloudTrail.

736.61 -> So that all sounds super lovely, Andrew, can we see it in operation?

740.781 -> Can we see it working? By all means.

743.993 -> Here's my demo environment that we're going to work through, talk through.

748.789 -> Very similar to how many of the customers

751 -> that I've worked with

752.877 -> want to test and validate WorkDocs.

755.087 -> They want to connect to their existing Active Directory

758.007 -> or have their Active Directory accessible

759.842 -> so they can use their existing user IDs.

762.303 -> So we've extended Active Directory from our corporate data center

766.682 -> into AWS cloud. In our case it's via VPN.

770.728 -> We've created an Active Directory connector,

772.813 -> connecting Active Directory server resources in my data center

778.194 -> and exposing them to my virtual private cloud

781.864 -> within Ireland, as my region

784.617 -> and now I'm going to build out my WorkDocs environment

789.038 -> so that we can test and understand

791.373 -> how it is used by users and by administrators.

796.754 -> Cool, so we've seen how customers are using WorkDocs,

800.633 -> we've seen why customers use WorkDocs,

802.927 -> let's look at what's going on

804.47 -> in terms of building our WorkDocs environments.

807.097 -> I've signed on to my console,

808.933 -> I'm now going to create my WorkDocs environment

811.519 -> for my test users to test and have a look at.

814.647 -> I've already created my Active Directory connector;

817.65 -> I've already created a directory service

820.528 -> that's referencing back to my Active Directory

823.239 -> within my own environment.

825.241 -> I could have created an Active Directory within AWS.

828.494 -> I'm going to sign on as an administrator.

830.871 -> I signed in the first time, so I'll put it in quiet to let us.

834.542 -> So now create a user and I've created a WorkDocs site.

837.419 -> Let's go out of the AWS console

839.463 -> and into the admin console for WorkDocs.

842.758 -> That's making use of the site URL you can see on the screen.

846.22 -> So I'm signed on to my WorkDocs console,

848.681 -> this is the standard user console

850.349 -> that users would manage their documents.

852.309 -> But I'm an administrator,

853.769 -> so I'm going to go to the right hand side, and open up

855.813 -> that admin control panel,

857.606 -> because I've been assigned as an administrator.

859.65 -> And here is where I administrate my WorkDocs site.

863.445 -> Here's where I've got different configuration settings

865.656 -> that we talked about in our admin controls.

868.117 -> Here's where I can see the users

869.702 -> that are associated with my Active Directory.

872.496 -> I've got a range of options that I can make use of.

875.875 -> The key thing that I'm going to start off first

877.877 -> is the Hancom online editing.

880.296 -> This allows users to interact in real time

883.007 -> with the documents that they're working on.

885.801 -> I've got other options that I can modify,

888.554 -> that I can make use of.

890.055 -> I could determine how much storage is available

893.267 -> for each user in terms of maxim,

894.727 -> I can also set IP control lists

897.021 -> to determine where users are connecting from.

899.857 -> Maybe I only want to access from a particular site.

903.319 -> I can then modify how policy settings are made.

906.822 -> How are users managed within my environment?

909.658 -> Can I share publicly, or can I not share publicly?

912.578 -> Is it all users who are added to my Active Directory

915.748 -> will become WorkDocs users or not?

918.876 -> I can configure all of these in policy settings

921.587 -> and allow autonomy of users or allow more control,

925.799 -> depending on my organization's wants and security needs.

930.346 -> So here I'm only going to allow power users

934.183 -> 336 00:15:36,061 --> 00:15:40,065 rather than every user being able to do that service and capability.

941.106 -> Cool, so I've set my policy settings,

944.568 -> now I'm going to enable Office online.

950.074 -> Currently not enabled for the site by default,

951.742 -> so let's check that out, make sure that that's all configured.

956.58 -> Now, I've already got some users

958.624 -> within my Active Directory environment, these are available.

961.126 -> They're not users within WorkDocs yet,

963.545 -> the default was not to enable users.

965.047 -> You saw in the policy settings that I can enable users if need be,

968.217 -> so that when new users are created,

969.802 -> they're automatically created as WorkDocs users.

972.972 -> Here what I'm going to do is set up my individual users as active users.

977.434 -> Set them up as power users or set them up as users,

980.646 -> as appropriate for their role,

982.69 -> and then I'm going to set a limit size

986.276 -> on the amount of storage that the users can consume

988.07 -> within the WorkDocs environment.

988.278 -> I'm going to set it to be at 50 gig for each one of my users.

994.201 -> Here I'm using the console and obviously, with the APIs and SDKs

997.83 -> I could script this, could enable users automatically

1002.501 -> using the script, or particular users within the Active Directory group.

1007.214 -> I've also got two system users.

1009.883 -> System users are going to be used in this demo environment

1013.012 -> to create collaboration team folders.

1016.223 -> Going to log on as those users, those users own those folders,

1020.06 -> and allow the pre-configuration of that environment

1022.896 -> prior to users logging on.

1024.94 -> I'm going to make use of Active Directory groups,

1027.818 -> so that users will be members

1029.486 -> of either Project Mouse or Project Cat

1032.364 -> and will work on documents associated with that project.

1035.451 -> By having a service user, I can pre-configure that environment,

1038.287 -> pre-configure that share,

1039.663 -> pre-configure the permissions so that when users log on

1042.124 -> they've got access to the resources that they need.

1044.418 -> We could allow users to share their own team folders.

1047.379 -> Here we're trying to save them time and effort,

1049.506 -> give them a faster time to value.

1052.384 -> So here, I'll log on to the WorkDocs environment

1055.095 -> as one of my service users

1056.722 -> because I'm going to set up that initial team folder

1059.349 -> for my Project Cat, Project Mouse security groups.

1064.855 -> Put in the super secure password.

1067.691 -> There's no MFA, Andrew!.

1068.776 -> There isn't any MFA in this demo,

1070.611 -> but yes, you can enable multi-factor authentication

1073.405 -> for your remote users

1074.698 -> in a live environment, should that be required.

1077.701 -> The user signing on, the system user's signing on the site

1079.703 -> and they've got the initial experience

1082.498 -> and the welcome to WorkDocs.

1083.916 -> I leave that as a fun and exciting exercise.

1086.418 -> So the user's in their WorkDocs web client environment, using a browser.

1090.422 -> That browser might be Safari, it might be IE,

1092.883 -> it might be Firefox, it might be Chrome.

1095.803 -> Now, let's create a folder.

1097.971 -> Now that will appear in my Docs for this particular user,

1101.683 -> for this service user,

1103.102 -> but this folder will be then shared with other users

1106.814 -> and it'll appear in their shared folders.

1109.566 -> Let's give this a name, this is going to be the Project Cats folder,

1114.071 -> for all of the Project Cats team,

1116.448 -> for all of the Project Cats documents.

1118.659 -> So I've created that folder and now let's share it with other people.

1123.872 -> You can see that the service account user,

1125.541 -> Project Cats, is the only user for that folder at the moment.

1128.502 -> Let's invite some other people.

1129.545 -> Now, WorkDocs has been integrated with my Active Directory,

1133.757 -> so I've got access to the users who are in my Active Directory.

1137.511 -> I could type in all of the individual usernames

1140.18 -> that are associated with this folder and it will be recognized

1142.933 -> because it's associated with my Active Directory.

1145.686 -> That's complicated and difficult to do at scale.

1149.69 -> Far simpler to make use of Active Directory group

1152.359 -> that I know my Project Cat users, in this particular instance,

1155.195 -> those Project Cat users are associated with it.

1157.197 -> So let's give contributor access to that group,

1161.243 -> obviously with different access levels.

1163.704 -> Here's contributor, so they can read and write through that directory,

1167.04 -> but I might have Project Mouse,

1168.709 -> for example, having viewer-only rights.

1172.88 -> Now, we set that up as a service account.

1176.341 -> I'm all good to go. I've got my service account,

1178.594 -> I've got my environment set up correctly,

1180.637 -> let's look at what this would look like

1182.014 -> from two individual users' point of view.

1184.933 -> Here I've got John and I've got Shirley.

1187.936 -> Now I look again, John and Shirley are working together.

1190.23 -> Shirley's a contractor, she's working from home.

1192.357 -> Yes, alright, in my example I've got two WorkSpaces providing this,

1195.36 -> but let's use our imagination.

1197.571 -> John's working in the office, Shirley's working from home.

1199.99 -> Shirley's a contractor and needs access

1201.909 -> to the files for Project Mouse in this particular instance.

1206.079 -> John very unhelpfully has those files,

1208.373 -> those important files that need to be shared

1209.917 -> and distributed amongst the group on his desktop.

1212.669 -> Not particularly useful in terms of collaboration

1215.881 -> and data access for remote users. Shirley's working from home.

1219.301 -> So because John is a member of the group Project Mouse,

1223.889 -> he has access to that shared team folder

1226.058 -> that's been set up as we did with Project Cat

1228.685 -> and he's moved those files from his desktop

1231.396 -> into his team folder.

1234.107 -> He's using the WorkDocs Drive client.

1236.068 -> It's been integrated into his Windows Explorer view,

1239.529 -> so it's just as if he was cutting and pasting

1241.198 -> into a folder in his directory,

1243.2 -> but those files have been uploaded in the background

1244.201 -> to the WorkDocs site and are now available

1249.665 -> to other members of that project group,

1252.251 -> who are maybe using their own WorkDocs client,

1254.461 -> or as Shirley's doing, making use of the web client

1258.006 -> to access those documents securely.

1261.176 -> We've talked about they're secured in the WorkDocs environment at rest,

1265.18 -> they're encrypted and secured to the end device

1267.975 -> using network file encryption.

1270.56 -> And what Shirley's going to do now,

1272.729 -> is interact, maybe she's on a chain call,

1275.065 -> maybe she's on a Zoom call

1276.692 -> with John and they're going to work collaboratively together

1279.736 -> on a document in WorkDocs.

1281.446 -> So Shirley has opened up

1284.116 -> the Mouse document in her browser

1286.91 -> using the Hancom editing tool.

1290.205 -> John's going to do the same.

1291.373 -> He has opened up the file from his Explorer,

1293.834 -> right-clicked on that, opened up the document in his web console

1297.17 -> and is now going to edit that document

1299.798 -> using the Hancom editing tool.

1301.675 -> So working on a great literary work here,

1304.428 -> and there's a discussion about the content of that work.

1308.265 -> John thinks there needs to be some changes and he wants

1309.975 -> to talk Shirley through the changes that he's advising to be made.

1313.562 -> Shirley as the contractor has access to this environment,

1315.689 -> using the web console accessed securely,

1318.275 -> using the WorkDocs environment.

1320.027 -> So John moves the piece

1321.903 -> where he thinks that change needs to be made.

1325.991 -> You may notice

1327.409 -> that Shirley's initials are appearing in the document, because Shirley's

1330.287 -> actively working on it, and from Shirley's point of view

1332.456 -> John's initials are appearing in the document

1334.499 -> because he's working on it.

1335.834 -> I believe John isn't convinced that the poem was written in 1785

1339.921 -> and wants to make a particular correction.

1341.673 -> As you can see, John's working on the document

1343.633 -> and that remote contractor or maybe that homeworker,

1346.72 -> in Shirley's case, can see the changes

1348.513 -> that John's making in real time.

1350.557 -> Shirley knows better and has changed it back.

1352.893 -> Well done, Shirley.

1355.062 -> So we can come out of the document.

1356.438 -> We've made our changes,

1358.815 -> we've agreed on the changes that can be made.

1360.901 -> We can save that as a new version of the document.

1364.821 -> That's not the only way that you can interact.

1366.656 -> We've talked about, yes, doing online editing,

1368.992 -> but has the capability and facility to make use of feedback tools

1373.83 -> within the WorkDocs environment.

1375.29 -> Here's Shirley looking at the activity on that file.

1379.002 -> Here, because Shirley is an individual user,

1380.754 -> she gets to see her pieces

1383.006 -> and who's been working on the documents as well.

1386.76 -> Now Shirley's concerned that maybe other people

1388.595 -> make the same mistake that John's done,

1390.43 -> so she's going to provide feedback into the document

1392.933 -> for others to be able to view and potentially comment on as well.

1403.402 -> And when she's finished doing all of it,

1404.945 -> all of the comments published as those,

1406.822 -> so that the rest of the team members can see the comments

1410.242 -> and feedback that Shirley has made.

1412.786 -> Now, if John refreshes his document,

1416.123 -> now that the document's been saved,

1417.332 -> so we're now looking at version two of the document.

1419.418 -> We have multiple versions of that document and can see

1422.629 -> the feedback that other users,

1425.382 -> Shirley being a great example here, has made and fed back on.

1428.76 -> So here we've created a WorkDocs site,

1431.471 -> referencing our own Active Directory.

1433.432 -> We've set policy settings for the environment,

1436.059 -> we've created users.

1437.727 -> We've created system users that have created folders for groups,

1440.814 -> allowing a homeworker

1442.524 -> or a contractor to be able to interact in real time

1445.11 -> using Hancom and feedback

1447.362 -> using the console on that WorkDocs environment.

1451.992 -> Cool, Andy. That looks really impressive.

1455.328 -> How can I get started myself?.

1458.623 -> Here's the must, should, could have.

1461.334 -> Amazon WorkDocs Drive's available for 64-bit versions of Windows 7,

1465.881 -> Windows 8 and Windows 10 if you've still got them in play

1468.383 -> and you can have it on Windows server

1471.553 -> from way back to 2008 up to all the way to 2019.

1477.142 -> Amazon WorkDocs Drives is also available, as I mentioned,

1479.603 -> for Mac OS versions 10, 11 or higher.

1482.856 -> Is there a maximum file upload limit?

1485.567 -> In the web client it's 5 gig,

1488.028 -> but the upload size using the Drive client,

1490.822 -> there's no limit for that.

1493.408 -> There should be no file type or username restrictions.

1497.537 -> Cool, so now I've provided

1500.081 -> the WorkDocs environment,

1502.501 -> what do my users need in order to be able

1504.961 -> to interact with that site as we saw in the demo?

1509.007 -> You've got the WorkDocs Drive Windows Mac client.

1511.384 -> That allows Windows Explorer shells, Mac extensions, custom icons.

1515.388 -> We saw them going to green

1517.933 -> as they've been uploaded to the environment.

1519.518 -> You've got search notifications and sync status.

1522.562 -> If you have an Android or an iOS device,

1524.814 -> the Amazon WorkDocs phone and tablet applications

1527.484 -> allow you to view, comment, download your Amazon WorkDocs files.

1531.821 -> You can also view and give feedback on,

1533.865 -> download the documents if you've got permission to do so.

1536.826 -> You can download that application from Google Play or Amazon App Store,

1540.539 -> depending on your device.

1542.249 -> You sign in with your organization name,

1544.417 -> your username and password.

1546.878 -> There will be a welcoming message from your administrator

1549.923 -> if the organization has usernames and you can set a password

1553.426 -> when you're registered

1554.386 -> if you've been invited to a WorkDocs site.

1557.847 -> The Amazon WorkDocs applications for iPhone and iPad

1562.727 -> allow you to view, comment on,

1564.104 -> download your Amazon WorkDocs files, just as with Android.

1567.357 -> You can also view, give feedback on

1569.192 -> and download other documents if you've got permissions to do so.

1573.53 -> You can download the iPhone and iPad apps from the Apple Store

1576.491 -> and sign in with your organization name,

1578.326 -> just as you can with Android.

1581.788 -> There is also the web client, which is available on Safari,

1584.874 -> it's available on Firefox, Chrome, Internet Explorer and Edge.

1592.007 -> Now with WorkDocs web client,

1593.842 -> as we've seen, you can upload, download files,

1596.553 -> organize your files in the WorkDocs environment.

1600.974 -> You can also view and comment on documents just as Shirley did

1604.06 -> and documents shared by others.

1605.854 -> The web client displays previews for many different types of files

1609.566 -> depending on the document.

1611.318 -> If your administrator enables single sign on,

1614.529 -> you can use your regular network log in

1616.531 -> to access Amazon WorkDocs.

1618.7 -> You might need to take additional steps

1620.785 -> to allow your browser to support single sign on.

1626.416 -> Andy, that's splendid.

1627.834 -> I understand how I can start a WorkDocs environment,

1631.713 -> I understand the benefit that it can bring to my organization.

1634.341 -> I've got existing file stores,

1636.134 -> is there a ready and simple way to migrate those files?.

1641.139 -> Absolutely.

1642.057 -> The Amazon WorkDocs migration service

1643.85 -> helps you move your user's files,

1645.393 -> your departmental file shares to Amazon WorkDocs.

1648.897 -> The service can migrate large amounts of data from tens of gigabytes

1651.983 -> to multiple terabytes.

1653.902 -> Using the Amazon WorkDocs migration service portal,

1657.822 -> you can configure migration tasks,

1660.241 -> select the source and target where WorkDocs account

1663.203 -> and the site to migrate the data to.

1665.664 -> You can schedule the migration task to execute during a specific period,

1669.459 -> as a one-time data transfer operation,

1671.586 -> or have period syncs so as to minimize disruption

1674.631 -> and downtime for your users.

1676.591 -> The Amazon WorkDocs migration service portal

1678.677 -> provides up-to-date information statues

1681.388 -> on migration jobs,

1682.889 -> including detailed reports

1684.516 -> once migration has successfully completed.

1688.103 -> How does it work?

1689.771 -> The WorkDocs migration service makes use of AWS DataSync

1693.441 -> that automatically handles many of the tasks

1695.568 -> related to data transfer,

1696.945 -> such as network optimization,

1699.155 -> data integrity validation,

1700.949 -> which can slow down migrations, burden your IT operations team.

1708.039 -> Software development kit, yes,

1709.916 -> there's a WorkDocs software development kit,

1711.793 -> as part of the AWS SDK.

1714.129 -> It's designed to accommodate a wide variety of use cases,

1718.174 -> spanning developer apps to enterprise integration.

1722.345 -> Amazon WorkDocs operates just as with Amazon WorkSpaces,

1728.017 -> Amazon AppStream, on a pay-as-you-go model,

1730.228 -> like all AWS services.

1732.063 -> There's no long-term commitments.

1735.15 -> Minimum users are free and can be upgraded if needed.

1739.487 -> If you have WorkSpaces, you can use WorkDocs for free,

1744.075 -> with access to all features and storage up to 50 gigs.

1747.787 -> And you can upgrade from that 50 gigs up to a terabyte.

1752.333 -> API pricing is an addition too and separate from per-user pricing.

1756.796 -> Charges apply after the 30-day trial period

1760.091 -> of the WorkDocs site has ended

1761.509 -> and only apply to third-party calls

1763.47 -> made by custom applications.

1764.888 -> There are no charges for API calls made by WorkDocs native applications,

1769.476 -> including WorkDocs web apps,

1771.019 -> WorkDocs Drive, WorkDocs Companion and AWS console operations.

1775.815 -> For APIs you pay only for what you use.

1778.61 -> There is no minimum fee.

1780.445 -> You can build new applications or create integrations

1783.573 -> with existing solutions

1785.033 -> and applications with Amazon WorkDocs.

1788.62 -> You pay for the API requests made against your WorkDocs site.

1792.665 -> API request docs are based on request type

1794.959 -> and are charged on the quantity

1796.127 -> of requests as listed on the website.

1801.382 -> Cool, we've talked through pricing,

1803.635 -> we've talked through how it looks,

1806.596 -> we've talked through demo.

1811.476 -> Where do we go next, Andy?

1813.144 -> Where can we go tomorrow? How can we get started ourselves?

1815.939 -> Amazon WorkDocs has a getting started document.

1819.609 -> You can download WorkDocs Drive

1821.361 -> on the Amazon WorkDocs site.

1822.695 -> Learn more on the documentation for WorkDocs

1825.698 -> and there is a 30-day free trial for the API use.

1830.87 -> Thank you, thank you, thank you! I hope that's been useful for you.

1834.457 -> I hope that you've got enough information

1836.96 -> in order to get started,

1838.503 -> enough information to get you up and running and I do look forward

1840.672 -> at a future re:Invent, or a future summit,

1843.466 -> you talking about how successful your WorkDocs implementation has been

1847.762 -> and how it's enabled you

1849.514 -> to be agile and help your users collaborate securely, using WorkDocs.

1853.309 -> Thanks very much!

Source: https://www.youtube.com/watch?v=haQoDdeGOBo