In addition to these components, there are network considerations, such as the need for CMS VPN, two subnets and their size, availability zones, number of workspaces, and expected growth that the project team should consider in their design. The Amazon WorkSpaces service requires three components to deploy successfully:Ī directory service to authenticate users and provide access to their WorkSpace.Īmazon Virtual Private Cloud (Amazon VPC) to run Amazon WorkSpaces. The project teams are strongly advised to review this guidance in conjunction with the AWS documentation on “ Best Practices for Deploying Amazon WorkSpaces” for the best outcome for their CMS projects. This document provides high-level guidance on the use of AWS WorkSpaces at CMS AWS enclave. Additionally, the project team assumes responsibility for and manages the guest operating system (including updates and security patches), other associated application software, and the AWS-provided security group firewall configuration to allow access to CMS resources from Amazon WorkSpaces.ĪWS documentation provides the most up-to-date guidance on automating the provisioning of Amazon WorkSpaces by using the CLI or API, securing them using integrated network encryption that the Amazon WorkSpaces service provides, or enabling encryption at rest for WorkSpaces. If the project team has a different need and chooses to stand up their own AWS WorkSpaces environment, then the guidelines for this paper should be followed.ĬMS project teams can leverage existing replicated EUA/Enterprise LDAP & Okta integration to manage their users and provide multi-factor authentication (MFA) and ‘EUA Job Code’ based access to their WorkSpaces.
The project teams may initiate this request via the slack channel #ppl-python-workspaces-questions or through #cms-data-community if they wish to utilize DaaS Service offered by OIT/EADG. They may alleviate many technical concerns, including the maintenance & support of the AWS WorkSpaces for the project team. These WorkSpaces are already integrated with CMS’s identity management (Okta/EUA) and security monitoring (Splunk) services.
#Amazon linux workspaces software
Python WorkSpace (Linux version) for Data Analytics needs with existing connectivity to Informatica, DB2, and IDR and planned enhancement to AWS Workdocs for collaboration and file sharing.ĮSRI (Environmental Systems Research Institute) Geographic Information System (GIS) software WorkSpace (Windows version)
In addition, CMS projects have used WorkSpaces to allow external users to access their data analytics platforms and business intelligence tools.įor a project team who wish to leverage existing CMS investments in AWS WorkSpaces, OIT/EADG offers the following options as Data Access as a Service (DaaS):
#Amazon linux workspaces windows
With Amazon WorkSpaces, the project teams can launch a Microsoft Windows or Amazon Linux desktop within CMS AWS enclave and connect to and access their desktop software remotely. As CMS continues to undertake IT modernization and Cloud migration projects, several project teams have either implemented or planning to implement Amazon WorkSpaces as a managed desktop computing service in the CMS AWS cloud.
0 kommentar(er)
