Cluster
Provides a Redshift Cluster Resource.
NOTE: A Redshift cluster's default IAM role can be managed both by this resource's
default_iam_role_arnargument and theaws.redshift.ClusterIamRolesresource'sdefault_iam_role_arnargument. Do not configure different values for both arguments. Doing so will cause a conflict of default IAM roles.
Example Usage
package generated_program;
import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.aws.redshift.Cluster;
import com.pulumi.aws.redshift.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()
.clusterIdentifier("tf-redshift-cluster")
.clusterType("single-node")
.databaseName("mydb")
.masterPassword("Mustbe8characters")
.masterUsername("exampleuser")
.nodeType("dc1.large")
.build());
}
}Import
Using pulumi import, import Redshift Clusters using the cluster_identifier. For example:
$ pulumi import aws:redshift/cluster:Cluster myprodcluster tf-redshift-cluster-12345Properties
The EC2 Availability Zone (AZ) in which you want Amazon Redshift to provision the cluster. For example, if you have several EC2 instances running in a specific Availability Zone, then you might want the cluster to be provisioned in the same zone in order to decrease network latency. Can only be changed if availability_zone_relocation_enabled is true.
The name of the maintenance track for the restored cluster. When you take a snapshot, the snapshot inherits the MaintenanceTrack value from the cluster. The snapshot might be on a different track than the cluster that was the source for the snapshot. For example, suppose that you take a snapshot of a cluster that is on the current track and then change the cluster to be on the trailing track. In this case, the snapshot and the source cluster are on different tracks. Default value is current.
The port number on which the cluster accepts incoming connections. Valid values are between 1115 and 65535. The cluster is accessible only via the JDBC and ODBC connection strings. Part of the connection string requires the port on which the cluster will listen for incoming connections. Default port is 5439.