cat ~/.ssh/id_rsa.pubĬopy the content of the key, it should start with “ssh-rsa” and finish with your username and hostname. Once the program has completed the key creation, we will need to retrieve the public key. The terminal will ask you where to save the new key, press enter to validate the default path (\.ssh\id_rsa). In order to address this issue, we are going to do an SSH port forwarding between the license server instance and your Nimble Studio workstation. If you try to click the “Sign in” on the homepage of the license server it will fail with the following message: “Activation is possible only from local machine”. Unfortunately, we cannot activate the license server remotely for safety reasons. If this is the case, give it a few more minutes to start, but if after 10 minutes the session manager is still not available check that you gave the correct policies to the role you created in the prerequisites section (it must have the policy “AmazonSSMManagedInstanceCore”). Note if you have just started your server, it is possible that the session manager will not be available quite yet, even if the health check shows 2 on 2 in the console. Choose “Session Manager”, then click the orange “Connect” button. In the table select your license server, then in the top bar click the button “Connect”. For that, go into the AWS console, search for EC2, then in the left column click “Instances”. We will now install the Chaos License server and configure it. Activate the Chaos License serverĪt this stage of the tutorial, you should have a running, but empty Linux server. Wait for it to be fully booted (“Status check” should indicate “2/2 checks passed” in the EC2 instance list on the AWS console) to continue this tutorial. Congratulations, your license server should now be starting! We will now have to configure it.
0 Comments
Leave a Reply. |