Skip to content

Latest commit

 

History

History
24 lines (23 loc) · 2.99 KB

running-stacks.org

File metadata and controls

24 lines (23 loc) · 2.99 KB
PersonOrganizationUsernameAMIStatus
Steven BermanDeloittesteven? ami-0f6b2119Stopped
Veronica Sara WeinerProbcompguest-1? ami-0f6b21198/12/17 Supposed to migrate to probcomp cluster
Brian PaulsProbcomp / visitorbrian? ami-0f6b2119Stopped
Andrew BoltonAcademic collaboratorandrew? ami-0f6b21198/12/17 Continuing to use for the forseeable future
ZaneProbcompzane? ami-0f6b2119Stopped
Marie HuberProbcompmarie? ami-0f6b2119Stopped
Stuart AltschuletBank of Americaoreilly-223ami-751b2c63Stopped
Guillaume AlleonAirbusguillaumeami-751b2c63Stopped
William McInroyProbcompliamami-751b2c63Stopped
Michael TruellProbcompmichaelami-751b2c63Stopped
Veronica Sara WeinerProbcompvsw-nelson?Stopped
Veronica Sara WeinerProbcompvsw-nelson-eeg?Stopped
Veronica Sara WeinerProbcompvsw-nelson-survey?Stopped
Marie HuberProbcompmariehuberami-751b2c638/12/17 Plan to teach how to stop and restart herself
Andrey KovalVancouver Island Health Authorityschool-39ami-751b2c63Week-to-week, since the PPAML summer school

The AMI is relevant because cloudformation update-stack will destroy and recreate the instance, losing all data on it, if one asks to change the AMI (even inadvertently). The AMI also indicates (indirectly) whether the Jupyter server will restart on its own if the instance is rebooted.