Create and Edit a Cloud Account for Redis Cloud Ultimate

    In Redis Cloud Ultimate subscriptions, most customers build their subscriptions in our AWS accounts so that we can take responsibility to make sure that the infrastructure is in optimal condition. If you need to build your subscriptions in your own AWS accounts, we need to have access to your AWS account to help with monitoring, maintenance and technical support. To provide us with secure authorization to access your AWS accounts, you need to:

    Create IAM entities for AWS cloud accounts

    For most Redis Enterprise Cloud Flexible or Annual subscriptions deployed to Amazon Web Services (AWS), we manage the supporting infrastructure for you in dedicated AWS accounts. Redis Enterprise Cloud Annual subscriptions let you manage this infrastructure with your own AWS accounts. You’ll want these accounts to be separate from any AWS application accounts and you’ll need to create some dedicated identity and access management (IAM) entities to allow us manage the infrastructure for you.

    AWS Zone Mapping for Redis Cloud Essentials

    To get top performance from your Redis Cloud Essentials database, you want to match the AWS availability zones of your application to your Redis Cloud Essentials database. Note: If you have a Multi-AZ subscription, you do not need to map AWS zones. AWS zone mapping is not yet supported for Redis Cloud Pro and Ultimate. Why do zone mapping? As you probably know, the Amazon AWS cloud infrastructure is divided into regions across the world and Availability Zones (AZ) inside each region.

    Member of Multiple Accounts

    You can be a member of multiple accounts in Redis Cloud. For example, if you created your own account and your company has arranged its subscriptions into multiple accounts (Dev, Test, and Prod) that you are a member of. When you open the Redis Cloud menu, you see a menu like the screenshot below. When you click on the arrow, you see all of the accounts you are a member of and you can switch between the accounts.

    Using flush_all for Memcached Cloud

    Follow the instructions below to use flush_all. flush_all for SASL protected Memcached Enterprise cloud databases If your resource has SASL authentication enabled, you can’t use nc command or telnet to run flush_all on your Memcached Enterprise Cloud resource. You have to download a Memcached CLI client that supports SASL. We recommend to use the bmemcached-CLI client, and the instructions here is for this client. This instruction refers to Ubuntu OS. Make the necessary changes if you are using other Linux flavor.