...
Open an entry in the Platform AWS Log. It is helpful to think though exactly what you are going to do and write it down. Then as you execute the change, if you deviate from the steps you wrote in the log, change the log. In the end when you haven't made any mistakes and everything has gone smoothly you will think this was a waste of time. It wasn't. The closer you are to a big demo the more true this will be.
Crowd (skip if using existing crowd deployment)
In most cases you should be re-using existing Crowd instances. We currently have two crowd servers running:
prod: https://dev-crowd.sagebase.org:8443/crowd/console
staging + test (shared): https://prod-crowd.sagebase.org:8443/crowd/console
If setting up a new Crowd server or for help troubleshooting see: Setting Up Production Crowd
If you just need to point a stack at a particular crowd instance, you do this by setting the org.sagebionetworks.crowd.endpoint in the stack.properties file (URLs as above minus the /crowd/console bit)
...
Click on 'Load Balancer' tab
For 'HTTP Listener port' choose 'OFF' for the repo and auth services, choose '80' for the portal.
For 'HTTPS Listener port' choose '443'.
For 'SSL Cert' choose arn:aws:iam::325565585839:server-certificate/SynapseCert
Configure Notifications
Click on 'Notifications' tab
Set Email Address to 'platform@sagebase.org'
Configure Container
Click on 'container.'
In the JVM Command Line Options For a production deployment:
...