Once you have the production application running, you might have several reasons to clone the environment so that you can continue testing it with the production dataset or troubleshoot the actual issue in hand on your production instances. You can make use of PowerShell scripting to automate the clone process, or you can do this on the AWS Console. In this case, I have a PowerShell clone_env.ps1 which I made using the existing production instance.
This script requires four parameters as an input to clone the existing environment. You can run the script as the following command:
Successful execution will stand up another environment for you, the same as the existing one. I know there are not a whole lot of checks that I have added to this script, such as ensuring the CNAME is available, but at a high level you can automate the clone of the environment...