Amazon WorkSpaces is one of the most innovative tools that you can use to cut costs and simplify your business processes. It's a virtual environment which offers a wide open whiteboard, group chat, and file sharing capabilities in a secure sandbox that ensures data quality and productivity. However, not everyone has the licence key to access Amazon WorkSpace. If you are looking to try out this service and then move on to another better solution, this article will show you how to setup your Amazon WorkSpaces public session.
AWS Work Spaces is a cloud-based virtual computer. Generally, like other AWS services, it is managed by the AWS System Manager console. To start a public session in AWS WorkSpaces we have to make the instance with the same VPC and sub-net which was used to create the AWS Work Spaces.
Before starting the session we have to create a Session Manager.
Session Manager Pre-requirement:
Here creates an account of the IAM instance to connect with a session manager. If you have created an IAM Instance profile just verify the profile with the Session Manager.
Controlling the user session access to the instance:
By this control, you will be able to which user can access the product and which just can’t access it. Here you can control the access by providing some default policies besides you can create and control your customized policies.
Configuring the session preference:
At the time of your session, you can customize your session with some preference. Here is some example of preference’
a). Enter the code in the YAML section like this’---
schemaVersion: '1.0'
description: Test description
sessionType: InteractiveCommands
parameters:
logpath:
type: String
description: The log file path to read.
default: "/var/log/amazon/ssm/amazon-ssm-agent.log"
allowedPattern: "^[a-zA-Z0-9-_/]+(.log)$"
properties:
linux:
commands: "tail -f {{ logpath }}"
runAsElevated: true
b). Or enter the JSON section like this,
{
"schemaVersion": "1.0",
"description": " Test description ",
"sessionType": "InteractiveCommands",
"parameters": {
"logpath": {
"type": "String",
"description": "The log file path to read.",
"default": "/var/log/amazon/ssm/amazon-ssm-agent.log",
"allowedPattern": "^[a-zA-Z0-9-_/]+(.log)$"
}
},
"properties": {
"linux": {
"commands": "tail -f {{ logpath }}",
"runAsElevated": true
}
}
}
c). At last, click on the ‘Create document’
Connecting the VPC with AWS Private Lint lets you feel safe and make the environment fully safe. By this only you will be allowed to access the system by your network. Your system can not be accessed by a public network.
Disabling & enabling SSM user account administrative permissions:
This is an optional option, if you want you can take action SSM user from here.
Enable SSH connection:
This is also an optional action, to experience the best you can enable it.
Now your session is ready to use publicly.