Please Note: This article is part of our historical archive. Because it was published a while ago, some of the information, links, or context may now be outdated.
Wondering how to fix the Error DBInstance xxxxxxxxx was not found during DescribeDBInstances? We can help you with this!
As a part of our AWS Support Services, we often receive similar requests from our AWS customers.
Today, let’s see the steps followed by our Support Techs to help our customers to resolve the DBInstance error.
Error DBInstance xxxxxxxxx was not found during DescribeDBInstances
If we delete an Amazon RDS database that is a part of our Elastic Beanstalk environment, we might receive this error. The lifecycle of that database is tied to the Elastic Beanstalk environment. Elastic Beanstalk gets out of sync with our database resource if we delete that database from the Amazon RDS console. Also, it can’t be deleted.
Now let’s see the steps to resolve this DBInstance error:
- Log in to the AWS Management Console and open the AWS CloudFormation console.
2. Select Stacks.
3. Now we can select the stack for the Elastic Beanstalk environment that we want to delete from the Stack name column.
We can identify our stack by checking that the environment ID from the Description column in the AWS CloudFormation console matches the environment ID of our Elastic Beanstalk environment.
4. Then select Delete.
5. Now from the pop-up window, select the AWSEBRDSDatabase check box in the Resources to retain – optional section.
Here the AWSEBRDSDatabase is the name of the resource that we want to skip or retain while deleting the stack. The stack can delete successfully if we skip this database resource,
6. Then select Delete Stack.
7. We can also use the AWS CLI to delete a stack with the following command:
aws cloudformation delete-stack --stack-name OurStackName --retain-resources AWSEBRDSDatabase
8. Finally, we can terminate our Elastic Beanstalk environment after the status of stack changes to DELETE_COMPLETE status.
[Need help with more AWS queries? We’d be happy to assist]
Conclusion
To conclude, today we discussed the steps followed by our Support Engineers to help our customers to fix the ‘Error DBInstance xxxxxxxxx was not found during DescribeDBInstances’.
