These instructions indicate how to create a new VPC for an AGTEK Access server. This is useful for either testing, or migration of an entirely new constellation of server components. These instructions do not indicate how to add multiple EC2 instances to the VPC for load balancing or failover error recovery.

1. Create the VPC
2. Tag VPC for “class” as “production” or “development”, etc.
3. Create RDS instance
4. Edit RDS security group to allow for traffic from within the VPC, specific subnet
   1. e.g. source 172.30.0.0/16 or use the EC2's security group
5. Create EC2 instance
6. Edit the EC2 security group to:
   1. allow for all external on 34015 - 0.0.0.0/0
   2. allow for SSH on port 22
7. Log into EC2 instance
8. create mount point for access store on /mnt/access
9. Attach access store to EC2 instance
10. Copy following files
    1. /mnt/access/tools/bashrc to ~/.bashrc
    2. /mnt/access/tools/menu.sh to ~
    3. /mnt/access/tools/agtekaccess to /etc/init.d
    4. /mnt/access/tools/agtektomcat to /etc/init.d
11. Log into old EC2 instance
12. Shutdown (only if migrating!) old server on old EC2-instance
13. Dump old RDS MySQL to /tmp/dump.sql
14. Copy /tmp/dump.sql to new EC2 instance
15. On new EC2 instance, restore sql via:
    1. mysql -u access -p -h new-rds-endpoint.rds.amazonaws.com < /tmp/dump.sql
16. Connect to MySQL, fix DBHost column in access:customer to be new-rds-endpoint.rd.amazonaws.com
17. Assign elastic IP to new EC2 Instance
18. Change DNS entry if new elastic IP
19. Start server on new EC2
20. Test server
21. Monitor server