Azure Cache for Redis Enterprise using Terraform
The Enterprise Tiers of Azure Cache for Redis are generally available as a native fully managed service on Microsoft Azure. This offering combines Azure’s global presence, flexibility, security, and compliance with Redis Enterprise’s unmatched availability, performance, and extended data structure functionality to create the best experience for enterprises. Enterprise features include:
- Open source Redis 6.0
- Zone redundancy, with up to 99.99% availability
- Active geo-replication, with up to 99.999% availability - Preview
- Redis on Flash (RoF)
- Disk persistence with recovery - Preview
- Redis Enterprise modules:
- Scaling
- Datasets up to 13TB
- Up to 2M concurrent client connections
- Over 1M ops/second
- Security
- Private Link support
- TLS connectivity
- Integrated billing and the ability to apply Azure-commitment spend
Azure Resource Manager (a.k.a AzureRM) is the deployment and management service for Azure. It provides a management layer that enables you to create, update, and delete resources in your Azure account. You use management features, like access control, locks, and tags, to secure and organize your resources after deployment.
The "azurerm_redis_enterprise_cluster" is a resource that manages a Redis Enterprise cluster. This is a template to get started with the 'azurerm_redis_enterprise_cluster' resource available in the 'azurerm' provider with Terraform.
#
Prerequisites#
Step 1. Getting StartedLogin in to Azure using the Azure CLI
#
Step 2: Clone the repository#
Step 3: Initialize the repositoryThe output should include:
Terraform has been successfully initialized
#
Step 4: Modify the variables(optional)The default variables are setup to deploy the smallest 'E10' instance into the 'East US' region.
Changes can be made by updating the variables.tf
file.
#
Step 5: Verify the planThe 'plan' output will show you everything being created by the template.
The plan step does not make any changes in Azure
#
Step 6: Apply the planWhen the plan looks good, 'apply' the template.
#
Step 7: Connect using generated outputThe access key is sensitive, so viewing the outputs must be requested specifically. The output is also in JSON format.
Example output: