update docs

deploy/awstools/awstools.py

@@ -48,7 +48,7 @@ def get_f1_ami_name() -> str:
     else:
         if cuser != "centos":
             print("Unknown $USER (expected centos/amzn). Defaulting to the Centos AWS EC2 AMI.")
-        return "FPGA Developer AMI - 1.12.1-40257ab5-6688-4c95-97d1-e251a40fd1fc"
+        return "FPGA Developer AMI - 1.12.2-40257ab5-6688-4c95-97d1-e251a40fd1fc"
 
 def get_incremented_f1_ami_name(ami_name: str, increment: int) -> str:
     """ For an ami_name of the format "STUFF - X.Y.Z-hash-stuff",

docs/Getting-Started-Guides/AWS-EC2-F1-Tutorial/Initial-Setup/Setting-up-your-Manager-Instance.rst

@@ -35,6 +35,7 @@ To launch a manager instance, follow these steps:
    ``FPGA Developer AMI - 1.12.2-40257ab5-6688-4c95-97d1-e251a40fd1fc`` and
    select the AMI that appears under the **Community AMIs** tab (there
    should be only one). **DO NOT USE ANY OTHER VERSION.** For example, **do not** use `FPGA Developer AMI` from the *AWS Marketplace AMIs* tab, as you will likely get an incorrect version of the AMI.
+   If you find that there are no results for this search, you can try incrementing the last part of the version number in the search string, e.g., ``1.12.2 -> 1.12.3``. Other parts of the search term should be unchanged.
 #. In the *Instance Type* drop-down, select the instance type of
    your choosing. A good choice is a ``c5.4xlarge`` (16 cores, 32 GiB) or a ``z1d.2xlarge`` (8 cores, 64 GiB).
 #. In the *Key pair (login)* drop-down, select the ``firesim`` key pair we setup earlier.
@@ -72,6 +73,22 @@ To launch a manager instance, follow these steps:
 
 #. Click the orange *Launch Instance* button.
 
+
+.. warning::
+    Recently, some AWS users been having issues with the launch process (after
+    you click ``Launch Instance``) getting stuck trying to "Subscribe" to the
+    AMI even when the account is already subscribed. We have been able to
+    bypass this issue by going to the FPGA Developer AMI page on AWS
+    Marketplace, clicking subscribe (even if already subscribed), and then
+    following the prompts about launching an instance until you get to the
+    point where you can select "Launch via EC2" in a dropdown. Once you click
+    continue on the page with "Launch via EC2", you will be brought back to
+    the usual launch instance page, but the AMI will be pre-selected and you
+    will be able to successfully launch at the end, after updating the rest
+    of the options as noted above.
+
+
+
 Access your instance
 ~~~~~~~~~~~~~~~~~~~~