Cluster
Provides a MemoryDB Cluster. More information about MemoryDB can be found in the Developer Guide.
Example Usage
package generated_program;
import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.aws.memorydb.Cluster;
import com.pulumi.aws.memorydb.ClusterArgs;
import java.util.List;
import java.util.ArrayList;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;
public class App {
public static void main(String[] args) {
Pulumi.run(App::stack);
}
public static void stack(Context ctx) {
var example = new Cluster("example", ClusterArgs.builder()
.aclName("open-access")
.nodeType("db.t4g.small")
.numShards(2)
.securityGroupIds(aws_security_group.example().id())
.snapshotRetentionLimit(7)
.subnetGroupName(aws_memorydb_subnet_group.example().id())
.build());
}
}Import
Use the name to import a cluster. For example
$ pulumi import aws:memorydb/cluster:Cluster example my-clusterProperties
When set to true, the cluster will automatically receive minor engine version upgrades after launch. Defaults to true.
Enables data tiering. This option is not supported by all instance types. For more information, see Data tiering.
Description for the cluster.
Patch version number of the Redis engine used by the cluster.
Version number of the Redis engine to be used for the cluster. Downgrades are not supported.
Name of the final cluster snapshot to be created when this resource is deleted. If omitted, no final snapshot will be made.
Specifies the weekly time range during which maintenance on the cluster is performed. Specify as a range in the format ddd:hh24:mi-ddd:hh24:mi (24H Clock UTC). The minimum maintenance window is a 60 minute period. Example: sun:23:00-mon:01:30.
Creates a unique name beginning with the specified prefix. Conflicts with name.
The compute and memory capacity of the nodes in the cluster. See AWS documentation on supported node types as well as vertical scaling. The following arguments are optional:
The number of replicas to apply to each shard, up to a maximum of 5. Defaults to 1 (i.e. 2 nodes per shard).
The name of the parameter group associated with the cluster.
Set of VPC Security Group ID-s to associate with this cluster.
Set of shards in this cluster.
List of ARN-s that uniquely identify RDB snapshot files stored in S3. The snapshot files will be used to populate the new cluster. Object names in the ARN-s cannot contain any commas.
The name of a snapshot from which to restore data into the new cluster.
The number of days for which MemoryDB retains automatic snapshots before deleting them. When set to 0, automatic backups are disabled. Defaults to 0.
The daily time range (in UTC) during which MemoryDB begins taking a daily snapshot of your shard. Example: 05:00-09:00.
ARN of the SNS topic to which cluster notifications are sent.
The name of the subnet group to be used for the cluster. Defaults to a subnet group consisting of default VPC subnets.
A flag to enable in-transit encryption on the cluster. When set to false, the acl_name must be open-access. Defaults to true.