Cancellation Amazon Redshift: Easy Method

What is Amazon Redshift

Overview

Amazon Redshift is a fully managed, petabyte-scale data warehousing service in the AWS ecosystem. It is designed for analytical workloads and integrates with many AWS services and third-party tools to support large-scale querying, compression, and managed storage.

Note: In Redshift, the term CANCEL specifically refers to cancelling a running database query or session; it is a technical operation (query/session level) and does not mean cancelling your AWS subscription or billing for the service.

How to cancel Amazon Redshift

• Cancel a running query: identify the process ID (PID) or session and run the SQL command CANCEL ; only superusers or users with CANCEL privilege can terminate other users’ queries. See Redshift CANCEL command.
• Stop or remove a cluster to stop compute charges: from the AWS Management Console, go to Amazon Redshift > Clusters, select the cluster, take a final manual snapshot if needed, then choose Delete (or Snapshot and Delete). Using the AWS CLI you can run aws redshift delete-cluster --cluster-identifier --skip-final-snapshot true|false; consult the cluster management docs: Working with clusters.
• For serverless or other Redshift offerings follow the specific stop/pause or delete instructions in their doc pages (Serverless has different lifecycle steps). Verify permissions (IAM) and create any final snapshots or exports before deletion to avoid data loss.
• If you have billing or account-level concerns (stop recurring charges, reserved node purchases, or close an account), open an AWS Support case via the Support Center or contact AWS Billing; see AWS Support.

What happens when you cancel

When you cancel a running query, only that query/session ends; other queries and cluster operations remain active. When you delete a cluster (the usual way to stop ongoing charges for provisioned Redshift), compute resources are terminated and you will no longer be billed for the cluster instance hours.

Deleting a cluster without taking a final snapshot can cause irreversible data loss. Snapshots and backups may remain and can continue to incur storage charges until they are deleted or exported. Some retained items (manual snapshots, automated snapshots retained by your snapshot retention settings) will continue to exist and may incur fees.

Will I get a refund?

AWS does not provide automatic monetary refunds for Amazon Redshift downtime or expected billing; service interruptions and performance failures are addressed under the AWS service-level terms via Service Credits, not direct cash refunds. Claims for Service Credits must be submitted according to the Redshift SLA and usually require documentation of the incident and timing.

Service Credit claims typically must be filed within two billing cycles of the incident and include the required details to validate the claim. Unauthorized or improper usage is not eligible for refund; only Service Credits are provided under the SLA when its conditions are met. For detailed SLA steps and submission rules see the Redshift SLA page: Amazon Redshift Service Level Agreement.

Amazon Redshift plans and pricing

These are approximate CAD conversions of USD on-demand prices (third-party tracker, May 2025) using an estimated exchange rate. For exact CAD pricing, region-specific taxes, reserved instances, or savings plans, use the AWS Pricing Calculator or contact AWS Sales.

Your consumer rights in Canada

Amazon Redshift subscriptions and use are governed by AWS agreements and the Redshift SLA; there is no general statutory “14-day refund right” specific to this cloud service. For typical cloud service purchases, cancellation and refund terms are set by the contract with AWS rather than a consumer cooling-off period.

If you believe you are entitled to compensation under the SLA, follow the SLA claim procedure promptly (claims are normally required within two billing cycles). For alleged unauthorized charges, contact AWS Billing Support immediately and preserve supporting records (billing invoices, timestamps, and case IDs).

Customer experiences

Users in Canada and elsewhere commonly praise Redshift for multi-datatype support, strong compression and performance, and deep integration with the AWS ecosystem; Capterra reviewers give an average rating around 4.4/5 and GetApp reviewers call it fast and scalable.

Common criticisms include limits on concurrency, less elasticity compared with some competitors (e.g., Snowflake or BigQuery), and the need for experienced DBAs to configure and optimize clusters. Some reviewers also cite complexity and potentially higher cost for certain workloads.

Documentation checklist

• Account ID, cluster identifier(s), and region (e.g., ca-central-1)
• Final snapshot ID(s) or confirmation of snapshot policy
• Relevant billing invoices and timestamps for the period in question
• Query/session IDs and PIDs if cancelling running queries
• SLA incident timestamps, error logs, and any Support case numbers

Common mistakes

Deleting a cluster without creating a final snapshot is a frequent and irreversible mistake; always take a final manual snapshot if you may need the data later. Another common error is assuming deleting a cluster immediately removes all charges - snapshots and exported data can still incur storage fees if not cleaned up.

Users sometimes attempt to use the CANCEL SQL command expecting account- or subscription-level cancellation; remember that CANCEL only targets running queries or sessions. Also, many expect cash refunds for downtime - AWS provides Service Credits under SLA criteria, not monetary refunds in most cases, so missing the SLA claim window (usually two billing cycles) can forfeit relief.

Comparative recap

After cancelling

After you cancel queries or delete a cluster, export or secure any final logs and snapshots you need, and verify billing to confirm charges have stopped. If you plan to remove all traces, delete manual snapshots, automated snapshot exports, and any ancillary S3 exports or snapshots that could incur storage fees.

Useful resources: Redshift documentation (Amazon Redshift Documentation), CANCEL command docs (CANCEL), Redshift SLA (SLA), and AWS Support (Support) and Billing Console (Billing Console).

Address

For registered notices or mailed correspondence, you can send documents to:

Amazon Web Services Canada, Inc., 120 Bremner Blvd, 26th Floor, Toronto, ON, M5J 0A8, Canada.

For traceability, it is recommended to send any formal cancellation letter via registered mail with return receipt (A/R) to confirm delivery and preserve proof of receipt.