You want to horizontally scale in or out an Atlassian Data Center deployment based on the 'cost-effective' Utoolity AWS Quick Start forks, e.g. to semantically stop the cluster during off-hours.
...
- (Optional) Create a backup of the cluster, as outlined in How to backup/restore an Atlassian Data Center deployment for replication purposes
This is not required as such, but should likely be included as an automated convenience step down the road?!
This is highly advised for Bitbucket, and might be advised for Confluence/Jira as a safety measure too, see note above.
- Navigate to the CloudFormation console and select the target stack
- Select 'Actions → Update Stack', then 'Use current template', and click 'Next'
- Scroll down to section 'Availability/Cost (Optional)' and change 'Stack standby mode' to 'cold', keep all other parameters as is, and click 'Next' twice
- Preview your changes to confirm that the only affected resources are of type AWS::AutoScaling::AutoScalingGroup, then click 'Update'
- Once the stack has reached the UPDATE_COMPLETE status, navigate to the EC2 console to observe that the cluster nodes are shutting down (this might take a moment to start and complete based on how the underlying Auto Scaling group is configured in detail
- (Bitbucket only) Select the 'Bitbucket NFS node' and click 'Actions → Instance State → Stop'
- There is currently an issue with the Bitbucket cluster not reliably coming up again, see note above.
- Once all cluster nodes have been shut down, navigate to the RDS console and select the cluster's RDS instance (in newer deployments it is named after the stack)
- Select 'Instance actions → Stop'
Scale out
Update the applicable Atlassian Data Center cluster CloudFormation stack to scale out (Stack standby mode → 'active'):
...