Changes

** Delete your ww VM. In AWS terminology that's '''Terminate www''': [[File:AWSTerminate.png|800px|border|center]] The VM will be shut down and then deleted. But not immediately. It will still show up in the list for some time, rename with the state "Terminated". Eventually it will dissapear without any further action from you. When you delete an instance on AWS: the virtual disk used by that instance will also be deleted. But any extra EBS devices you added to it will not be deleted automatically. That's going to be very useful in this case. After you terminate ww: go to Elastic Block Store, Volumes and note that www-deleteddata is still there. ** Modify Navigate to Subnets in the VPC Management Console and modify subnet -ops345 to not autoAuto-assign public IPsIP addresses: [[File:AWSNoAutoPublicIP.png|800px|border|center]] * Then create a new VM with the following configuration:** '''vpc-ops345'''** '''subnet-ops345'''** Primary IP on eth0 '''10.3.45.11'''** Recreate Reuse the '''ops345wwsg''' security group (it was not deleted with ww)** Name the new VM '''www instance with ''' (not ww)After the same steps, except specify a primary ipmachine starts you can SSH to it exactly as you SSHed to ww (via port 2211 on router).** Install httpdCreate a user with your username and sudo privileges, phpdelete ec2-user** Set the hostname to be '''www.youruserid.ops345.ca''' permanentlyTo get install software you'll be in a bit of a bind because yum install downloads software from online repositories and www doesn't have internet access.* You can add a temporary public IP to work, an instance which does not get a public IP automatically: allocate a new elastic ip IP named "temporarytemporary_ip" , and associate it with the wwwinstance.* Install httpd and php*