Troubleshooting Managed Bodo Cloud Platform Issues on AWS
Here are solutions to potential issues you may encounter while using the Bodo Cloud Platform:
Cluster Creation Fails
Most of cluster creation failures are usually due to one of the following:
Your account hits AWS resource limits such as limits on the number of VPCs and EC2 instances
Your AWS credentials do not have the required permissions (see Setting AWS Credentials)
AWS does not have enough of the requested resources (such as some of the large EC2 instances)
In case of failure, the logs are made available on the platform and should provide some details regarding why the failure occurred. Even though cluster creation was not successful, some AWS resources may still have been provisioned. Click on the delete icon to remove all the created resources, otherwise you may incur charges for the provisioned AWS resources. You can try to create a cluster again after addressing the underlying issue such as increasing limits or providing AWS credentials with the required permissions.
Cluster Deletion Fails
Failures during cluster deletion are very rare and usually only occur when the provisioned resources have been manually modified in some way. In these cases, logs are provided to help you diagnose the issue. For instance, if logs indicate that some resource cannot be deleted due to a dependent resource, you can try to delete the resource manually through the AWS Management Console and try to remove the cluster through the platform again.