Streaming the AWS Wickr desktop client with Amazon AppStream 2.0
AWS Architecture BlogStreaming the AWS Wickr desktop client with Amazon AppStream 2.0by Charles H. | on13 JAN 2023| inAmazon EC2,Amazon Simple Storage Service (S3),Architecture,AWS Wickr|Permalink|ShareAmazon Web Services (AWS) customers usingAWS Wickrwho want to find a way to access their AWS Wickr Windows desktop client though a web browser, can useAmazon AppStream 2.0to stream the application through to their users.Using this architecture, you can provide lightweight access to the AWS Wickr desktop client for users that cannot install it onto their local device. By using AppStream 2.0, you can focus on managing your AWS Wickr network while AppStream 2.0 manages the AWS resources required to host and run the application, scaling automatically and providing on-demand access to your users.If you want to ensure that AWS Wickr user data persists between streaming sessions, you can make use of AppStream 2.0 user persistence to securely save user data (including AWS Wickr client data) toAmazon Simple Storage Service(Amazon S3).In this post, we discuss how to build an AppStream 2.0 image for AWS Wickr on Windows, enable persistence for users, and deploy a stack.Solution overviewThese steps will illustrate deploying an AppStream 2.0 Windows Image Builder to a single availability zone. Then we deploy an AppStream 2.0 fleet with internet access and user data persistence to three availability zones for high availability.Review theRegions and Availability Zonesdocumentation and theAWS Regional Services Listto choose the best Region for your deployment, as well as the networking and bandwidth requirements forUser Connections to Amazon AppStream 2.0.Figure 1. AWS Wickr with Amazon AppStream 2.0 ArchitectureCostThe costs associated with using AWS services when deploying AppStream 2.0 and AWS Wickr in your AWS account can be estimated on the pricing pages for the services used.WalkthroughThis walkthrough takes you from installing the AWS Wickr for Windows desktop client onto an AppStream 2.0 Image Builder, to configuring the client for persistence, and finally to deploying a fleet and stack for your users to consume:Install AWS Wickr for Windows client onto your AppStream 2.0 Windows Image Builder.Configure the client using the Image Assistant to set up user data and settings persistence.Create an on-demand instance streaming fleet.Create a user stack and enable user data and settings persistence.Create a user pool.Test your streaming application and prove data persistence.PrerequisitesYou should have the following prerequisites:Familiarity with AppStream 2.0 and an existing AWS Wickr account with associated credentials. Currently, it is not possible for an AWS Wickr user to register their account over AppStream 2.0.An AWS account with access to AppStream 2.0. Instructions for setting up an AWS account can be found atSetting Up for Amazon AppStream 2.0.A running AppStream 2.0 image builder, based on the WinServer2019-10-05-2022 base image with the AWS Wickr for Windowsclient installerdownloaded to it.An up-to-date Google Chrome browser (if you want to use your device’s webcam).Install AWS WickrAppStream 2.0 usesAmazon Elastic Compute Cloud(Amazon EC2) instances to stream applications. You launch instances from base images, called image builders. In this step you will install the AWS Wickr client onto your image builder before moving on to configuration.Connect to your image builder as anAdministrator.Run the AWS Wickr installer and carry out the following steps:On theWelcome to the AWS Wickr Setup Wizardprompt, chooseNext.ForInstallation Type, chooseEverybody (all users).ChooseNextto accept the default installation folder.ChooseInstall.Once the AWS Wickr client has finished installing, uncheckLaunch Wickron the final screen, and then chooseFinish.Run the Image AssistantTo create your own custom image, connect to an image builder instance, install and configure your applications for streaming with guidance from the Image Assistant, and then create your image by creating a snapshot of the image builder instance:Run theImage Assistantshortcut found on the desktop.Under1. ADD APPS, chooseAdd App.ChooseProgram Files,Amazon Web Services,Wickr, andAWS Wickr.Scroll to the bottom, choose theWickrapplication, and then chooseOpen.In the pop-up that appears, customize theNameandDisplay Name(if needed), and then in theLaunch Parametersbox, enter-datalocation “C:\Users\%username%”(Figure 2).Figure 2. Updating Launch ParametersNote: If you want to mask the name of the application within the URL used for streaming, replace the Display Name field text with something else.ChooseSave.Wickr will now appear as an app on the Image Assistant screen. ChooseNext.Under the2. CONFIGURE APPSstage, follow the instructions from 1-5, chooseSave settings, and chooseNext(Figure 3).Figure 3. Configuring the Application with Image AssistantUnder the3. TESTstage, carry out steps 1-3.Under the4. OPTIMIZEstage, selectLaunch.As instructed, once the app has launched successfully, selectContinueand wait for the app to be optimized.Under the5. CONFIGURE IMAGEstage, give the image that will be created aName,Displayname, andDescription.Choose theAlways use latest agent versioncheckbox. This ensures that new image builders or fleet instances that are launched from your image always use the latest AppStream 2.0 agent version, and then select Next (Figure 4).Figure 4. Finalizing the Application ImageUnder the6. REVIEWstage, selectDisconnect and Create Image. Your session will be terminated while your image is being created.Create an AppStream 2.0 fleetWith AppStream 2.0, youcreate fleet instancesand stacks as part of the process of streaming applications. A fleet consists of streaming instances that run the image that you specify.Return to the AppStream 2.0 management console.ChooseFleetsfrom the menu on the left.Choose yourFleet type(this demonstration usesOn-Demand) and chooseNext.Give the Fleet aName,Display name, and aDescription.Note: If you wish to mask the name of the fleet within the URL used for streaming, replace theNameandDisplay namesection with something else.Choose yourFleet instance type(this walkthrough uses a general purposestream.standard.largeinstance type).Adjust theFleet capacityas required, leave the other sections as they’re displayed by default, and chooseNext.On theChoose an Imagescreen, choose the image you created earlier.On theConfigure networkscreen, chooseEnable default internet accessand choose your VPC, along with three subnets that you will deploy into. Finally, choose theSecurity groupthat you will use to restrict access (the default is to allow access from all IPs). ChooseNext.Review your settings and then chooseCreate fleet.Create an AppStream 2.0 stackAstackconsists of an associated fleet, user access policies, and storage configurations. In this step, you will create a stack, enable application settings persistence, and associate the stack with the fleet you provisioned previously.From the menu in the AppStream 2.0 management console, chooseStacks.ChooseCreate Stack.Give the stack aName, and optionally aDisplay nameandDescription.Leave all other options as they’re displayed by default and chooseNext.In theEnable storagewindow, ensure thatEnable home foldersis selected, leave all the settings as they are, and chooseNext.In theEdit user settingssection, modify the copy and paste functionality to your requirements, and ensure thatEnable application settings persistenceis selected. ChooseNext.Review your configuration and chooseCreate stack.You will now be presented with an overview of the stack you have created. Choose theActiondropdown list and chooseAssociate fleet.From the dropdown list, choose the fleet that you previously provisioned and chooseAssociate.Create an AppStream 2.0 user poolUsers can access application stacksthrough a persistent URL and login credentials by using their email address and a password that they choose. In this step, you will create a user and assign it to a stack so you can access your AppStream 2.0 streaming session.ChooseUser pool.ChooseCreate user.Enter an email address, first name, and last name, and then chooseCreate User.In theUser poolwindow, choose theUserand then chooseAction.ChooseAssign stack, choose the newly created stack, and chooseSend email notification to user.ChooseAssign stack.You will receive two emails. Follow the instructions on the one titledStart accessing your apps using AppStream 2.0to access your app.Launch your AppStream 2.0 streaming sessionIn this step, you will use the user created earlier to log in to an AppStream 2.0 streaming session. You will then prove AWS Wickr user data persistence by exiting and logging back into your session.Note: You will only be able to launch your session once your fleet has been provisioned. This can take around 15-20 minutes.Choose thelogin page linkfrom the email you received in the previous section and log in.You will be presented with the AWS Wickr client icon. Choose it to start your session.Log in to the AWS Wickr client with your credentials.As you have application persistence enabled, you can close the tab and the session will pick up from where you left it when you log back in (Figure 5).Figure 5. Accessing the Streaming ApplicationCleanupTo avoid incurring future charges, delete the stack, user, fleet, custom image, and image builder that you have created.ConclusionIn this post, we demonstrated how customers can take advantage of AppStream 2.0 as a managed service to enable the provisioning of AWS Wickr clients for users, with persistence between sessions, through a web browser.Charles H.Charles is the Senior Solutions Architect Security Specialist for AWS Wickr in EMEA. Charles is based in the UK and supports customers across all sectors with their adoption of Wickr. He loves speaking with customers on how other AWS Security services can help make them more secure, plus experimenting with other AWS services on how they can be leveraged by our customers.
Amazon Web Services (AWS) customers using AWS Wickr who want to find a way to access their AWS Wickr Windows desktop client though a web browser, can use Amazon AppStream 2.0 to stream the application through to their users. Using this architecture, you can provide lightweight access to the AWS Wickr desktop client for users […]
Charles H.
Amazon EC2 Amazon Simple Storage Service (S3) Architecture AWS Wickr