Skip to content
This repository has been archived by the owner on Oct 19, 2019. It is now read-only.

Attempts at optimising AWS

William Parry edited this page May 3, 2017 · 1 revision
  • A user should be able to remote into their machine
  • A user should not have to log in each time (it should remember them)
  • A user should be able to install their games and have them persist

The original approach of making a new AMI each time kind of worked but it meant that if you wanted to retrieve the password for the box you couldn't (it wasn't the original AMI). This meant that the user would have to remember the password and automatically logging in with RDP wouldn't work.

  1. Using snapshots

Could not mount as primary drive so tried to mount it as secondary drive, use PowerShell to make it online (because of collision) and then use the registry to swap C: and E: around (E being the snapshotted volume). The first couple of commands worked but setting the registry didn't persist.

  1. Using a fixed EBS volume and symlinking the Steam and My Games folder

Set hard links "mklink /J source dest" but it did not persist steam login (even though looked through config). Looks as though there are registry entries. Messing around with registry copying etc probably wouldn't end well.

One option is to write a batch script that generates a shortcut to steam that has the username and password set as flags, but that would mean storing the creds in their EBS volume.

Solution

  1. Copy base AMI
  2. Get password using KeyPair
  3. Use KMS to encrypt password and store in the user profile .cloudrig folder
  4. Update AMI and tag (option to delete previous unless base)
  5. Boot up cloudrig
  6. Use KMS to decrypt password (KeyPair now redundant since not using base AMI)
Clone this wiki locally