Help Center/ TaurusDB_TaurusDB for PostgreSQL/ FAQs/ Network Security/ After My TaurusDB for PostgreSQL Instance Is Deleted, Why Can't the Associated Security Group Be Deleted Immediately?

Updated on 2025-11-14 GMT+08:00

View PDF

After My TaurusDB for PostgreSQL Instance Is Deleted, Why Can't the Associated Security Group Be Deleted Immediately?

When creating an instance, you must select a security group. If no security group is available or created, TaurusDB for PostgreSQL allocates a security group to you by default.

After an instance is deleted, it is moved to the recycle bin and retained for seven days by default. To modify the retention period, configure a recycling policy.

The deleted instance is not removed from the security group immediately until the instance is deleted from the recycle bin. Before deleting a security group, ensure that the security group is not associated with any instance. For details about how to query instances associated with a security group, see How Do I Know the Instances Associated with a Security Group?

Parent Topic: Network Security

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.

Chatbot