- Newest
- Most votes
- Most comments
I understand you're experiencing unexpected billing for Amazon Managed Streaming for Apache Kafka (MSK) and want to delete the resource. To help you resolve this issue, I'll guide you through the process of locating and deleting an MSK cluster.
First, it's important to note that you should ensure you have a backup of any important data stored in the cluster before deletion, as this process cannot be undone.
To delete an MSK Provisioned cluster, you have two main options:
-
Using the AWS Management Console:
- Sign in to the AWS Management Console and open the Amazon MSK console.
- In the list of clusters, find and select the checkbox next to the cluster you want to delete.
- Click on the "Delete" button and confirm the deletion when prompted.
-
Using the AWS Command Line Interface (CLI):
- Open your command line interface.
- Run the following command, replacing 'ClusterArn' with the Amazon Resource Name (ARN) of your cluster: aws kafka delete-cluster --cluster-arn ClusterArn
If you're unsure of your cluster's ARN, you can list all clusters in your account to find it.
After deletion, the billing for this cluster should stop. However, keep in mind that AWS billing is often delayed, so you might see charges for a short period after deletion.
If you're still unable to locate the cluster, it's possible that it might be in a different AWS region than you're currently viewing. Make sure to check all regions where you might have created resources.
If you continue to have trouble locating or deleting the cluster, or if you see ongoing charges after deletion, it would be advisable to contact AWS Support for further assistance. They can help you identify any hidden resources or resolve any billing discrepancies.
Sources
Delete an Amazon MSK Provisioned cluster using the AWS Management Console - Amazon Managed Streaming for Apache Kafka
Delete an Amazon MSK Provisioned cluster using the AWS CLI - Amazon Managed Streaming for Apache Kafka
Hello, Since this has to do with billing , AWS Support team could help you on this. I would advice you to contact them immediately by opening a ticket to them.
Thanks
Relevant content
- asked 8 months ago
- asked 6 months ago
- Accepted Answerasked 2 months ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 18 days ago