Unmapping a Redis Cloud account from Google Cloud Marketplace (GCP MP) requires careful preparation to avoid billing or data loss issues. This guide explains the required prerequisites, the step-by-step procedure in the Redis Cloud Console, troubleshooting common issues, and special considerations for last remaining accounts or legacy 3PIC contracts. Following these steps ensures you can disconnect safely with minimal risk of service interruption.
Prerequisites
Before unmapping, confirm the following:
Permissions in GCP: You must have either the Billing Administrator (
roles/billing.admin) role or a combination of Billing User (roles/billing.user) and Consumer Procurement Order Administrator (roles/consumerprocurement.orderAdmin) on the GCP billing account.Permissions in Redis Cloud: You must be the Account Owner in the Redis Cloud Console.
Payment Method Preparation: Add a valid credit card and switch all active subscriptions to that card if your account is iSaaS-based. The UI will block unmapping if subscriptions still use Marketplace billing.
Account Type Verification: Identify whether your Redis Cloud account is under the legacy 3PIC contract (Marketplace-only billing, no fallback) or the modern iSaaS model (supports switching to credit card). The unmapping steps differ.
See the Redis Cloud GCP Marketplace integration docs for more background on account mapping models.
Step-by-Step: How to Unmap (Disconnect)
Log in to the Redis Cloud Console and select the account to disconnect.
Switch Payment Methods: Under Billing & Payments → Payment Methods, add a credit card and update each subscription to use it instead of Marketplace.
Disconnect Account: Still under Billing & Payments, select Disconnect (or Remove Marketplace Account) to unmap if this is not the last account linked to the Marketplace contract.
Special Case – Last Account: If this is the last Redis Cloud account mapped to the Marketplace contract, you must unsubscribe directly in the Google Cloud Console → Marketplace → Your Orders. This action ends the contract and may trigger resource deletion depending on your subscription model.
For details, see Google’s Cancel a Marketplace offer guide.Confirm Success: After unmapping, the Redis Cloud Console should no longer display Marketplace as a payment option, and all subscriptions should reflect the credit card method.
Troubleshooting & Common Scenarios
Error: “Cannot unmap from Marketplace while Redis resources are using Marketplace for payment.”
Add a credit card and update every subscription’s payment method before retrying.Last account cannot be unmapped in Redis Cloud UI.
Use the GCP Console to unsubscribe from the Marketplace listing.No option to add a credit card.
This indicates a 3PIC legacy account, which does not support fallback payment methods. Unsubscribing in GCP Marketplace is the only path.Resources deleted after unsubscribing.
If you fail to migrate subscriptions before unsubscribing, Redis Cloud deletes affected databases after the grace period (typically 5 days under 3PIC).Missing “Manage on Provider” button in GCP Console.
Verify that you are in the correct GCP project and signed in with a user who has the required IAM roles.
Special Considerations
Last Remaining Account
The last account on a Marketplace contract must always be unmapped by unsubscribing in the GCP Console.
3PIC (Legacy) vs. iSaaS
3PIC: Marketplace billing only; no credit card option. Unsubscribe in GCP → resources deleted after grace period.
Refer to the official Google documentation on canceling Marketplace offers.iSaaS: Can switch to a credit card before disconnecting, allowing safe unmapping in the Redis Cloud Console.
Key Takeaways
Always switch payment methods before disconnecting.
Only Account Owners can perform unmapping.
The last account must be unmapped in the GCP Console, not in Redis Cloud.
Back up all critical databases before making billing changes, as unsubscribing can delete resources.
Contact Redis Support for complex billing or migration cases.
0 comments
Please sign in to leave a comment.