Client amazon workspaces login registration#
Client amazon workspaces login download#
Client amazon workspaces login windows#

And again, as you might remember from an earlier movie, we could change this bundle by either installing, or we could use a different base image that had other applications installed on it.

and you have your Linux, a replacement desktop running on the Amazon cloud with the various tools that come with this bundle. And you can see now we're in a Linux WorkSpace instance. So now, I'm going to go ahead and log in to this Linux WorkSpace and you'll see what the client looks like. Once you do that, on subsequent log-ins, you won't need the reg code, and you will use the username and password.

And then, you will be presented with the screen with the username and asked to change the password.

You're going to need to provide the registration code. And then for the first time when you connect, what you're going to need to do is provide the, and I'll just go back and show you.

So what then happens is you will download your version of the client, and you'll have a thick client basically running on your device. So what that does is that generates a email that's sent to the user. And then you select the WorkSpace, it has to be available or on, as you can see it is right here.

And you can see here's all the various choices along the bottom here from a Windows desktop, Mac, to tablets and iPads. So the clients are downloadable based on what kind of client device you're using. And the way that you would access this is with the traditional client.

And if you drill in, you can see that I have a registration code. So I have a Linux WorkSpace that's available. You can see in the WorkSpaces section here, that what I've done is I've just given a different username, but it's the same email. So it's just a tip from the real world, really. So a tricky way around this for testing is to give different usernames to the same email. And that's logical if you think about it because if you're a user logging in, you only need one WorkSpace or one desktop. Another thing to note here is you can only identify one user with one bundle. And then I just deleted that and then recreated it with WSP for demonstration purposes. So what I did is I had originally created a Windows bundle with PCoIP. The default is the PCoIP, but if you scroll down, you can see now you have WSP for Windows only, not for Linux. And of note is when you're creating a bundle, that's actually why I did this. It's web streaming protocol, and it allows you to access from a browser client. The WSP is a new protocol, relatively new as of this recording. The PCoIP or over IP is you're going to use a client that you download. You have a number of different options in terms of bundles and hardware, software, and a new option is protocols. Just have to add a user to get to that point. You'll remember from a previous movie, when you go to launch a WorkSpace, you have, and I'll just get to that point here. And so you would need to fill out a support ticket if you want to do any production level testing of let's say different sized WorkSpaces. A default Amazon account has a pretty low quota. Another thing you need to allocate is appropriate quota in your account, really to protect you from spinning up too many WorkSpaces and incurring costs. So when you're testing, you need to allocate appropriate time.

And if it's more powerful, it can take even longer. I'll remind you that it takes between 20 minutes and a half an hour for a test WorkSpace to be created. As we drill in and look at WorkSpaces with a little bit more detail, what I've done is I've recreated a different version of the Windows WorkSpace for a reason that will become apparent in a minute here.

Client amazon workspaces login registration#

Client amazon workspaces login download#

Client amazon workspaces login windows#