{
  "id": "configuring-aws-instances",
  "title": "Configure AWS EC2 instances for Redis Enterprise Software",
  "url": "https://redis.io/docs/latest/operate/rs/7.8/installing-upgrading/install/plan-deployment/configuring-aws-instances/",
  "summary": "Considerations for installing and running Redis Enterprise Software on Amazon Elastic Cloud Compute (EC2) instances.",
  "content": "There are some special considerations for installing\nand running Redis Enterprise Software on Amazon Elastic Cloud Compute (EC2) instances. \n\nThese include:\n\n- [Storage considerations](#storage)\n- [Instance types](#instance-types)\n- [Security group configuration](#security)\n\n## Storage considerations {#storage}\n\nAWS EC2 instances are ephemeral, but your persistent database storage should\nnot be. If you require a persistent storage location for your database,\nthe storage must be located outside of the instance. When you\nset up an instance, make sure it has a properly sized EBS-backed volume\nconnected. When you set up Redis Enterprise Software on the instance, make sure that [the\npersistence storage]() is configured to use this volume.\n\n\nAfter [installing the Redis Enterprise Software package]() on the instance\nand **before** running through [the setup process](),\nyou must give the group `redislabs` permission to the EBS volume by\nrunning the following command from the OS command-line interface (CLI):\n```sh\nchown redislabs:redislabs /\u003c ebs folder name\u003e\n```\n\n\nAnother feature that may be of importance to you is the use of\nProvisioned IOPS for EBS-backed volumes. Provisioned IOPS guarantee a\ncertain level of disk performance. There are two features in Redis Enterprise Software where\nthis feature could be critical to use:\n\n1. When using [Auto Tiering]()\n1. When using AOF on every write and there is a high write load. In\n    this case, the provisioned IOPS should be on the nodes used as\n    replicas in the cluster.\n\n## Instance types {#instance-types}\n\nChoose an instance type that has (at minimum) enough free memory and\ndisk space to meet the Redis Enterprise Software [hardware\nrequirements]().\n\nIn addition, some instance types are optimized for EBS-backed volumes\nand some are not. If you are using persistent storage, you should use an\ninstance type that is, especially if disk drain rate matters to your database\nimplementation.\n\n## Security group configuration {#security}\n\nWhen configuring the security group:\n\n- Define a custom TCP rule for port 8443 to allow web browser access\n    to the Redis Enterprise Software Cluster Manager UI from the IP address range you use to\n    access the Cluster Manager UI.\n- If you are using the DNS resolving option with Redis Enterprise Software, define a DNS UDP\n    rule for port 53 to allow access to the databases' endpoints by\n    using the [DNS resolving mechanism]().\n- To create a cluster that has multiple nodes all running as instances on AWS,\n    you need to define a security group that has an All TCP rule for all ports, 0 - 65535,\n    and add it to all instances that are part of the cluster.\n    This ensures that all nodes are able to communicate with each other.\n    To limit the number of open ports, you can open only the [ports used by Redis Enterprise Software]().\n\nAfter successfully launching the instances:\n\n1. Install Redis Enterprise Software from the [Linux package or AWS AMI]().\n2. [Set up the cluster]().\n",
  "tags": ["docs","operate","rs"],
  "last_updated": "2026-04-01T08:10:08-05:00"
}