This may be resolved if we can persist SHA state outside of the cluster, using either the R53 TXT record method, an object in S3, or a dynamodb record.
We can use an ASG of min1/max1 and avoid creating a new cluster on controller reboot if it can verify existence of a previous SHA key.
This may be resolved if we can persist SHA state outside of the cluster, using either the R53 TXT record method, an object in S3, or a dynamodb record.
We can use an ASG of min1/max1 and avoid creating a new cluster on controller reboot if it can verify existence of a previous SHA key.