Merge pull request #58 from MatthewVita/additional_cloud_guide_clarifications

Additional cloud guide clarifications

Author: MatthewVita

v1-Beta-AWS-Guide/assets/eb/00-options.config

@@ -1,6 +1,6 @@
 option_settings:
   aws:elasticbeanstalk:application:environment:
-    # Example: "America\\/New_York"
+    # Example: "America/New_York"
     TIMEZONE: "<<enter timezone here>>"
 
     # Example: "10.0.4.20"

v1-Beta-AWS-Guide/chapters/05-Session-Management.md

@@ -6,7 +6,7 @@ _[< previous chapter](04-Database-System.md) | [next chapter >](06-Application-S
 
 1. In the AWS Management Console, click **Services**, **EC2**, and then click **Launch Instance**.
 2. Under **Quick Start**, select "**Ubuntu Server 16.04**".
-3. Under **Choose an Instance Type**, select your preferred instance size. If you aren't sure, select "**t2.medium**".
+3. Under **Choose an Instance Type**, select your preferred instance size. If you aren't sure, select "**t2.micro**".
 4. Click **Next: Configure Instance Details**.
 
 ### Associate cache with your private network

v1-Beta-AWS-Guide/chapters/06-Application-Servers.md

@@ -12,6 +12,8 @@ _[< previous chapter](05-Session-Management.md) | [next chapter >](07-Secure-Dom
 
 ### Establish fully managed web server infrastructure
 
+_NOTE: If you are on a fresh account, you will need to look at the bottom area of the following screens for a link to "switch to previous version while we finalize the design.". Please know that TeamEpsilon will most likely be done with automated AWS solution before Amazon forces users to use this new design, which breaks the following sections._
+
 1. In the AWS Management Console, click **Services**, **Elastic Beanstalk**, and then click **Create New Application** to the top right.
 2. Enter "**openemr**" for the **Application Name**
 3. Click **Create web server**.
@@ -78,7 +80,7 @@ _[< previous chapter](05-Session-Management.md) | [next chapter >](07-Secure-Dom
 ### Post-install security update
 
 1. In the AWS Management Console, click **EC2** and then click **Instances** in the left hand pane.
-2. Clickbox the running **your_practice** instance and note the **Public DNS (IPv4)** in the bottom pane.
+2. Clickbox the running **your_practice** instance and note the **Private IP** in the bottom pane.
 3. Using this IP, SSH into the server. If you aren't sure, please review [How do I SSH into Instances](../chapters/09-Administration.md#how-do-i-ssh-into-instances) section.
 4. Run `sudo /opt/elasticbeanstalk/hooks/appdeploy/post/09-post-install-setup-file-deletion.sh` to manually remove public setup files (will be ran automatically when subsequent instances are created by ElasticBeanstalk).
 

v1-Beta-AWS-Guide/chapters/09-Administration.md

@@ -118,7 +118,7 @@ _Note: If you are not already connected to OpenVPN, be sure that the **OpenVPN C
 
 #### OpenVPN
 
-Using your "**your-username.ppk**" keypair, access your instance by following [these instructions](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/putty.html#putty-ssh). Note that step 1 can be skipped. Also note that "**user_name@public_dns_name**" is "**openvpnas@(your noted internal redis ip)**".
+Using your "**your-username.ppk**" keypair, access your instance by following [these instructions](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/putty.html#putty-ssh). Note that step 1 can be skipped. Also note that "**user_name@public_dns_name**" is "**openvpnas@(your noted internal openvpn ip)**".
 
 #### Redis Access
 
@@ -133,6 +133,10 @@ Using your "**your-username.ppk**" keypair, access your instance by following [t
 
 ## KNOWN ISSUES
 
+### I Can't Access the Billing Section
+
+Logout of AWS and relogin as the "root" user instead of the IAM user that was created for going through the guide.
+
 ### I'm Occasionally Seeing "Site ID is missing from session data!" Errors
 
 This is a known issue with this AWS Guide. This error will be shown when the ElasticBeanstalk is autoscaling a new instance. Fortunately, the time window for this error is extremely small (will only show if a user is load balanced to the new instance in a time window of about 30 seconds). However, this this downtime may be unacceptable for your use case (e.x.: bigger institutions) so you may set a finite number of instances for the load balanced cluster to minimize the chance of this error happening. Note this is not a full solution, but a workaround that will _reduce_ the odds of this error occuring: