updates updates

Fixed AWS server previously used name error

We noticed a 'Security Group' alert where AWS was preventing a new AWS server from being provisioned due to the new server's name matching a previously used server's name. This was resulting in a 500 error being displayed to the user.

We've pushed a fix to move past the alert and continue to provision the server on AWS.