AWS ElastiCache

Amazon ElastiCache is a serverless caching service delivering real-time, cost-optimized performance for modern applications. DuploCloud supports Memcached, Redis, and Valkey ElastiCache instances.

Creating a Memcached ElastiCache Instance

1. In the DuploCloud Portal, navigate to Cloud Services -> Database.

2. Select the ElastiCache tab and click Add. The Create a ElastiCache page displays.
3. Enter a database Name.

4. Specify the number of Replicas.

5. In the Type list box, select Memcached.

6. Select the Memcached Version.

7. Select the node size in the Size list box.

8. Click Create. The Memcached ElastiCache instance is created.

Creating a Redis or Valkey ElastiCache Instance

1. In the DuploCloud Portal, navigate to Cloud Services -> Database.

2. Select the ElastiCache tab and click Add. The Create an ElastiCache page displays.

1. Enter a database Name.

2. Specify the number of Replicas.

3. Optionally, enable Automatic Failover: if the primary node in the cluster fails, one of the read replicas is automatically promoted. This setting requires at least two replicas.

4. Optionally, enable Cluster Mode and specify the No Of Shards.

1. Optionally, configure snapshots for backup:

1. Optionally, click the CloudWatch link above the Log Delivery Configuration field to enable exporting engine logs and slow logs to Amazon CloudWatch Logs.

   • Complete the fields to configure CloudWatch:

     • Log Format

1. Click Create. The Redis or Valkey database instance is created.

Updating Snapshot Retention Limit

After a Redis or Valkey ElastiCache instance is created, most settings cannot be changed without deleting and recreating the instance. However, you can update the Snapshot Retention Limit at any time.

To update the Snapshot Retention Limit:

1. Navigate to Cloud Services -> Database.

2. Select the ElastiCache tab.

3. Click on the name of the ElastiCache instance in the NAME column.

4. Click Actions, and select Update Snapshot Retention Limit. The Update Snapshot Retention Limit

Creating an ElastiCache Global Datastore

DuploCloud supports ElastiCache Global Datastores, which allow you to replicate a Redis cluster across AWS regions.

Creating a Global Datastore

When you create a Global Datastore in DuploCloud, a primary Redis cluster, in the current Tenant, and a secondary cluster in a different region are created automatically as part of the process. You can then add additional secondary clusters in other regions as necessary.

1. Navigate to to Cloud Services → Database → ElastiCache → Global Datastores.

2. Click Add. The Create a Global Datastore pane displays.
3. Complete the fields, as required for your configuration:

1. Click Create to provision the ElastiCache Global Datastore.

Adding Regional Clusters

After creating a Global Datastore, you can add secondary clusters (regional clusters) to replicate the primary Redis cluster across other AWS regions.

1. Navigate to Cloud Services → Databases → ElastiCache → Global Datastores.

2. Select the Regional Clusters tab.

3. Click Add. The Add Secondary Cluster pane displays.

1. Click Create to provision the secondary cluster.

Viewing Cluster Details

To view cluster details, including connection endpoints for a Global Datastore:

1. Navigate to Cloud Services → Database → ElastiCache → Global Datastores.

2. Select the name of the Global Datastore.

3. Select the Regional Clusters tab. A list of clusters in the Global Datastore displays.

4. Click the name of the cluster you want to view details for.

Removing Clusters

To remove a cluster from a Global Datastore:

1. Navigate to Cloud Services → Database → ElastiCache → Global Datastores.

2. Select the name of the Global Datastore.

3. Select the Regional Clusters tab

4. Click the menu icon () in the row of the cluster you want to remove.

Troubleshooting Redis Connection Issues in AWS

When a Redis instance in an AWS environment is experiencing connection issues, ensure the Security Group (SG) configuration allows VPN traffic to port 6379. Then, using the nc command, verify the Redis instance's accessibility.

If you encounter local DNS resolution problems, consider changing your DNS provider or connecting directly using the Redis instance's IP address, which can be obtained via the dig command.

For persistent DNS issues, resetting your router or using external DNS query tools may help. If other troubleshooting steps fail, exploring can offer additional insights.