

Ada lebih banyak contoh AWS SDK yang tersedia di repo Contoh [SDK AWS Doc](https://github.com/awsdocs/aws-doc-sdk-examples). GitHub 

Terjemahan disediakan oleh mesin penerjemah. Jika konten terjemahan yang diberikan bertentangan dengan versi bahasa Inggris aslinya, utamakan versi bahasa Inggris.

# Contoh Amazon Redshift menggunakan AWS CLI
<a name="cli_2_redshift_code_examples"></a>

Contoh kode berikut menunjukkan cara melakukan tindakan dan mengimplementasikan skenario umum dengan menggunakan AWS Command Line Interface with Amazon Redshift.

*Tindakan* merupakan kutipan kode dari program yang lebih besar dan harus dijalankan dalam konteks. Sementara tindakan menunjukkan cara memanggil fungsi layanan individual, Anda dapat melihat tindakan dalam konteks dalam skenario terkait.

Setiap contoh menyertakan tautan ke kode sumber lengkap, di mana Anda dapat menemukan instruksi tentang cara mengatur dan menjalankan kode dalam konteks.

**Topics**
+ [Tindakan](#actions)

## Tindakan
<a name="actions"></a>

### `accept-reserved-node-exchange`
<a name="redshift_AcceptReservedNodeExchange_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`accept-reserved-node-exchange`.

**AWS CLI**  
**Untuk menerima pertukaran node cadangan**  
`accept-reserved-node-exchange`Contoh berikut menerima pertukaran node DC1 reserved untuk node DC2 reserved.  

```
aws redshift accept-reserved-node-exchange /
    --reserved-node-id 12345678-12ab-12a1-1a2a-12ab-12a12EXAMPLE /
    --target-reserved-node-offering-id 12345678-12ab-12a1-1a2a-12ab-12a12EXAMPLE
```
Output:  

```
{
    "ExchangedReservedNode": {
        "ReservedNodeId": "12345678-12ab-12a1-1a2a-12ab-12a12EXAMPLE",
        "ReservedNodeOfferingId": "12345678-12ab-12a1-1a2a-12ab-12a12EXAMPLE",
        "NodeType": "dc2.large",
        "StartTime": "2019-12-06T21:17:26Z",
        "Duration": 31536000,
        "FixedPrice": 0.0,
        "UsagePrice": 0.0,
        "CurrencyCode": "USD",
        "NodeCount": 1,
        "State": "exchanging",
        "OfferingType": "All Upfront",
        "RecurringCharges": [
            {
                "RecurringChargeAmount": 0.0,
                "RecurringChargeFrequency": "Hourly"
            }
        ],
        "ReservedNodeOfferingType": "Regular"
    }
}
```
Untuk informasi selengkapnya, lihat [Memutakhirkan Node Cadangan Dengan AWS CLI](https://docs.aws.amazon.com/redshift/latest/mgmt/purchase-reserved-node-offering-console.html) di Panduan Manajemen Cluster *Amazon Redshift*.  
+  Untuk detail API, lihat [AcceptReservedNodeExchange](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/accept-reserved-node-exchange.html)di *Referensi AWS CLI Perintah*. 

### `authorize-cluster-security-group-ingress`
<a name="redshift_AuthorizeClusterSecurityGroupIngress_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`authorize-cluster-security-group-ingress`.

**AWS CLI**  
Mengotorisasi Akses ke GroupThis contoh Keamanan EC2 mengotorisasi akses ke grup keamanan Amazon EC2 bernama.Perintah:  

```
aws redshift authorize-cluster-security-group-ingress --cluster-security-group-name mysecuritygroup --ec2-security-group-name myec2securitygroup --ec2-security-group-owner-id 123445677890
```
Mengotorisasi Akses ke rentang CIDRContoh ini mengotorisasi akses ke rentang CIDR.Command:  

```
aws redshift authorize-cluster-security-group-ingress --cluster-security-group-name mysecuritygroup --cidrip 192.168.100.100/32
```
+  Untuk detail API, lihat [AuthorizeClusterSecurityGroupIngress](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/authorize-cluster-security-group-ingress.html)di *Referensi AWS CLI Perintah*. 

### `authorize-snapshot-access`
<a name="redshift_AuthorizeSnapshotAccess_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`authorize-snapshot-access`.

**AWS CLI**  
Otorisasi AWS Akun untuk Memulihkan SnapshotThis contoh mengotorisasi AWS akun `444455556666` untuk memulihkan snapshot. `my-snapshot-id` Secara default, output dalam format JSON.Command:  

```
aws redshift authorize-snapshot-access --snapshot-id my-snapshot-id --account-with-restore-access 444455556666
```
Hasil:  

```
{
   "Snapshot": {
      "Status": "available",
      "SnapshotCreateTime": "2013-07-17T22:04:18.947Z",
      "EstimatedSecondsToCompletion": 0,
      "AvailabilityZone": "us-east-1a",
      "ClusterVersion": "1.0",
      "MasterUsername": "adminuser",
      "Encrypted": false,
      "OwnerAccount": "111122223333",
      "BackupProgressInMegabytes": 11.0,
      "ElapsedTimeInSeconds": 0,
      "DBName": "dev",
      "CurrentBackupRateInMegabytesPerSecond: 0.1534,
      "ClusterCreateTime": "2013-01-22T21:59:29.559Z",
      "ActualIncrementalBackupSizeInMegabytes"; 11.0,
      "SnapshotType": "manual",
      "NodeType": "dw.hs1.xlarge",
      "ClusterIdentifier": "mycluster",
      "TotalBackupSizeInMegabytes": 20.0,
      "Port": 5439,
      "NumberOfNodes": 2,
      "SnapshotIdentifier": "my-snapshot-id"
   }
}
```
+  Untuk detail API, lihat [AuthorizeSnapshotAccess](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/authorize-snapshot-access.html)di *Referensi AWS CLI Perintah*. 

### `batch-delete-cluster-snapshots`
<a name="redshift_BatchDeleteClusterSnapshots_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`batch-delete-cluster-snapshots`.

**AWS CLI**  
**Untuk menghapus satu set snapshot cluster**  
`batch-delete-cluster-snapshots`Contoh berikut menghapus satu set snapshot cluster manual.  

```
aws redshift batch-delete-cluster-snapshots \
        --identifiers SnapshotIdentifier=mycluster-2019-11-06-14-12 SnapshotIdentifier=mycluster-2019-11-06-14-20
```
Output:  

```
{
    "Resources": [
        "mycluster-2019-11-06-14-12",
        "mycluster-2019-11-06-14-20"
    ]
}
```
Untuk informasi selengkapnya, lihat [Snapshot Amazon Redshift](https://docs.aws.amazon.com/redshift/latest/mgmt/working-with-snapshots.html) di Panduan Manajemen Cluster *Amazon Redshift*.  
+  Untuk detail API, lihat [BatchDeleteClusterSnapshots](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/batch-delete-cluster-snapshots.html)di *Referensi AWS CLI Perintah*. 

### `batch-modify-cluster-snapshots`
<a name="redshift_BatchModifyClusterSnapshots_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`batch-modify-cluster-snapshots`.

**AWS CLI**  
**Untuk memodifikasi satu set snapshot cluster**  
`batch-modify-cluster-snapshots`Contoh berikut memodifikasi pengaturan untuk satu set snapshot cluster.  

```
aws redshift batch-modify-cluster-snapshots \
    --snapshot-identifier-list mycluster-2019-11-06-16-31 mycluster-2019-11-06-16-32 \
    --manual-snapshot-retention-period 30
```
Output:  

```
{
    "Resources": [
        "mycluster-2019-11-06-16-31",
        "mycluster-2019-11-06-16-32"
    ],
    "Errors": [],
    "ResponseMetadata": {
        "RequestId": "12345678-12ab-12a1-1a2a-12ab-12a12EXAMPLE",
        "HTTPStatusCode": 200,
        "HTTPHeaders": {
                "x-amzn-requestid": "12345678-12ab-12a1-1a2a-12ab-12a12EXAMPLE,
                "content-type": "text/xml",
                "content-length": "480",
                "date": "Sat, 07 Dec 2019 00:36:09 GMT",
                "connection": "keep-alive"
        },
        "RetryAttempts": 0
    }
}
```
Untuk informasi selengkapnya, lihat [Snapshot Amazon Redshift](https://docs.aws.amazon.com/redshift/latest/mgmt/working-with-snapshots.html) di Panduan Manajemen Cluster *Amazon Redshift*.  
+  Untuk detail API, lihat [BatchModifyClusterSnapshots](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/batch-modify-cluster-snapshots.html)di *Referensi AWS CLI Perintah*. 

### `cancel-resize`
<a name="redshift_CancelResize_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`cancel-resize`.

**AWS CLI**  
**Untuk membatalkan pengubahan ukuran klaster**  
`cancel-resize`Contoh berikut membatalkan operasi pengubahan ukuran klasik untuk sebuah cluster.  

```
aws redshift cancel-resize \
    --cluster-identifier mycluster
```
Output:  

```
{
    "TargetNodeType": "dc2.large",
    "TargetNumberOfNodes": 2,
    "TargetClusterType": "multi-node",
    "Status": "CANCELLING",
    "ResizeType": "ClassicResize",
    "TargetEncryptionType": "NONE"
}
```
Untuk informasi selengkapnya, lihat [Mengubah Ukuran Cluster di Amazon Redshift di](https://docs.aws.amazon.com/redshift/latest/mgmt/rs-resize-tutorial.html) Panduan Manajemen Cluster Amazon *Redshift*.  
+  Untuk detail API, lihat [CancelResize](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/cancel-resize.html)di *Referensi AWS CLI Perintah*. 

### `copy-cluster-snapshot`
<a name="redshift_CopyClusterSnapshot_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`copy-cluster-snapshot`.

**AWS CLI**  
Dapatkan Deskripsi Semua Cluster VersionsThis contoh mengembalikan deskripsi semua versi cluster. Secara default, output dalam format JSON.Command:  

```
aws redshift copy-cluster-snapshot --source-snapshot-identifier cm:examplecluster-2013-01-22-19-27-58 --target-snapshot-identifier my-saved-snapshot-copy
```
Hasil:  

```
{
   "Snapshot": {
      "Status": "available",
      "SnapshotCreateTime": "2013-01-22T19:27:58.931Z",
      "AvailabilityZone": "us-east-1c",
      "ClusterVersion": "1.0",
      "MasterUsername": "adminuser",
      "DBName": "dev",
      "ClusterCreateTime": "2013-01-22T19:23:59.368Z",
      "SnapshotType": "manual",
      "NodeType": "dw.hs1.xlarge",
      "ClusterIdentifier": "examplecluster",
      "Port": 5439,
      "NumberOfNodes": "2",
      "SnapshotIdentifier": "my-saved-snapshot-copy"
   },
   "ResponseMetadata": {
      "RequestId": "3b279691-64e3-11e2-bec0-17624ad140dd"
   }
}
```
+  Untuk detail API, lihat [CopyClusterSnapshot](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/copy-cluster-snapshot.html)di *Referensi AWS CLI Perintah*. 

### `create-cluster-parameter-group`
<a name="redshift_CreateClusterParameterGroup_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`create-cluster-parameter-group`.

**AWS CLI**  
Buat GroupThis contoh Parameter Cluster membuat parameter cluster baru Group.Command:  

```
aws redshift create-cluster-parameter-group --parameter-group-name myclusterparametergroup --parameter-group-family redshift-1.0 --description "My first cluster parameter group"
```
Hasil:  

```
{
   "ClusterParameterGroup": {
      "ParameterGroupFamily": "redshift-1.0",
      "Description": "My first cluster parameter group",
      "ParameterGroupName": "myclusterparametergroup"
   },
   "ResponseMetadata": {
      "RequestId": "739448f0-64cc-11e2-8f7d-3b939af52818"
   }
}
```
+  Untuk detail API, lihat [CreateClusterParameterGroup](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/create-cluster-parameter-group.html)di *Referensi AWS CLI Perintah*. 

### `create-cluster-security-group`
<a name="redshift_CreateClusterSecurityGroup_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`create-cluster-security-group`.

**AWS CLI**  
Membuat GroupThis contoh Keamanan Cluster membuat grup keamanan klaster baru. Secara default, output dalam format JSON.Command:  

```
aws redshift create-cluster-security-group --cluster-security-group-name mysecuritygroup --description "This is my cluster security group"
```
Hasil:  

```
{
   "create_cluster_security_group_response": {
      "create_cluster_security_group_result": {
         "cluster_security_group": {
            "description": "This is my cluster security group",
            "owner_id": "300454760768",
            "cluster_security_group_name": "mysecuritygroup",
            "ec2_security_groups": \[],
            "ip_ranges": \[]
         }
      },
      "response_metadata": {
         "request_id": "5df486a0-343a-11e2-b0d8-d15d0ef48549"
      }
   }
}
```
Anda juga dapat memperoleh informasi yang sama dalam format teks menggunakan `--output text` option.Command:  
`--output text`Option.command:  
 Option.command:  

```
aws redshift create-cluster-security-group --cluster-security-group-name mysecuritygroup --description "This is my cluster security group" --output text
```
Hasil:  

```
This is my cluster security group   300454760768    mysecuritygroup
a0c0bfab-343a-11e2-95d2-c3dc9fe8ab57
```
+  Untuk detail API, lihat [CreateClusterSecurityGroup](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/create-cluster-security-group.html)di *Referensi AWS CLI Perintah*. 

### `create-cluster-snapshot`
<a name="redshift_CreateClusterSnapshot_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`create-cluster-snapshot`.

**AWS CLI**  
Buat SnapshotThis contoh Cluster membuat snapshot cluster baru. Secara default, output dalam format JSON.Command:  

```
aws redshift create-cluster-snapshot --cluster-identifier mycluster --snapshot-identifier my-snapshot-id
```
Hasil:  

```
{
   "Snapshot": {
      "Status": "creating",
      "SnapshotCreateTime": "2013-01-22T22:20:33.548Z",
      "AvailabilityZone": "us-east-1a",
      "ClusterVersion": "1.0",
      "MasterUsername": "adminuser",
      "DBName": "dev",
      "ClusterCreateTime": "2013-01-22T21:59:29.559Z",
      "SnapshotType": "manual",
      "NodeType": "dw.hs1.xlarge",
      "ClusterIdentifier": "mycluster",
      "Port": 5439,
      "NumberOfNodes": "2",
      "SnapshotIdentifier": "my-snapshot-id"
   },
   "ResponseMetadata": {
      "RequestId": "f024d1a5-64e1-11e2-88c5-53eb05787dfb"
   }
}
```
+  Untuk detail API, lihat [CreateClusterSnapshot](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/create-cluster-snapshot.html)di *Referensi AWS CLI Perintah*. 

### `create-cluster-subnet-group`
<a name="redshift_CreateClusterSubnetGroup_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`create-cluster-subnet-group`.

**AWS CLI**  
Buat GroupThis contoh Cluster Subnet membuat cluster subnet group.Command baru:  

```
aws redshift create-cluster-subnet-group --cluster-subnet-group-name mysubnetgroup  --description "My subnet group" --subnet-ids subnet-763fdd1c
```
Hasil:  

```
{
   "ClusterSubnetGroup": {
      "Subnets": [
         {
            "SubnetStatus": "Active",
            "SubnetIdentifier": "subnet-763fdd1c",
            "SubnetAvailabilityZone": {
               "Name": "us-east-1a"
            }
         } ],
      "VpcId": "vpc-7e3fdd14",
      "SubnetGroupStatus": "Complete",
      "Description": "My subnet group",
      "ClusterSubnetGroupName": "mysubnetgroup"
   },
   "ResponseMetadata": {
      "RequestId": "500b8ce2-698f-11e2-9790-fd67517fb6fd"
   }
}
```
+  Untuk detail API, lihat [CreateClusterSubnetGroup](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/create-cluster-subnet-group.html)di *Referensi AWS CLI Perintah*. 

### `create-cluster`
<a name="redshift_CreateCluster_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`create-cluster`.

**AWS CLI**  
Buat Cluster dengan ParametersThis contoh Minimal membuat cluster dengan set minimal parameter. Secara default, output dalam format JSON.Command:  

```
aws redshift create-cluster --node-type dw.hs1.xlarge --number-of-nodes 2 --master-username adminuser --master-user-password TopSecret1 --cluster-identifier mycluster
```
Hasil:  

```
{
   "Cluster": {
      "NodeType": "dw.hs1.xlarge",
      "ClusterVersion": "1.0",
      "PubliclyAccessible": "true",
      "MasterUsername": "adminuser",
      "ClusterParameterGroups": [
         {
            "ParameterApplyStatus": "in-sync",
            "ParameterGroupName": "default.redshift-1.0"
         } ],
      "ClusterSecurityGroups": [
         {
            "Status": "active",
            "ClusterSecurityGroupName": "default"
         } ],
      "AllowVersionUpgrade": true,
      "VpcSecurityGroups": \[],
      "PreferredMaintenanceWindow": "sat:03:30-sat:04:00",
      "AutomatedSnapshotRetentionPeriod": 1,
      "ClusterStatus": "creating",
      "ClusterIdentifier": "mycluster",
      "DBName": "dev",
      "NumberOfNodes": 2,
      "PendingModifiedValues": {
         "MasterUserPassword": "\****"
      }
   },
   "ResponseMetadata": {
      "RequestId": "7cf4bcfc-64dd-11e2-bea9-49e0ce183f07"
   }
}
```
+  Untuk detail API, lihat [CreateCluster](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/create-cluster.html)di *Referensi AWS CLI Perintah*. 

### `create-event-subscription`
<a name="redshift_CreateEventSubscription_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`create-event-subscription`.

**AWS CLI**  
**Untuk membuat langganan notifikasi untuk suatu acara**  
`create-event-subscription`Contoh berikut membuat langganan pemberitahuan acara.  

```
aws redshift create-event-subscription \
    --subscription-name mysubscription \
    --sns-topic-arn arn:aws:sns:us-west-2:123456789012:MySNStopic \
    --source-type cluster \
    --source-ids mycluster
```
Output:  

```
{
        "EventSubscription": {
        "CustomerAwsId": "123456789012",
        "CustSubscriptionId": "mysubscription",
        "SnsTopicArn": "arn:aws:sns:us-west-2:123456789012:MySNStopic",
        "Status": "active",
        "SubscriptionCreationTime": "2019-12-09T20:05:19.365Z",
        "SourceType": "cluster",
        "SourceIdsList": [
            "mycluster"
        ],
        "EventCategoriesList": [],
        "Severity": "INFO",
        "Enabled": true,
        "Tags": []
    }
}
```
Untuk informasi selengkapnya, lihat [Berlangganan Pemberitahuan Peristiwa Amazon Redshift](https://docs.aws.amazon.com/redshift/latest/mgmt/working-with-event-notifications.html) di Panduan Manajemen Cluster *Amazon Redshift*.  
+  Untuk detail API, lihat [CreateEventSubscription](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/create-event-subscription.html)di *Referensi AWS CLI Perintah*. 

### `create-hsm-client-certificate`
<a name="redshift_CreateHsmClientCertificate_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`create-hsm-client-certificate`.

**AWS CLI**  
**Untuk membuat sertifikat klien HSM**  
`create-hsm-client-certificate`Contoh berikut menghasilkan sertifikat klien HSM yang dapat digunakan cluster untuk terhubung ke HSM.  

```
aws redshift create-hsm-client-certificate \
    --hsm-client-certificate-identifier myhsmclientcert
```
Output:  

```
{
    "HsmClientCertificate": {
        "HsmClientCertificateIdentifier": "myhsmclientcert",
        "HsmClientCertificatePublicKey": "-----BEGIN CERTIFICATE-----
        MIICiEXAMPLECQD6m7oRw0uXOjANBgkqhkiG9w0BAQUFADCBiDELMAkGA1UEBhMC
        VVMxCzAJBgNVBAgTEXAMPLEwDgYDVQQHEwdTZWF0dGxlMQ8wDQYDVQQKEwZBbWF6
        b24xFDASBgNVBAsTC0lBTSBDb25EXAMPLEIwEAYDVQQDEwlUZXN0Q2lsYWMxHzAd
        BgkqhkiG9w0BCQEWEG5vb25lQGFtYXpvbi5jb2EXAMPLETEwNDI1MjA0NTIxWhcN
        MTIwNDI0MjA0NTIxWjCBiDELMAkGA1UEBhMCVVMxCzAJBgNVBEXAMPLEMRAwDgYD
        EXAMPLETZWF0dGxlMQ8wDQYDVQQKEwZBbWF6b24xFDASBgNVBAsTC0lBTSBDb25z
        b2xlMRIwEAEXAMPLEwlUZXN0Q2lsYWMxHzAdBgkqhkiG9w0BCQEWEG5vb25lQGFt
        YXpvbi5jb20wgZ8wDQYJKEXAMPLEAQEBBQADgY0AMIGJAoGBAMaK0dn+a4GmWIWJ
        21uUSfwfEvySWtC2XADZ4nB+BLYgVIk6EXAMPLE3G93vUEIO3IyNoH/f0wYK8m9T
        rDHudUZg3qX4waLG5M43q7Wgc/MbQITxOUSQv7c7ugEXAMPLEzZswY6786m86gpE
        Ibb3OhjZnzcvQAaRHhdlQWIMm2nrAgMBAAEwDQYJKoZIhvcNAQEEXAMPLEEAtCu4
        nUhVVxYUEXAMPLEh8Mg9q6q+auNKyExzyLwaxlAoo7TJHidbtS4J5iNmZgXL0Fkb
        FFBjvSfpJIlJ00zbhNYS5f6GEXAMPLEl0ZxBHjJnyp378OD8uTs7fLvjx79LjSTb
        NYiytVbZPQUQ5Yaxu2jXnimvw3rEXAMPLE=-----END CERTIFICATE-----\n",
    "Tags": []
    }
}
```
Untuk informasi selengkapnya, lihat [Referensi Izin API Amazon Redshift di Panduan Manajemen](https://docs.aws.amazon.com/redshift/latest/mgmt/redshift-policy-resources.resource-permissions.html) Cluster *Amazon Redshift*.  
+  Untuk detail API, lihat [CreateHsmClientCertificate](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/create-hsm-client-certificate.html)di *Referensi AWS CLI Perintah*. 

### `create-hsm-configuration`
<a name="redshift_CreateHsmConfiguration_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`create-hsm-configuration`.

**AWS CLI**  
**Untuk membuat konfigurasi HSM**  
`create-hsm-configuration`Contoh berikut membuat konfigurasi HSM tertentu yang berisi informasi yang diperlukan oleh cluster untuk menyimpan dan menggunakan kunci enkripsi database dalam modul keamanan perangkat keras (HSM).  

```
aws redshift create-hsm-configuration /
    --hsm-configuration-identifier myhsmconnection
    --description "My HSM connection"
    --hsm-ip-address 192.0.2.09
    --hsm-partition-name myhsmpartition /
    --hsm-partition-password A1b2c3d4 /
    --hsm-server-public-certificate myhsmclientcert
```
Output:  

```
{
    "HsmConfiguration": {
        "HsmConfigurationIdentifier": "myhsmconnection",
        "Description": "My HSM connection",
        "HsmIpAddress": "192.0.2.09",
        "HsmPartitionName": "myhsmpartition",
        "Tags": []
    }
}
```
+  Untuk detail API, lihat [CreateHsmConfiguration](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/create-hsm-configuration.html)di *Referensi AWS CLI Perintah*. 

### `create-snapshot-copy-grant`
<a name="redshift_CreateSnapshotCopyGrant_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`create-snapshot-copy-grant`.

**AWS CLI**  
**Untuk membuat hibah salinan snapshot**  
`create-snapshot-copy-grant`Contoh berikut membuat hibah salinan snapshot dan mengenkripsi snapshot yang disalin di Wilayah tujuan. AWS   

```
aws redshift create-snapshot-copy-grant \
    --snapshot-copy-grant-name mysnapshotcopygrantname
```
Output:  

```
{
    "SnapshotCopyGrant": {
        "SnapshotCopyGrantName": "mysnapshotcopygrantname",
        "KmsKeyId": "arn:aws:kms:us-west-2:123456789012:key/bPxRfih3yCo8nvbEXAMPLEKEY",
        "Tags": []
    }
}
```
Untuk informasi selengkapnya, lihat [Enkripsi Database Amazon Redshift](https://docs.aws.amazon.com/redshift/latest/mgmt/working-with-db-encryption.html) di Panduan Manajemen *Cluster Amazon Redshift*.  
+  Untuk detail API, lihat [CreateSnapshotCopyGrant](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/create-snapshot-copy-grant.html)di *Referensi AWS CLI Perintah*. 

### `create-snapshot-schedule`
<a name="redshift_CreateSnapshotSchedule_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`create-snapshot-schedule`.

**AWS CLI**  
**Untuk membuat jadwal snapshot**  
`create-snapshot-schedule`Contoh berikut membuat jadwal snapshot dengan deskripsi yang ditentukan dan tingkat setiap 12 jam.  

```
aws redshift create-snapshot-schedule \
    --schedule-definitions "rate(12 hours)" \
    --schedule-identifier mysnapshotschedule \
    --schedule-description "My schedule description"
```
Output:  

```
{
    "ScheduleDefinitions": [
        "rate(12 hours)"
    ],
    "ScheduleIdentifier": "mysnapshotschedule",
    "ScheduleDescription": "My schedule description",
    "Tags": []
}
```
Untuk informasi selengkapnya, lihat [Jadwal Snapshot Otomatis di Panduan](https://docs.aws.amazon.com/redshift/latest/mgmt/working-with-snapshots.html#automated-snapshot-schedules) Manajemen *Cluster Amazon Redshift*.  
+  Untuk detail API, lihat [CreateSnapshotSchedule](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/create-snapshot-schedule.html)di *Referensi AWS CLI Perintah*. 

### `create-tags`
<a name="redshift_CreateTags_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`create-tags`.

**AWS CLI**  
**Untuk membuat tag untuk sebuah cluster**  
`create-tags`Contoh berikut menambahkan key/value pasangan tag yang ditentukan ke cluster tertentu.  

```
aws redshift create-tags \
    --resource-name arn:aws:redshift:us-west-2:123456789012:cluster:mycluster \
    --tags "Key"="mytags","Value"="tag1"
```
Perintah ini tidak menghasilkan output apa pun.  
Untuk informasi selengkapnya, lihat [Menandai Sumber Daya di Amazon](https://docs.aws.amazon.com/redshift/latest/mgmt/amazon-redshift-tagging.html) Redshift di Panduan Manajemen Cluster *Amazon Redshift*.  
+  Untuk detail API, lihat [CreateTags](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/create-tags.html)di *Referensi AWS CLI Perintah*. 

### `delete-cluster-parameter-group`
<a name="redshift_DeleteClusterParameterGroup_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`delete-cluster-parameter-group`.

**AWS CLI**  
Hapus GroupThis contoh Parameter Cluster menghapus parameter cluster Group.Command:  

```
aws redshift delete-cluster-parameter-group --parameter-group-name myclusterparametergroup
```
+  Untuk detail API, lihat [DeleteClusterParameterGroup](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/delete-cluster-parameter-group.html)di *Referensi AWS CLI Perintah*. 

### `delete-cluster-security-group`
<a name="redshift_DeleteClusterSecurityGroup_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`delete-cluster-security-group`.

**AWS CLI**  
Menghapus GroupThis contoh Keamanan Cluster menghapus grup keamanan klaster.Command:  

```
aws redshift delete-cluster-security-group --cluster-security-group-name mysecuritygroup
```
+  Untuk detail API, lihat [DeleteClusterSecurityGroup](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/delete-cluster-security-group.html)di *Referensi AWS CLI Perintah*. 

### `delete-cluster-snapshot`
<a name="redshift_DeleteClusterSnapshot_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`delete-cluster-snapshot`.

**AWS CLI**  
Menghapus SnapshotThis contoh Cluster menghapus cluster Snapshot.Command:  

```
aws redshift delete-cluster-snapshot --snapshot-identifier my-snapshot-id
```
+  Untuk detail API, lihat [DeleteClusterSnapshot](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/delete-cluster-snapshot.html)di *Referensi AWS CLI Perintah*. 

### `delete-cluster-subnet-group`
<a name="redshift_DeleteClusterSubnetGroup_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`delete-cluster-subnet-group`.

**AWS CLI**  
Menghapus GroupThis contoh subnet Cluster menghapus cluster subnet group.Command:  

```
aws redshift delete-cluster-subnet-group --cluster-subnet-group-name mysubnetgroup
```
Hasil:  

```
{
   "ResponseMetadata": {
      "RequestId": "253fbffd-6993-11e2-bc3a-47431073908a"
   }
}
```
+  Untuk detail API, lihat [DeleteClusterSubnetGroup](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/delete-cluster-subnet-group.html)di *Referensi AWS CLI Perintah*. 

### `delete-cluster`
<a name="redshift_DeleteCluster_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`delete-cluster`.

**AWS CLI**  
Hapus Cluster tanpa SnapshotThis contoh Final Cluster menghapus cluster, memaksa penghapusan data sehingga tidak ada snapshot cluster akhir yang dibuat.Command:  

```
aws redshift delete-cluster --cluster-identifier mycluster --skip-final-cluster-snapshot
```
Menghapus Cluster, Mengizinkan SnapshotThis contoh Final Cluster menghapus klaster, tetapi menentukan snapshot.Command cluster akhir:  

```
aws redshift delete-cluster --cluster-identifier mycluster --final-cluster-snapshot-identifier myfinalsnapshot
```
+  Untuk detail API, lihat [DeleteCluster](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/delete-cluster.html)di *Referensi AWS CLI Perintah*. 

### `delete-event-subscription`
<a name="redshift_DeleteEventSubscription_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`delete-event-subscription`.

**AWS CLI**  
**Untuk menghapus langganan acara**  
`delete-event-subscription`Contoh berikut menghapus langganan pemberitahuan acara yang ditentukan.  

```
aws redshift delete-event-subscription \
    --subscription-name mysubscription
```
Perintah ini tidak menghasilkan output apa pun.  
Untuk informasi selengkapnya, lihat [Berlangganan Pemberitahuan Peristiwa Amazon Redshift](https://docs.aws.amazon.com/redshift/latest/mgmt/working-with-event-notifications.html) di Panduan Manajemen Cluster *Amazon Redshift*.  
+  Untuk detail API, lihat [DeleteEventSubscription](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/delete-event-subscription.html)di *Referensi AWS CLI Perintah*. 

### `delete-hsm-client-certificate`
<a name="redshift_DeleteHsmClientCertificate_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`delete-hsm-client-certificate`.

**AWS CLI**  
**Untuk menghapus sertifikat klien HSM**  
`delete-hsm-client-certificate`Contoh berikut menghapus sertifikat klien HSM.  

```
aws redshift delete-hsm-client-certificate \
    --hsm-client-certificate-identifier myhsmclientcert
```
Perintah ini tidak menghasilkan output apa pun.  
Untuk informasi selengkapnya, lihat [Referensi Izin API Amazon Redshift di Panduan Manajemen](https://docs.aws.amazon.com/redshift/latest/mgmt/redshift-policy-resources.resource-permissions.html) Cluster *Amazon Redshift*.  
+  Untuk detail API, lihat [DeleteHsmClientCertificate](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/delete-hsm-client-certificate.html)di *Referensi AWS CLI Perintah*. 

### `delete-hsm-configuration`
<a name="redshift_DeleteHsmConfiguration_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`delete-hsm-configuration`.

**AWS CLI**  
**Untuk menghapus konfigurasi HSM**  
`delete-hsm-configuration`Contoh berikut menghapus konfigurasi HSM yang ditentukan dari akun saat ini AWS .  

```
aws redshift delete-hsm-configuration /
    --hsm-configuration-identifier myhsmconnection
```
Perintah ini tidak menghasilkan output apa pun.  
+  Untuk detail API, lihat [DeleteHsmConfiguration](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/delete-hsm-configuration.html)di *Referensi AWS CLI Perintah*. 

### `delete-scheduled-action`
<a name="redshift_DeleteScheduledAction_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`delete-scheduled-action`.

**AWS CLI**  
**Untuk menghapus tindakan terjadwal**  
`delete-scheduled-action`Contoh berikut menghapus tindakan terjadwal yang ditentukan.  

```
aws redshift delete-scheduled-action \
    --scheduled-action-name myscheduledaction
```
Perintah ini tidak menghasilkan output apa pun.  
+  Untuk detail API, lihat [DeleteScheduledAction](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/delete-scheduled-action.html)di *Referensi AWS CLI Perintah*. 

### `delete-snapshot-copy-grant`
<a name="redshift_DeleteSnapshotCopyGrant_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`delete-snapshot-copy-grant`.

**AWS CLI**  
**Untuk menghapus hibah salinan snapshot**  
`delete-snapshot-copy-grant`Contoh berikut menghapus hibah salinan snapshot yang ditentukan.  

```
aws redshift delete-snapshot-copy-grant \
    --snapshot-copy-grant-name mysnapshotcopygrantname
```
Perintah ini tidak menghasilkan output apa pun.  
Untuk informasi selengkapnya, lihat [Enkripsi Database Amazon Redshift](https://docs.aws.amazon.com/redshift/latest/mgmt/working-with-db-encryption.html) di Panduan Manajemen *Cluster Amazon Redshift*.  
+  Untuk detail API, lihat [DeleteSnapshotCopyGrant](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/delete-snapshot-copy-grant.html)di *Referensi AWS CLI Perintah*. 

### `delete-snapshot-schedule`
<a name="redshift_DeleteSnapshotSchedule_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`delete-snapshot-schedule`.

**AWS CLI**  
**Untuk menghapus jadwal snapshot**  
`delete-snapshot-schedule`Contoh berikut menghapus jadwal snapshot yang ditentukan. Anda harus memisahkan cluster sebelum menghapus jadwal.  

```
aws redshift delete-snapshot-schedule \
    --schedule-identifier mysnapshotschedule
```
Perintah ini tidak menghasilkan output apa pun.  
Untuk informasi selengkapnya, lihat [Jadwal Snapshot Otomatis di Panduan](https://docs.aws.amazon.com/redshift/latest/mgmt/working-with-snapshots.html#automated-snapshot-schedules) Manajemen *Cluster Amazon Redshift*.  
+  Untuk detail API, lihat [DeleteSnapshotSchedule](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/delete-snapshot-schedule.html)di *Referensi AWS CLI Perintah*. 

### `delete-tags`
<a name="redshift_DeleteTags_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`delete-tags`.

**AWS CLI**  
**Untuk menghapus tag dari klaster**  
`delete-tags`Contoh berikut menghapus tag dengan nama kunci yang ditentukan dari cluster yang ditentukan.  

```
aws redshift delete-tags \
    --resource-name arn:aws:redshift:us-west-2:123456789012:cluster:mycluster \
    --tag-keys "clustertagkey" "clustertagvalue"
```
Perintah ini tidak menghasilkan output apa pun.  
Untuk informasi selengkapnya, lihat [Menandai Sumber Daya di Amazon](https://docs.aws.amazon.com/redshift/latest/mgmt/amazon-redshift-tagging.html) Redshift di Panduan Manajemen Cluster *Amazon Redshift*.  
+  Untuk detail API, lihat [DeleteTags](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/delete-tags.html)di *Referensi AWS CLI Perintah*. 

### `describe-account-attributes`
<a name="redshift_DescribeAccountAttributes_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`describe-account-attributes`.

**AWS CLI**  
**Untuk mendeskripsikan atribut AWS akun**  
`describe-account-attributes`Contoh berikut menampilkan atribut yang dilampirkan ke AWS akun panggilan.  

```
aws redshift describe-account-attributes
```
Output:  

```
{
    "AccountAttributes": [
        {
            "AttributeName": "max-defer-maintenance-duration",
            "AttributeValues": [
                {
                    "AttributeValue": "45"
                }
            ]
        }
    ]
}
```
+  Untuk detail API, lihat [DescribeAccountAttributes](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/describe-account-attributes.html)di *Referensi AWS CLI Perintah*. 

### `describe-cluster-db-revisions`
<a name="redshift_DescribeClusterDbRevisions_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`describe-cluster-db-revisions`.

**AWS CLI**  
**Untuk menggambarkan revisi DB untuk sebuah cluster**  
`describe-cluster-db-revisions`Contoh berikut menampilkan rincian dari array `ClusterDbRevision` objek untuk cluster tertentu.  

```
aws redshift describe-cluster-db-revisions \
    --cluster-identifier mycluster
```
Output:  

```
{
    "ClusterDbRevisions": [
        {
            "ClusterIdentifier": "mycluster",
            "CurrentDatabaseRevision": "11420",
            "DatabaseRevisionReleaseDate": "2019-11-22T16:43:49.597Z",
            "RevisionTargets": []
        }
    ]
}
```
+  Untuk detail API, lihat [DescribeClusterDbRevisions](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/describe-cluster-db-revisions.html)di *Referensi AWS CLI Perintah*. 

### `describe-cluster-parameter-groups`
<a name="redshift_DescribeClusterParameterGroups_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`describe-cluster-parameter-groups`.

**AWS CLI**  
Dapatkan Deskripsi All Cluster Parameter GroupsThis contoh mengembalikan deskripsi semua kelompok parameter cluster untuk akun, dengan header kolom. Secara default, output dalam format JSON.Command:  

```
aws redshift describe-cluster-parameter-groups
```
Hasil:  

```
{
   "ParameterGroups": [
      {
         "ParameterGroupFamily": "redshift-1.0",
         "Description": "My first cluster parameter group",
         "ParameterGroupName": "myclusterparametergroup"
      } ],
   "ResponseMetadata": {
      "RequestId": "8ceb8f6f-64cc-11e2-bea9-49e0ce183f07"
   }
}
```
Anda juga dapat memperoleh informasi yang sama dalam format teks menggunakan `--output text` option.Command:  
`--output text`Option.command:  
 Option.command:  

```
aws redshift describe-cluster-parameter-groups --output text
```
Hasil:  

```
redshift-1.0        My first cluster parameter group        myclusterparametergroup
RESPONSEMETADATA    9e665a36-64cc-11e2-8f7d-3b939af52818
```
+  Untuk detail API, lihat [DescribeClusterParameterGroups](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/describe-cluster-parameter-groups.html)di *Referensi AWS CLI Perintah*. 

### `describe-cluster-parameters`
<a name="redshift_DescribeClusterParameters_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`describe-cluster-parameters`.

**AWS CLI**  
Ambil Parameter untuk GroupThis contoh Parameter Cluster Tertentu mengambil parameter untuk grup parameter bernama. Secara default, output dalam format JSON.Command:  

```
aws redshift describe-cluster-parameters --parameter-group-name myclusterparametergroup
```
Hasil:  

```
{
   "Parameters": [
      {
         "Description": "Sets the display format for date and time values.",
         "DataType": "string",
         "IsModifiable": true,
         "Source": "engine-default",
         "ParameterValue": "ISO, MDY",
         "ParameterName": "datestyle"
      },
      {
         "Description": "Sets the number of digits displayed for floating-point values",
         "DataType": "integer",
         "IsModifiable": true,
         "AllowedValues": "-15-2",
         "Source": "engine-default",
         "ParameterValue": "0",
         "ParameterName": "extra_float_digits"
      },
      (...remaining output omitted...)
   ]
}
```
Anda juga dapat memperoleh informasi yang sama dalam format teks menggunakan `--output text` option.Command:  
`--output text`Option.command:  
 Option.command:  

```
aws redshift describe-cluster-parameters --parameter-group-name myclusterparametergroup --output text
```
Hasil:  

```
RESPONSEMETADATA    cdac40aa-64cc-11e2-9e70-918437dd236d
Sets the display format for date and time values.   string  True    engine-default  ISO, MDY        datestyle
Sets the number of digits displayed for floating-point values       integer True    -15-2   engine-default  0       extra_float_digits
This parameter applies a user-defined label to a group of queries that are run during the same session..    string  True    engine-default  default query_group
require ssl for all databaseconnections     boolean True    true,false      engine-default  false   require_ssl
Sets the schema search order for names that are not schema-qualified.       string  True    engine-default  $user, public   search_path
Aborts any statement that takes over the specified number of milliseconds.  integer True    engine-default  0       statement_timeout
wlm json configuration      string  True    engine-default  \[{"query_concurrency":5}]      wlm_json_configuration
```
+  Untuk detail API, lihat [DescribeClusterParameters](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/describe-cluster-parameters.html)di *Referensi AWS CLI Perintah*. 

### `describe-cluster-security-groups`
<a name="redshift_DescribeClusterSecurityGroups_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`describe-cluster-security-groups`.

**AWS CLI**  
Dapatkan Deskripsi All Cluster Security GroupsThis contoh mengembalikan deskripsi semua grup keamanan klaster untuk akun tersebut. Secara default, output dalam format JSON.Command:  

```
aws redshift describe-cluster-security-groups
```
Hasil:  

```
{
   "ClusterSecurityGroups": [
      {
         "OwnerId": "100447751468",
         "Description": "default",
         "ClusterSecurityGroupName": "default",
         "EC2SecurityGroups": \[],
         "IPRanges": [
            {
               "Status": "authorized",
               "CIDRIP": "0.0.0.0/0"
            }
         ]
      },
      {
         "OwnerId": "100447751468",
         "Description": "This is my cluster security group",
         "ClusterSecurityGroupName": "mysecuritygroup",
         "EC2SecurityGroups": \[],
         "IPRanges": \[]
      },
      (...remaining output omitted...)
   ]
}
```
+  Untuk detail API, lihat [DescribeClusterSecurityGroups](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/describe-cluster-security-groups.html)di *Referensi AWS CLI Perintah*. 

### `describe-cluster-snapshots`
<a name="redshift_DescribeClusterSnapshots_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`describe-cluster-snapshots`.

**AWS CLI**  
Dapatkan Deskripsi Semua Cluster SnapshotsThis contoh mengembalikan deskripsi semua snapshot cluster untuk akun. Secara default, output dalam format JSON.Command:  

```
aws redshift describe-cluster-snapshots
```
Hasil:  

```
{
   "Snapshots": [
      {
         "Status": "available",
         "SnapshotCreateTime": "2013-07-17T22:02:22.852Z",
         "EstimatedSecondsToCompletion": -1,
         "AvailabilityZone": "us-east-1a",
         "ClusterVersion": "1.0",
         "MasterUsername": "adminuser",
         "Encrypted": false,
         "OwnerAccount": "111122223333",
         "BackupProgressInMegabytes": 20.0,
         "ElapsedTimeInSeconds": 0,
         "DBName": "dev",
         "CurrentBackupRateInMegabytesPerSecond: 0.0,
         "ClusterCreateTime": "2013-01-22T21:59:29.559Z",
         "ActualIncrementalBackupSizeInMegabytes"; 20.0
         "SnapshotType": "automated",
         "NodeType": "dw.hs1.xlarge",
         "ClusterIdentifier": "mycluster",
         "Port": 5439,
         "TotalBackupSizeInMegabytes": 20.0,
         "NumberOfNodes": "2",
         "SnapshotIdentifier": "cm:mycluster-2013-01-22-22-04-18"
      },
      {
         "EstimatedSecondsToCompletion": 0,
         "OwnerAccount": "111122223333",
         "CurrentBackupRateInMegabytesPerSecond: 0.1534,
         "ActualIncrementalBackupSizeInMegabytes"; 11.0,
         "NumberOfNodes": "2",
         "Status": "available",
         "ClusterVersion": "1.0",
         "MasterUsername": "adminuser",
         "AccountsWithRestoreAccess": [
            {
               "AccountID": "444455556666"
            } ],
         "TotalBackupSizeInMegabytes": 20.0,
         "DBName": "dev",
         "BackupProgressInMegabytes": 11.0,
         "ClusterCreateTime": "2013-01-22T21:59:29.559Z",
         "ElapsedTimeInSeconds": 0,
         "ClusterIdentifier": "mycluster",
         "SnapshotCreateTime": "2013-07-17T22:04:18.947Z",
         "AvailabilityZone": "us-east-1a",
         "NodeType": "dw.hs1.xlarge",
         "Encrypted": false,
         "SnapshotType": "manual",
         "Port": 5439,
         "SnapshotIdentifier": "my-snapshot-id"
      } ]
   }
   (...remaining output omitted...)
```
+  Untuk detail API, lihat [DescribeClusterSnapshots](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/describe-cluster-snapshots.html)di *Referensi AWS CLI Perintah*. 

### `describe-cluster-subnet-groups`
<a name="redshift_DescribeClusterSubnetGroups_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`describe-cluster-subnet-groups`.

**AWS CLI**  
Dapatkan Deskripsi Semua Cluster Subnet GroupsThis contoh mengembalikan deskripsi dari semua kelompok subnet cluster. Secara default, output dalam format JSON.Command:  

```
aws redshift describe-cluster-subnet-groups
```
Hasil:  

```
{
   "ClusterSubnetGroups": [
      {
         "Subnets": [
            {
               "SubnetStatus": "Active",
               "SubnetIdentifier": "subnet-763fdd1c",
               "SubnetAvailabilityZone": {
                  "Name": "us-east-1a"
               }
            }
         ],
         "VpcId": "vpc-7e3fdd14",
         "SubnetGroupStatus": "Complete",
         "Description": "My subnet group",
         "ClusterSubnetGroupName": "mysubnetgroup"
      }
   ],
   "ResponseMetadata": {
      "RequestId": "37fa8c89-6990-11e2-8f75-ab4018764c77"
   }
}
```
+  Untuk detail API, lihat [DescribeClusterSubnetGroups](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/describe-cluster-subnet-groups.html)di *Referensi AWS CLI Perintah*. 

### `describe-cluster-tracks`
<a name="redshift_DescribeClusterTracks_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`describe-cluster-tracks`.

**AWS CLI**  
**Untuk menggambarkan trek cluster**  
`describe-cluster-tracks`Contoh berikut menampilkan rincian trek pemeliharaan yang tersedia.  

```
aws redshift describe-cluster-tracks \
    --maintenance-track-name current
```
Output:  

```
{
    "MaintenanceTracks": [
        {
            "MaintenanceTrackName": "current",
            "DatabaseVersion": "1.0.11420",
            "UpdateTargets": [
                {
                    "MaintenanceTrackName": "preview_features",
                    "DatabaseVersion": "1.0.11746",
                    "SupportedOperations": [
                        {
                            "OperationName": "restore-from-cluster-snapshot"
                        }
                    ]
                },
                {
                    "MaintenanceTrackName": "trailing",
                    "DatabaseVersion": "1.0.11116",
                    "SupportedOperations": [
                        {
                            "OperationName": "restore-from-cluster-snapshot"
                        },
                        {
                            "OperationName": "modify-cluster"
                        }
                    ]
                }
            ]
        }
    ]
}
```
Untuk informasi selengkapnya, lihat [Memilih Trek Pemeliharaan Cluster](https://docs.aws.amazon.com/redshift/latest/mgmt/working-with-clusters.html#rs-mgmt-maintenance-tracks) di *Panduan Manajemen Cluster Amazon Redshift*.  
+  Untuk detail API, lihat [DescribeClusterTracks](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/describe-cluster-tracks.html)di *Referensi AWS CLI Perintah*. 

### `describe-cluster-versions`
<a name="redshift_DescribeClusterVersions_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`describe-cluster-versions`.

**AWS CLI**  
Dapatkan Deskripsi Semua Cluster VersionsThis contoh mengembalikan deskripsi semua versi cluster. Secara default, output dalam format JSON.Command:  

```
aws redshift describe-cluster-versions
```
Hasil:  

```
{
   "ClusterVersions": [
      {
      "ClusterVersion": "1.0",
      "Description": "Initial release",
      "ClusterParameterGroupFamily": "redshift-1.0"
      } ],
   "ResponseMetadata": {
      "RequestId": "16a53de3-64cc-11e2-bec0-17624ad140dd"
   }
}
```
+  Untuk detail API, lihat [DescribeClusterVersions](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/describe-cluster-versions.html)di *Referensi AWS CLI Perintah*. 

### `describe-clusters`
<a name="redshift_DescribeClusters_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`describe-clusters`.

**AWS CLI**  
Dapatkan Deskripsi Semua ClustersThis contoh mengembalikan deskripsi semua cluster untuk akun. Secara default, output dalam format JSON.Command:  

```
aws redshift describe-clusters
```
Hasil:  

```
{
   "Clusters": [
   {
      "NodeType": "dw.hs1.xlarge",
      "Endpoint": {
         "Port": 5439,
         "Address": "mycluster.coqoarplqhsn.us-east-1.redshift.amazonaws.com"
      },
      "ClusterVersion": "1.0",
      "PubliclyAccessible": "true",
      "MasterUsername": "adminuser",
      "ClusterParameterGroups": [
         {
            "ParameterApplyStatus": "in-sync",
            "ParameterGroupName": "default.redshift-1.0"
         } ],
      "ClusterSecurityGroups": [
         {
            "Status": "active",
            "ClusterSecurityGroupName": "default"
         } ],
      "AllowVersionUpgrade": true,
      "VpcSecurityGroups": \[],
      "AvailabilityZone": "us-east-1a",
      "ClusterCreateTime": "2013-01-22T21:59:29.559Z",
      "PreferredMaintenanceWindow": "sat:03:30-sat:04:00",
      "AutomatedSnapshotRetentionPeriod": 1,
      "ClusterStatus": "available",
      "ClusterIdentifier": "mycluster",
      "DBName": "dev",
      "NumberOfNodes": 2,
      "PendingModifiedValues": {}
   } ],
   "ResponseMetadata": {
      "RequestId": "65b71cac-64df-11e2-8f5b-e90bd6c77476"
   }
}
```
Anda juga dapat memperoleh informasi yang sama dalam format teks menggunakan `--output text` option.Command:  
`--output text`Option.command:  
 Option.command:  

```
aws redshift describe-clusters --output text
```
Hasil:  

```
dw.hs1.xlarge       1.0     true    adminuser       True    us-east-1a      2013-01-22T21:59:29.559Z        sat:03:30-sat:04:00     1       available       mycluster       dev     2
ENDPOINT    5439    mycluster.coqoarplqhsn.us-east-1.redshift.amazonaws.com
in-sync     default.redshift-1.0
active      default
PENDINGMODIFIEDVALUES
RESPONSEMETADATA    934281a8-64df-11e2-b07c-f7fbdd006c67
```
+  Untuk detail API, lihat [DescribeClusters](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/describe-clusters.html)di *Referensi AWS CLI Perintah*. 

### `describe-default-cluster-parameters`
<a name="redshift_DescribeDefaultClusterParameters_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`describe-default-cluster-parameters`.

**AWS CLI**  
Dapatkan Deskripsi ParametersThis contoh Cluster Default mengembalikan deskripsi parameter cluster default untuk `redshift-1.0` keluarga. Secara default, output dalam format JSON.Command:  

```
aws redshift describe-default-cluster-parameters --parameter-group-family redshift-1.0
```
Hasil:  

```
{
   "DefaultClusterParameters": {
   "ParameterGroupFamily": "redshift-1.0",
   "Parameters": [
      {
         "Description": "Sets the display format for date and time values.",
         "DataType": "string",
         "IsModifiable": true,
         "Source": "engine-default",
         "ParameterValue": "ISO, MDY",
         "ParameterName": "datestyle"
      },
      {
         "Description": "Sets the number of digits displayed for floating-point values",
         "DataType": "integer",
         "IsModifiable": true,
         "AllowedValues": "-15-2",
         "Source": "engine-default",
         "ParameterValue": "0",
         "ParameterName": "extra_float_digits"
      },
      (...remaining output omitted...)
      ]
   }
}
```
Untuk melihat daftar keluarga grup parameter yang valid, gunakan `describe-cluster-parameter-groups` perintah.  
`describe-cluster-parameter-groups`perintah.  
 perintah.  
+  Untuk detail API, lihat [DescribeDefaultClusterParameters](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/describe-default-cluster-parameters.html)di *Referensi AWS CLI Perintah*. 

### `describe-event-categories`
<a name="redshift_DescribeEventCategories_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`describe-event-categories`.

**AWS CLI**  
**Untuk mendeskripsikan kategori acara untuk sebuah cluster**  
`describe-event-categories`Contoh berikut menampilkan rincian untuk kategori acara untuk cluster.  

```
aws redshift describe-event-categories \
    --source-type cluster
```
Output:  

```
{
    "EventCategoriesMapList": [
        {
            "SourceType": "cluster",
            "Events": [
                {
                    "EventId": "REDSHIFT-EVENT-2000",
                    "EventCategories": [
                        "management"
                    ],
                    "EventDescription": "Cluster <cluster name> created at <time in UTC>.",
                    "Severity": "INFO"
                },
                {
                    "EventId": "REDSHIFT-EVENT-2001",
                    "EventCategories": [
                        "management"
                    ],
                    "EventDescription": "Cluster <cluster name> deleted at <time in UTC>.",
                    "Severity": "INFO"
                },
                {
                    "EventId": "REDSHIFT-EVENT-3625",
                    "EventCategories": [
                        "monitoring"
                    ],
                    "EventDescription": "The cluster <cluster name> can't be resumed with its previous elastic network interface <ENI id>. We will allocate a new elastic network interface and associate it with the cluster node.",
                    "Severity": "INFO"
                }
            ]
        }
    ]
}
```
+  Untuk detail API, lihat [DescribeEventCategories](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/describe-event-categories.html)di *Referensi AWS CLI Perintah*. 

### `describe-event-subscriptions`
<a name="redshift_DescribeEventSubscriptions_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`describe-event-subscriptions`.

**AWS CLI**  
**Untuk menggambarkan langganan acara**  
`describe-event-subscriptions`Contoh berikut menampilkan langganan pemberitahuan acara untuk langganan yang ditentukan.  

```
aws redshift describe-event-subscriptions \
    --subscription-name mysubscription
```
Output:  

```
{
    "EventSubscriptionsList": [
        {
            "CustomerAwsId": "123456789012",
            "CustSubscriptionId": "mysubscription",
            "SnsTopicArn": "arn:aws:sns:us-west-2:123456789012:MySNStopic",
            "Status": "active",
            "SubscriptionCreationTime": "2019-12-09T21:50:21.332Z",
            "SourceIdsList": [],
            "EventCategoriesList": [
                "management"
            ],
            "Severity": "ERROR",
            "Enabled": true,
            "Tags": []
        }
    ]
}
```
Untuk informasi selengkapnya, lihat [Berlangganan Pemberitahuan Peristiwa Amazon Redshift](https://docs.aws.amazon.com/redshift/latest/mgmt/working-with-event-notifications.html) di Panduan Manajemen Cluster *Amazon Redshift*.  
+  Untuk detail API, lihat [DescribeEventSubscriptions](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/describe-event-subscriptions.html)di *Referensi AWS CLI Perintah*. 

### `describe-events`
<a name="redshift_DescribeEvents_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`describe-events`.

**AWS CLI**  
Jelaskan Semua PeristiwaContoh ini mengembalikan semua peristiwa. Secara default, output dalam format JSON.Command:  

```
aws redshift describe-events
```
Hasil:  

```
{
   "Events": [
      {
      "Date": "2013-01-22T19:17:03.640Z",
      "SourceIdentifier": "myclusterparametergroup",
      "Message": "Cluster parameter group myclusterparametergroup has been created.",
      "SourceType": "cluster-parameter-group"
      } ],
   "ResponseMetadata": {
      "RequestId": "9f056111-64c9-11e2-9390-ff04f2c1e638"
   }
}
```
Anda juga dapat memperoleh informasi yang sama dalam format teks menggunakan `--output text` option.Command:  
`--output text`Option.command:  
 Option.command:  

```
aws redshift describe-events --output text
```
Hasil:  

```
2013-01-22T19:17:03.640Z    myclusterparametergroup Cluster parameter group myclusterparametergroup has been created.       cluster-parameter-group
RESPONSEMETADATA    8e5fe765-64c9-11e2-bce3-e56f52c50e17
```
+  Untuk detail API, lihat [DescribeEvents](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/describe-events.html)di *Referensi AWS CLI Perintah*. 

### `describe-hsm-client-certificates`
<a name="redshift_DescribeHsmClientCertificates_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`describe-hsm-client-certificates`.

**AWS CLI**  
**Untuk menggambarkan sertifikat klien HSM**  
`describe-hsm-client-certificates`Contoh berikut menampilkan rincian untuk sertifikat klien HSM yang ditentukan.  

```
aws redshift describe-hsm-client-certificates \
    --hsm-client-certificate-identifier myhsmclientcert
```
Output:  

```
{
    "HsmClientCertificates": [
        {
        "HsmClientCertificateIdentifier": "myhsmclientcert",
        "HsmClientCertificatePublicKey": "-----BEGIN CERTIFICATE-----\
        EXAMPLECAfICCQD6m7oRw0uXOjANBgkqhkiG9w0BAQUFADCBiDELMAkGA1UEBhMC
        VVMxCzAJBgNVBAEXAMPLERAwDgYDVQQHEwdTZWF0dGxlMQ8wDQYDVQQKEwZBbWF6
        b24xFDASBgNVBAsTC0lBTSBDb25zEXAMPLEwEAYDVQQDEwlUZXN0Q2lsYWMxHzAd
        BgkqhkiG9w0BCQEWEG5vb25lQGFtYXpvbi5jb20wHhEXAMPLEDI1MjA0EXAMPLEN
        EXAMPLE0MjA0NTIxWjCBiDELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAldBMRAwDgYD
        VQQHEwdTZWF0dGEXAMPLEQYDVQQKEwZBbWF6b24xFDASBgNVBAsTC0lBTSBDb25z
        b2xlMRIwEAYDVQQDEwlUZXN0Q2lsEXAMPLEdBgkqhkiG9w0BCQEWEG5vb25lQGFt
        YXpvbi5jb20wgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIEXAMPLEMaK0dn+a4GmWIWJ
        21uUSfwfEvySWtC2XADZ4nB+BLYgVIk60CpiwsZ3G93vUEIO3IyNoH/f0wYK8m9T
        rDHudUZg3qX4waLG5M43q7Wgc/MbQITxOUSQv7c7ugFFDzQGBzZswY67EXAMPLEE
        EXAMPLEZnzcvQAaRHhdlQWIMm2nrAgMBAAEwDQYJKoZIhvcNAQEFBQADgYEAtCu4
        nUhVVxYUntneD9EXAMPLE6q+auNKyExzyLwaxlAoo7TJHidbtS4J5iNmZgXL0Fkb
        FFBjvSfpJIlJ00zbhNYS5f6GuoEDEXAMPLEBHjJnyp378OD8uTs7fLvjx79LjSTb
        NYiytVbZPQUQ5Yaxu2jXnimvw3rEXAMPLE=-----END CERTIFICATE-----\n",
        "Tags": []
        }
    ]
}
```
Untuk informasi selengkapnya, lihat [Referensi Izin API Amazon Redshift di Panduan Manajemen](https://docs.aws.amazon.com/redshift/latest/mgmt/redshift-policy-resources.resource-permissions.html) Cluster *Amazon Redshift*.  
+  Untuk detail API, lihat [DescribeHsmClientCertificates](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/describe-hsm-client-certificates.html)di *Referensi AWS CLI Perintah*. 

### `describe-hsm-configurations`
<a name="redshift_DescribeHsmConfigurations_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`describe-hsm-configurations`.

**AWS CLI**  
**Untuk menggambarkan konfigurasi HSM**  
`describe-hsm-configurations`Contoh berikut menampilkan detail untuk konfigurasi HSM yang tersedia untuk akun panggilan AWS .  

```
aws redshift describe-hsm-configurations /
    --hsm-configuration-identifier myhsmconnection
```
Output:  

```
{
    "HsmConfigurations": [
        {
            "HsmConfigurationIdentifier": "myhsmconnection",
            "Description": "My HSM connection",
            "HsmIpAddress": "192.0.2.09",
            "HsmPartitionName": "myhsmpartition",
            "Tags": []
        }
    ]
}
```
+  Untuk detail API, lihat [DescribeHsmConfigurations](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/describe-hsm-configurations.html)di *Referensi AWS CLI Perintah*. 

### `describe-logging-status`
<a name="redshift_DescribeLoggingStatus_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`describe-logging-status`.

**AWS CLI**  
**Untuk mendeskripsikan status logging untuk sebuah klaster**  
`describe-logging-status`Contoh berikut menampilkan apakah informasi, seperti kueri dan upaya koneksi, sedang dicatat untuk sebuah cluster.  

```
aws redshift describe-logging-status \
    --cluster-identifier mycluster
```
Output:  

```
{
    "LoggingEnabled": false
}
```
Untuk informasi selengkapnya, lihat [Logging Audit Database](https://docs.aws.amazon.com/redshift/latest/mgmt/db-auditing.html) di *Panduan Manajemen Cluster Amazon Redshift*.  
+  Untuk detail API, lihat [DescribeLoggingStatus](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/describe-logging-status.html)di *Referensi AWS CLI Perintah*. 

### `describe-node-configuration-options`
<a name="redshift_DescribeNodeConfigurationOptions_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`describe-node-configuration-options`.

**AWS CLI**  
**Untuk menggambarkan opsi konfigurasi simpul**  
`describe-node-configuration-options`Contoh berikut menampilkan properti konfigurasi node yang mungkin seperti tipe node, jumlah node, dan penggunaan disk untuk snapshot cluster yang ditentukan.  

```
aws redshift describe-node-configuration-options \
    --action-type restore-cluster \
    --snapshot-identifier rs:mycluster-2019-12-09-16-42-43
```
Output:  

```
{
    "NodeConfigurationOptionList": [
        {
            "NodeType": "dc2.large",
            "NumberOfNodes": 2,
            "EstimatedDiskUtilizationPercent": 19.61
        },
        {
            "NodeType": "dc2.large",
            "NumberOfNodes": 4,
            "EstimatedDiskUtilizationPercent": 9.96
        },
        {
            "NodeType": "ds2.xlarge",
            "NumberOfNodes": 2,
            "EstimatedDiskUtilizationPercent": 1.53
        },
        {
            "NodeType": "ds2.xlarge",
            "NumberOfNodes": 4,
            "EstimatedDiskUtilizationPercent": 0.78
        }
    ]
}
```
Untuk informasi selengkapnya, lihat [Membeli Node Cadangan Amazon Redshift di Panduan](https://docs.aws.amazon.com/redshift/latest/mgmt/purchase-reserved-node-instance.html) Manajemen *Cluster Amazon Redshift*.  
+  Untuk detail API, lihat [DescribeNodeConfigurationOptions](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/describe-node-configuration-options.html)di *Referensi AWS CLI Perintah*. 

### `describe-orderable-cluster-options`
<a name="redshift_DescribeOrderableClusterOptions_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`describe-orderable-cluster-options`.

**AWS CLI**  
Menjelaskan Semua OptionsThis contoh Cluster yang Dapat Dipesan mengembalikan deskripsi semua opsi cluster yang dapat dipesan. Secara default, output dalam format JSON.Command:  

```
aws redshift describe-orderable-cluster-options
```
Hasil:  

```
{
   "OrderableClusterOptions": [
      {
         "NodeType": "dw.hs1.8xlarge",
         "AvailabilityZones": [
            { "Name": "us-east-1a" },
            { "Name": "us-east-1b" },
            { "Name": "us-east-1c" } ],
         "ClusterVersion": "1.0",
         "ClusterType": "multi-node"
      },
      {
         "NodeType": "dw.hs1.xlarge",
         "AvailabilityZones": [
            { "Name": "us-east-1a" },
            { "Name": "us-east-1b" },
            { "Name": "us-east-1c" } ],
         "ClusterVersion": "1.0",
         "ClusterType": "multi-node"
      },
      {
      "NodeType": "dw.hs1.xlarge",
      "AvailabilityZones": [
         { "Name": "us-east-1a" },
         { "Name": "us-east-1b" },
         { "Name": "us-east-1c" } ],
      "ClusterVersion": "1.0",
      "ClusterType": "single-node"
      } ],
   "ResponseMetadata": {
      "RequestId": "f6000035-64cb-11e2-9135-ff82df53a51a"
   }
}
```
Anda juga dapat memperoleh informasi yang sama dalam format teks menggunakan `--output text` option.Command:  
`--output text`Option.command:  
 Option.command:  

```
aws redshift describe-orderable-cluster-options --output text
```
Hasil:  

```
dw.hs1.8xlarge      1.0     multi-node
us-east-1a
us-east-1b
us-east-1c
dw.hs1.xlarge       1.0     multi-node
us-east-1a
us-east-1b
us-east-1c
dw.hs1.xlarge       1.0     single-node
us-east-1a
us-east-1b
us-east-1c
RESPONSEMETADATA    e648696b-64cb-11e2-bec0-17624ad140dd
```
+  Untuk detail API, lihat [DescribeOrderableClusterOptions](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/describe-orderable-cluster-options.html)di *Referensi AWS CLI Perintah*. 

### `describe-reserved-node-offerings`
<a name="redshift_DescribeReservedNodeOfferings_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`describe-reserved-node-offerings`.

**AWS CLI**  
Jelaskan OfferingsThis contoh Node Cadangan menunjukkan semua penawaran node cadangan yang tersedia untuk Purchase.command:  

```
aws redshift describe-reserved-node-offerings
```
Hasil:  

```
{
   "ReservedNodeOfferings": [
      {
         "OfferingType": "Heavy Utilization",
         "FixedPrice": "",
         "NodeType": "dw.hs1.xlarge",
         "UsagePrice": "",
         "RecurringCharges": [
            {
               "RecurringChargeAmount": "",
               "RecurringChargeFrequency": "Hourly"
            } ],
         "Duration": 31536000,
         "ReservedNodeOfferingId": "ceb6a579-cf4c-4343-be8b-d832c45ab51c"
      },
      {
         "OfferingType": "Heavy Utilization",
         "FixedPrice": "",
         "NodeType": "dw.hs1.8xlarge",
         "UsagePrice": "",
         "RecurringCharges": [
            {
            "RecurringChargeAmount": "",
            "RecurringChargeFrequency": "Hourly"
            } ],
         "Duration": 31536000,
         "ReservedNodeOfferingId": "e5a2ff3b-352d-4a9c-ad7d-373c4cab5dd2"
      },
      ...remaining output omitted...
   ],
   "ResponseMetadata": {
      "RequestId": "8b1a1a43-75ff-11e2-9666-e142fe91ddd1"
   }
}
```
Jika Anda ingin membeli penawaran node yang dicadangkan, Anda dapat menelepon `purchase-reserved-node-offering` menggunakan valid *ReservedNodeOfferingId*.  
`purchase-reserved-node-offering`menggunakan yang valid *ReservedNodeOfferingId*.  
 menggunakan yang valid *ReservedNodeOfferingId*.  
*ReservedNodeOfferingId*.  
.  
+  Untuk detail API, lihat [DescribeReservedNodeOfferings](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/describe-reserved-node-offerings.html)di *Referensi AWS CLI Perintah*. 

### `describe-reserved-nodes`
<a name="redshift_DescribeReservedNodes_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`describe-reserved-nodes`.

**AWS CLI**  
 NodesThis Contoh Description Reserved menunjukkan penawaran node reserved yang telah dibeli.Command:  

```
aws redshift describe-reserved-nodes
```
Hasil:  

```
{
   "ResponseMetadata": {
      "RequestId": "bc29ce2e-7600-11e2-9949-4b361e7420b7"
   },
   "ReservedNodes": [
      {
         "OfferingType": "Heavy Utilization",
         "FixedPrice": "",
         "NodeType": "dw.hs1.xlarge",
         "ReservedNodeId": "1ba8e2e3-bc01-4d65-b35d-a4a3e931547e",
         "UsagePrice": "",
         "RecurringCharges": [
            {
               "RecurringChargeAmount": "",
               "RecurringChargeFrequency": "Hourly"
            } ],
         "NodeCount": 1,
         "State": "payment-pending",
         "StartTime": "2013-02-13T17:08:39.051Z",
         "Duration": 31536000,
         "ReservedNodeOfferingId": "ceb6a579-cf4c-4343-be8b-d832c45ab51c"
      }
   ]
}
```
+  Untuk detail API, lihat [DescribeReservedNodes](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/describe-reserved-nodes.html)di *Referensi AWS CLI Perintah*. 

### `describe-resize`
<a name="redshift_DescribeResize_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`describe-resize`.

**AWS CLI**  
Jelaskan ResizeThis contoh menggambarkan pengubahan ukuran terbaru dari sebuah cluster. Permintaan itu untuk 3 node tipe `dw.hs1.8xlarge` .Command:  

```
aws redshift describe-resize --cluster-identifier mycluster
```
Hasil:  

```
{
   "Status": "NONE",
   "TargetClusterType": "multi-node",
   "TargetNodeType": "dw.hs1.8xlarge",
   "ResponseMetadata": {
      "RequestId": "9f52b0b4-7733-11e2-aa9b-318b2909bd27"
   },
   "TargetNumberOfNodes": "3"
}
```
+  Untuk detail API, lihat [DescribeResize](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/describe-resize.html)di *Referensi AWS CLI Perintah*. 

### `describe-scheduled-actions`
<a name="redshift_DescribeScheduledActions_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`describe-scheduled-actions`.

**AWS CLI**  
**Untuk menggambarkan tindakan terjadwal**  
`describe-scheduled-actions`Contoh berikut menampilkan detail untuk setiap tindakan yang dijadwalkan saat ini.  

```
aws redshift describe-scheduled-actions
```
Output:  

```
{
    "ScheduledActions": [
        {
            "ScheduledActionName": "resizecluster",
            "TargetAction": {
                "ResizeCluster": {
                    "ClusterIdentifier": "mycluster",
                    "NumberOfNodes": 4,
                    "Classic": false
                }
            },
            "Schedule": "at(2019-12-10T00:07:00)",
            "IamRole": "arn:aws:iam::123456789012:role/myRedshiftRole",
            "State": "ACTIVE",
            "NextInvocations": [
                "2019-12-10T00:07:00Z"
            ]
        }
    ]
}
```
+  Untuk detail API, lihat [DescribeScheduledActions](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/describe-scheduled-actions.html)di *Referensi AWS CLI Perintah*. 

### `describe-snapshot-copy-grants`
<a name="redshift_DescribeSnapshotCopyGrants_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`describe-snapshot-copy-grants`.

**AWS CLI**  
**Untuk menggambarkan hibah salinan snapshot**  
`describe-snapshot-copy-grants`Contoh berikut menampilkan rincian untuk hibah salinan snapshot cluster yang ditentukan.  

```
aws redshift describe-snapshot-copy-grants \
    --snapshot-copy-grant-name mysnapshotcopygrantname
```
Output:  

```
{
    "SnapshotCopyGrants": [
        {
            "SnapshotCopyGrantName": "mysnapshotcopygrantname",
            "KmsKeyId": "arn:aws:kms:us-west-2:123456789012:key/bPxRfih3yCo8nvbEXAMPLEKEY",
            "Tags": []
        }
    ]
}
```
Untuk informasi selengkapnya, lihat [Enkripsi Database Amazon Redshift](https://docs.aws.amazon.com/redshift/latest/mgmt/working-with-db-encryption.html) di Panduan Manajemen *Cluster Amazon Redshift*.  
+  Untuk detail API, lihat [DescribeSnapshotCopyGrants](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/describe-snapshot-copy-grants.html)di *Referensi AWS CLI Perintah*. 

### `describe-snapshot-schedules`
<a name="redshift_DescribeSnapshotSchedules_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`describe-snapshot-schedules`.

**AWS CLI**  
**Untuk menggambarkan jadwal snapshot**  
`describe-snapshot-schedules`Contoh berikut menampilkan rincian untuk jadwal snapshot cluster yang ditentukan.  

```
aws redshift describe-snapshot-schedules \
    --cluster-identifier mycluster \
    --schedule-identifier mysnapshotschedule
```
Output:  

```
{
    "SnapshotSchedules": [
        {
            "ScheduleDefinitions": [
                "rate(12 hours)"
            ],
            "ScheduleIdentifier": "mysnapshotschedule",
            "ScheduleDescription": "My schedule description",
            "Tags": [],
            "AssociatedClusterCount": 1,
            "AssociatedClusters": [
                {
                    "ClusterIdentifier": "mycluster",
                    "ScheduleAssociationState": "ACTIVE"
                }
            ]
        }
    ]
}
```
Untuk informasi selengkapnya, lihat [Jadwal Snapshot Otomatis di Panduan](https://docs.aws.amazon.com/redshift/latest/mgmt/working-with-snapshots.html#automated-snapshot-schedules) Manajemen *Cluster Amazon Redshift*.  
+  Untuk detail API, lihat [DescribeSnapshotSchedules](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/describe-snapshot-schedules.html)di *Referensi AWS CLI Perintah*. 

### `describe-storage`
<a name="redshift_DescribeStorage_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`describe-storage`.

**AWS CLI**  
**Untuk menggambarkan penyimpanan**  
`describe-storage`Contoh berikut menampilkan detail tentang penyimpanan cadangan dan ukuran penyimpanan sementara untuk akun.  

```
aws redshift describe-storage
```
Output:  

```
{
    "TotalBackupSizeInMegaBytes": 193149.0,
    "TotalProvisionedStorageInMegaBytes": 655360.0
}
```
Untuk informasi selengkapnya, lihat [Mengelola Penyimpanan Snapshot](https://docs.aws.amazon.com/redshift/latest/mgmt/working-with-snapshots.html#managing-snapshot-storage) di Panduan Manajemen *Cluster Amazon Redshift*.  
+  Untuk detail API, lihat [DescribeStorage](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/describe-storage.html)di *Referensi AWS CLI Perintah*. 

### `describe-table-restore-status`
<a name="redshift_DescribeTableRestoreStatus_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`describe-table-restore-status`.

**AWS CLI**  
**Untuk menjelaskan status permintaan pemulihan tabel dari snapshot cluster**  
`describe-table-restore-status`Contoh berikut menampilkan rincian untuk permintaan pemulihan tabel yang dibuat untuk cluster tertentu.  

```
aws redshift describe-table-restore-status /
    --cluster-identifier mycluster
```
Output:  

```
{
    "TableRestoreStatusDetails": [
        {
            "TableRestoreRequestId": "z1116630-0e80-46f4-ba86-bd9670411ebd",
            "Status": "IN_PROGRESS",
            "RequestTime": "2019-12-27T18:22:12.257Z",
            "ClusterIdentifier": "mycluster",
            "SnapshotIdentifier": "mysnapshotid",
            "SourceDatabaseName": "dev",
            "SourceSchemaName": "public",
            "SourceTableName": "mytable",
            "TargetDatabaseName": "dev",
            "TargetSchemaName": "public",
            "NewTableName": "mytable-clone"
        }
    ]
}
```
Untuk informasi selengkapnya, lihat [Memulihkan Tabel dari Snapshot di Panduan](https://docs.aws.amazon.com/redshift/latest/mgmt/working-with-snapshots.html#working-with-snapshot-restore-table-from-snapshot) Manajemen *Cluster Amazon Redshift*.  
+  Untuk detail API, lihat [DescribeTableRestoreStatus](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/describe-table-restore-status.html)di *Referensi AWS CLI Perintah*. 

### `describe-tags`
<a name="redshift_DescribeTags_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`describe-tags`.

**AWS CLI**  
**Untuk mendeskripsikan tag**  
`describe-tags`Contoh berikut menampilkan sumber daya cluster tertentu terkait dengan nama tag tertentu dan nilai-nilai.  

```
aws redshift describe-tags \
    --resource-name arn:aws:redshift:us-west-2:123456789012:cluster:mycluster \
    --tag-keys clustertagkey \
    --tag-values clustertagvalue
```
Output:  

```
{
    "TaggedResources": [
                    {
            "Tag": {
                "Key": "clustertagkey",
                "Value": "clustertagvalue"
            },
            "ResourceName": "arn:aws:redshift:us-west-2:123456789012:cluster:mycluster",
            "ResourceType": "cluster"
        }
    ]
}
```
Untuk informasi selengkapnya, lihat [Menandai Sumber Daya di Amazon](https://docs.aws.amazon.com/redshift/latest/mgmt/amazon-redshift-tagging.html) Redshift di Panduan Manajemen Cluster *Amazon Redshift*.  
+  Untuk detail API, lihat [DescribeTags](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/describe-tags.html)di *Referensi AWS CLI Perintah*. 

### `disable-snapshot-copy`
<a name="redshift_DisableSnapshotCopy_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`disable-snapshot-copy`.

**AWS CLI**  
**Untuk menonaktifkan salinan snapshot untuk klaster**  
`disable-snapshot-copy`Contoh berikut menonaktifkan salinan otomatis snapshot untuk cluster yang ditentukan.  

```
aws redshift disable-snapshot-copy \
    --cluster-identifier mycluster
```
Output:  

```
{
    "Cluster": {
        "ClusterIdentifier": "mycluster",
        "NodeType": "dc2.large",
        "ClusterStatus": "available",
        "ClusterAvailabilityStatus": "Available",
        "MasterUsername": "adminuser",
        "DBName": "dev",
        "Endpoint": {
            "Address": "mycluster.cmeaswqeuae.us-west-2.redshift.amazonaws.com",
            "Port": 5439
        },
        "ClusterCreateTime": "2019-12-05T18:44:36.991Z",
        "AutomatedSnapshotRetentionPeriod": 3,
        "ManualSnapshotRetentionPeriod": -1,
        "ClusterSecurityGroups": [],
        "VpcSecurityGroups": [
            {
                "VpcSecurityGroupId": "sh-i9b431cd",
                "Status": "active"
            }
        ],
        "ClusterParameterGroups": [
            {
                "ParameterGroupName": "default.redshift-1.0",
                "ParameterApplyStatus": "in-sync"
            }
        ],
        "ClusterSubnetGroupName": "default",
        "VpcId": "vpc-b1fel7t9",
        "AvailabilityZone": "us-west-2f",
        "PreferredMaintenanceWindow": "sat:16:00-sat:16:30",
        "PendingModifiedValues": {
            "NodeType": "dc2.large",
            "NumberOfNodes": 2,
            "ClusterType": "multi-node"
        },
        "ClusterVersion": "1.0",
        "AllowVersionUpgrade": true,
        "NumberOfNodes": 4,
        "PubliclyAccessible": false,
        "Encrypted": false,
        "Tags": [
            {
                "Key": "mytags",
                "Value": "tag1"
            }
        ],
        "EnhancedVpcRouting": false,
        "IamRoles": [
            {
                "IamRoleArn": "arn:aws:iam::123456789012:role/myRedshiftRole",
                "ApplyStatus": "in-sync"
            }
        ],
        "MaintenanceTrackName": "current",
        "DeferredMaintenanceWindows": [],
        "ExpectedNextSnapshotScheduleTime": "2019-12-10T04:42:43.390Z",
        "ExpectedNextSnapshotScheduleTimeStatus": "OnTrack",
        "NextMaintenanceWindowStartTime": "2019-12-14T16:00:00Z"
    }
}
```
Untuk informasi selengkapnya, lihat [Menyalin Snapshot ke AWS Wilayah Lain di Panduan](https://docs.aws.amazon.com/redshift/latest/mgmt/working-with-snapshots.html#cross-region-snapshot-copy) Manajemen *Cluster Amazon Redshift*.  
+  Untuk detail API, lihat [DisableSnapshotCopy](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/disable-snapshot-copy.html)di *Referensi AWS CLI Perintah*. 

### `enable-snapshot-copy`
<a name="redshift_EnableSnapshotCopy_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`enable-snapshot-copy`.

**AWS CLI**  
**Untuk mengaktifkan salinan snapshot untuk klaster**  
`enable-snapshot-copy`Contoh berikut memungkinkan salinan otomatis snapshot untuk cluster yang ditentukan.  

```
aws redshift enable-snapshot-copy \
    --cluster-identifier mycluster \
    --destination-region us-west-1
```
Output:  

```
{
    "Cluster": {
        "ClusterIdentifier": "mycluster",
        "NodeType": "dc2.large",
        "ClusterStatus": "available",
        "ClusterAvailabilityStatus": "Available",
        "MasterUsername": "adminuser",
        "DBName": "dev",
        "Endpoint": {
            "Address": "mycluster.cmeaswqeuae.us-west-2.redshift.amazonaws.com",
            "Port": 5439
        },
        "ClusterCreateTime": "2019-12-05T18:44:36.991Z",
        "AutomatedSnapshotRetentionPeriod": 3,
        "ManualSnapshotRetentionPeriod": -1,
        "ClusterSecurityGroups": [],
        "VpcSecurityGroups": [
            {
                "VpcSecurityGroupId": "sh-f4c731cd",
                "Status": "active"
            }
        ],
        "ClusterParameterGroups": [
            {
                "ParameterGroupName": "default.redshift-1.0",
                "ParameterApplyStatus": "in-sync"
            }
        ],
        "ClusterSubnetGroupName": "default",
        "VpcId": "vpc-b1ael7t9",
        "AvailabilityZone": "us-west-2f",
        "PreferredMaintenanceWindow": "sat:16:00-sat:16:30",
        "PendingModifiedValues": {
            "NodeType": "dc2.large",
            "NumberOfNodes": 2,
            "ClusterType": "multi-node"
        },
        "ClusterVersion": "1.0",
        "AllowVersionUpgrade": true,
        "NumberOfNodes": 4,
        "PubliclyAccessible": false,
        "Encrypted": false,
        "ClusterSnapshotCopyStatus": {
            "DestinationRegion": "us-west-1",
            "RetentionPeriod": 7,
            "ManualSnapshotRetentionPeriod": -1
        },
        "Tags": [
            {
                "Key": "mytags",
                "Value": "tag1"
            }
        ],
        "EnhancedVpcRouting": false,
        "IamRoles": [
            {
                "IamRoleArn": "arn:aws:iam::123456789012:role/myRedshiftRole",
                "ApplyStatus": "in-sync"
            }
        ],
        "MaintenanceTrackName": "current",
        "DeferredMaintenanceWindows": [],
        "ExpectedNextSnapshotScheduleTime": "2019-12-10T04:42:43.390Z",
        "ExpectedNextSnapshotScheduleTimeStatus": "OnTrack",
        "NextMaintenanceWindowStartTime": "2019-12-14T16:00:00Z"
    }
}
```
Untuk informasi selengkapnya, lihat [Menyalin Snapshot ke AWS Wilayah Lain di Panduan](https://docs.aws.amazon.com/redshift/latest/mgmt/working-with-snapshots.html#cross-region-snapshot-copy) Manajemen *Cluster Amazon Redshift*.  
+  Untuk detail API, lihat [EnableSnapshotCopy](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/enable-snapshot-copy.html)di *Referensi AWS CLI Perintah*. 

### `get-cluster-credentials`
<a name="redshift_GetClusterCredentials_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`get-cluster-credentials`.

**AWS CLI**  
**Untuk mendapatkan kredensi klaster untuk akun AWS **  
`get-cluster-credentials`Contoh berikut mengambil kredensil sementara yang memungkinkan akses ke database Amazon Redshift.  

```
aws redshift get-cluster-credentials \
    --db-user adminuser --db-name dev \
    --cluster-identifier mycluster
```
Output:  

```
{
    "DbUser": "IAM:adminuser",
    "DbPassword": "AMAFUyyuros/QjxPTtgzcsuQsqzIasdzJEN04aCtWDzXx1O9d6UmpkBtvEeqFly/EXAMPLE==",
    "Expiration": "2019-12-10T17:25:05.770Z"
}
```
*Untuk informasi selengkapnya, lihat [Membuat Kredensyal Database IAM Menggunakan Amazon Redshift CLI atau API di Panduan Manajemen Cluster](https://docs.aws.amazon.com/redshift/latest/mgmt/generating-iam-credentials-cli-api.html) Amazon Redshift.*  
+  Untuk detail API, lihat [GetClusterCredentials](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/get-cluster-credentials.html)di *Referensi AWS CLI Perintah*. 

### `get-reserved-node-exchange-offerings`
<a name="redshift_GetReservedNodeExchangeOfferings_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`get-reserved-node-exchange-offerings`.

**AWS CLI**  
**Untuk mendapatkan penawaran pertukaran node yang dipesan**  
`get-reserved-node-exchange-offerings`Contoh berikut mengambil array yang cocok dengan node `DC1` reserved yang ditentukan. `DC2` `ReservedNodeOfferings`  

```
aws redshift get-reserved-node-exchange-offerings \
    --reserved-node-id 12345678-12ab-12a1-1a2a-12ab-12a12EXAMPLE
```
Output:  

```
{
    "ReservedNodeOfferings": [
        {
            "ReservedNodeOfferingId": "12345678-12ab-12a1-1a2a-12ab-12a12EXAMPLE",
            "NodeType": "dc2.large",
            "Duration": 31536000,
            "FixedPrice": 0.0,
            "UsagePrice": 0.0,
            "CurrencyCode": "USD",
            "OfferingType": "All Upfront",
            "RecurringCharges": [
                {
                    "RecurringChargeAmount": 0.0,
                    "RecurringChargeFrequency": "Hourly"
                }
            ],
            "ReservedNodeOfferingType": "Regular"
        }
    ]
}
```
Untuk informasi selengkapnya, lihat [Memutakhirkan Node Cadangan Dengan AWS CLI](https://docs.aws.amazon.com/redshift/latest/mgmt/purchase-reserved-node-offering-console.html) di Panduan Manajemen Cluster *Amazon Redshift*.  
+  Untuk detail API, lihat [GetReservedNodeExchangeOfferings](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/get-reserved-node-exchange-offerings.html)di *Referensi AWS CLI Perintah*. 

### `modify-cluster-iam-roles`
<a name="redshift_ModifyClusterIamRoles_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`modify-cluster-iam-roles`.

**AWS CLI**  
**Untuk memodifikasi peran IAM untuk sebuah cluster**  
`modify-cluster-iam-roles`Contoh berikut menghapus peran AWS IAM tertentu dari cluster tertentu.  

```
aws redshift modify-cluster-iam-roles \
    --cluster-identifier mycluster \
    --remove-iam-roles arn:aws:iam::123456789012:role/myRedshiftRole
```
Output:  

```
{
    "Cluster": {
        "ClusterIdentifier": "mycluster",
        "NodeType": "dc2.large",
        "ClusterStatus": "available",
        "ClusterAvailabilityStatus": "Available",
        "MasterUsername": "adminuser",
        "DBName": "dev",
        "Endpoint": {
            "Address": "mycluster.cmeaswqeuae.us-west-2.redshift.amazonaws.com",
            "Port": 5439
        },
        "ClusterCreateTime": "2019-12-05T18:44:36.991Z",
        "AutomatedSnapshotRetentionPeriod": 3,
        "ManualSnapshotRetentionPeriod": -1,
        "ClusterSecurityGroups": [],
        "VpcSecurityGroups": [
            {
                "VpcSecurityGroupId": "sh-f9b731sd",
                "Status": "active"
            }
        ],
        "ClusterParameterGroups": [
            {
                "ParameterGroupName": "default.redshift-1.0",
                "ParameterApplyStatus": "in-sync"
            }
        ],
        "ClusterSubnetGroupName": "default",
        "VpcId": "vpc-b2fal7t9",
        "AvailabilityZone": "us-west-2f",
        "PreferredMaintenanceWindow": "sat:16:00-sat:16:30",
        "PendingModifiedValues": {
            "NodeType": "dc2.large",
            "NumberOfNodes": 2,
            "ClusterType": "multi-node"
        },
        "ClusterVersion": "1.0",
        "AllowVersionUpgrade": true,
        "NumberOfNodes": 4,
        "PubliclyAccessible": false,
        "Encrypted": false,
        "ClusterSnapshotCopyStatus": {
            "DestinationRegion": "us-west-1",
            "RetentionPeriod": 7,
            "ManualSnapshotRetentionPeriod": -1
        },
        "Tags": [
            {
                "Key": "mytags",
                "Value": "tag1"
            }
        ],
        "EnhancedVpcRouting": false,
        "IamRoles": [],
        "MaintenanceTrackName": "current",
        "DeferredMaintenanceWindows": [],
        "ExpectedNextSnapshotScheduleTime": "2019-12-11T04:42:55.631Z",
        "ExpectedNextSnapshotScheduleTimeStatus": "OnTrack",
        "NextMaintenanceWindowStartTime": "2019-12-14T16:00:00Z"
    }
}
```
Untuk informasi selengkapnya, lihat [Menggunakan Kebijakan Berbasis Identitas (Kebijakan IAM) untuk Amazon Redshift di](https://docs.aws.amazon.com/redshift/latest/mgmt/redshift-iam-access-control-identity-based.html) Panduan Manajemen Cluster Amazon *Redshift*.  
+  Untuk detail API, lihat [ModifyClusterIamRoles](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/modify-cluster-iam-roles.html)di *Referensi AWS CLI Perintah*. 

### `modify-cluster-maintenance`
<a name="redshift_ModifyClusterMaintenance_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`modify-cluster-maintenance`.

**AWS CLI**  
**Untuk memodifikasi pemeliharaan cluster**  
`modify-cluster-maintenance`Contoh berikut menunda pemeliharaan cluster yang ditentukan selama 30 hari.  

```
aws redshift modify-cluster-maintenance \
    --cluster-identifier mycluster \
    --defer-maintenance \
    --defer-maintenance-duration 30
```
Output:  

```
{
    "Cluster": {
        "ClusterIdentifier": "mycluster",
        "NodeType": "dc2.large",
        "ClusterStatus": "available",
        "ClusterAvailabilityStatus": "Available",
        "MasterUsername": "adminuser",
        "DBName": "dev",
        "Endpoint": {
            "Address": "mycluster.cmeaswqeuae.us-west-2.redshift.amazonaws.com",
            "Port": 5439
        },
        "ClusterCreateTime": "2019-12-05T18:44:36.991Z",
        "AutomatedSnapshotRetentionPeriod": 3,
        "ManualSnapshotRetentionPeriod": -1,
        "ClusterSecurityGroups": [],
        "VpcSecurityGroups": [
            {
                "VpcSecurityGroupId": "sh-a1a123ab",
                "Status": "active"
            }
        ],
        "ClusterParameterGroups": [
            {
                "ParameterGroupName": "default.redshift-1.0",
                "ParameterApplyStatus": "in-sync"
            }
        ],
        "ClusterSubnetGroupName": "default",
        "VpcId": "vpc-b1ael7t9",
        "AvailabilityZone": "us-west-2f",
        "PreferredMaintenanceWindow": "sat:16:00-sat:16:30",
        "PendingModifiedValues": {
            "NodeType": "dc2.large",
            "NumberOfNodes": 2,
            "ClusterType": "multi-node"
        },
        "ClusterVersion": "1.0",
        "AllowVersionUpgrade": true,
        "NumberOfNodes": 4,
        "PubliclyAccessible": false,
        "Encrypted": false,
        "ClusterSnapshotCopyStatus": {
            "DestinationRegion": "us-west-1",
            "RetentionPeriod": 7,
            "ManualSnapshotRetentionPeriod": -1
        },
        "Tags": [
            {
                "Key": "mytags",
                "Value": "tag1"
            }
        ],
        "EnhancedVpcRouting": false,
        "IamRoles": [],
        "MaintenanceTrackName": "current",
        "DeferredMaintenanceWindows": [
            {
                "DeferMaintenanceIdentifier": "dfm-mUdVIfFcT1B4SGhw6fyF",
                "DeferMaintenanceStartTime": "2019-12-10T18:18:39.354Z",
                "DeferMaintenanceEndTime": "2020-01-09T18:18:39.354Z"
            }
        ],
        "ExpectedNextSnapshotScheduleTime": "2019-12-11T04:42:55.631Z",
        "ExpectedNextSnapshotScheduleTimeStatus": "OnTrack",
        "NextMaintenanceWindowStartTime": "2020-01-11T16:00:00Z"
    }
}
```
Untuk informasi selengkapnya, lihat [Pemeliharaan Cluster](https://docs.aws.amazon.com/redshift/latest/mgmt/working-with-clusters.html#rs-cluster-maintenance) di *Panduan Manajemen Cluster Amazon Redshift*.  
+  Untuk detail API, lihat [ModifyClusterMaintenance](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/modify-cluster-maintenance.html)di *Referensi AWS CLI Perintah*. 

### `modify-cluster-parameter-group`
<a name="redshift_ModifyClusterParameterGroup_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`modify-cluster-parameter-group`.

**AWS CLI**  
**Ubah parameter dalam grup parameter**  
`modify-cluster-parameter-group`Contoh berikut memodifikasi parameter *wlm\$1json\$1configuration* untuk manajemen beban kerja. Ini menerima parameter dari file yang berisi konten JSON yang ditunjukkan di bawah ini.  

```
aws redshift modify-cluster-parameter-group \
    --parameter-group-name myclusterparametergroup \
    --parameters file://modify_pg.json
```
Isi dari `modify_pg.json`:  

```
[
    {
        "ParameterName": "wlm_json_configuration",
        "ParameterValue": "[{\"user_group\":\"example_user_group1\",\"query_group\": \"example_query_group1\", \"query_concurrency\":7},{\"query_concurrency\":5}]"
    }
]
```
Output:  

```
{
   "ParameterGroupStatus": "Your parameter group has been updated but changes won't get applied until you reboot the associated Clusters.",
   "ParameterGroupName": "myclusterparametergroup",
   "ResponseMetadata": {
      "RequestId": "09974cc0-64cd-11e2-bea9-49e0ce183f07"
   }
}
```
+  Untuk detail API, lihat [ModifyClusterParameterGroup](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/modify-cluster-parameter-group.html)di *Referensi AWS CLI Perintah*. 

### `modify-cluster-snapshot-schedule`
<a name="redshift_ModifyClusterSnapshotSchedule_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`modify-cluster-snapshot-schedule`.

**AWS CLI**  
**Untuk mengubah jadwal snapshot cluster**  
`modify-cluster-snapshot-schedule`Contoh berikut menghapus jadwal snapshot yang ditentukan dari cluster yang ditentukan.  

```
aws redshift modify-cluster-snapshot-schedule \
    --cluster-identifier mycluster \
    --schedule-identifier mysnapshotschedule \
    --disassociate-schedule
```
Perintah ini tidak menghasilkan output apa pun.  
Untuk informasi selengkapnya, lihat [Jadwal Snapshot Otomatis di Panduan](https://docs.aws.amazon.com/redshift/latest/mgmt/working-with-snapshots.html#automated-snapshot-schedules) Manajemen *Cluster Amazon Redshift*.  
+  Untuk detail API, lihat [ModifyClusterSnapshotSchedule](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/modify-cluster-snapshot-schedule.html)di *Referensi AWS CLI Perintah*. 

### `modify-cluster-snapshot`
<a name="redshift_ModifyClusterSnapshot_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`modify-cluster-snapshot`.

**AWS CLI**  
**Untuk memodifikasi snapshot cluster**  
`modify-cluster-snapshot`Contoh berikut menetapkan pengaturan periode retensi manual untuk snapshot cluster yang ditentukan ke nilai 10 hari.  

```
aws redshift modify-cluster-snapshot \
    --snapshot-identifier mycluster-2019-11-06-16-32 \
    --manual-snapshot-retention-period 10
```
Output:  

```
{
    "Snapshot": {
        "SnapshotIdentifier": "mycluster-2019-11-06-16-32",
        "ClusterIdentifier": "mycluster",
        "SnapshotCreateTime": "2019-12-07T00:34:05.633Z",
        "Status": "available",
        "Port": 5439,
        "AvailabilityZone": "us-west-2f",
        "ClusterCreateTime": "2019-12-05T18:44:36.991Z",
        "MasterUsername": "adminuser",
        "ClusterVersion": "1.0",
        "SnapshotType": "manual",
        "NodeType": "dc2.large",
        "NumberOfNodes": 2,
        "DBName": "dev",
        "VpcId": "vpc-b1cel7t9",
        "Encrypted": false,
        "EncryptedWithHSM": false,
        "OwnerAccount": "123456789012",
        "TotalBackupSizeInMegaBytes": 64384.0,
        "ActualIncrementalBackupSizeInMegaBytes": 24.0,
        "BackupProgressInMegaBytes": 24.0,
        "CurrentBackupRateInMegaBytesPerSecond": 13.0011,
        "EstimatedSecondsToCompletion": 0,
        "ElapsedTimeInSeconds": 1,
        "Tags": [
            {
                "Key": "mytagkey",
                "Value": "mytagvalue"
            }
        ],
        "EnhancedVpcRouting": false,
        "MaintenanceTrackName": "current",
        "ManualSnapshotRetentionPeriod": 10,
        "ManualSnapshotRemainingDays": 6,
        "SnapshotRetentionStartTime": "2019-12-07T00:34:07.479Z"
    }
}
```
Untuk informasi selengkapnya, lihat [Snapshot Amazon Redshift](https://docs.aws.amazon.com/redshift/latest/mgmt/working-with-snapshots.html) di Panduan Manajemen Cluster *Amazon Redshift*.  
+  Untuk detail API, lihat [ModifyClusterSnapshot](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/modify-cluster-snapshot.html)di *Referensi AWS CLI Perintah*. 

### `modify-cluster-subnet-group`
<a name="redshift_ModifyClusterSubnetGroup_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`modify-cluster-subnet-group`.

**AWS CLI**  
Memodifikasi Subnet dalam GroupThis contoh Cluster Subnet menunjukkan cara memodifikasi daftar subnet dalam grup subnet cache. Secara default, output dalam format JSON.Command:  

```
aws redshift modify-cluster-subnet-group --cluster-subnet-group-name mysubnetgroup --subnet-ids subnet-763fdd1 subnet-ac830e9
```
Hasil:  

```
{
   "ClusterSubnetGroup":
   {
      "Subnets": [
         {
            "SubnetStatus": "Active",
            "SubnetIdentifier": "subnet-763fdd1c",
            "SubnetAvailabilityZone":
               { "Name": "us-east-1a" }
         },
         {
            "SubnetStatus": "Active",
            "SubnetIdentifier": "subnet-ac830e9",
            "SubnetAvailabilityZone":
               { "Name": "us-east-1b" }
         } ],
      "VpcId": "vpc-7e3fdd14",
      "SubnetGroupStatus": "Complete",
      "Description": "My subnet group",
      "ClusterSubnetGroupName": "mysubnetgroup"
   },
   "ResponseMetadata": {
      "RequestId": "8da93e89-8372-f936-93a8-873918938197a"
   }
}
```
+  Untuk detail API, lihat [ModifyClusterSubnetGroup](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/modify-cluster-subnet-group.html)di *Referensi AWS CLI Perintah*. 

### `modify-cluster`
<a name="redshift_ModifyCluster_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`modify-cluster`.

**AWS CLI**  
Mengaitkan Grup Keamanan dengan ClusterThis contoh menunjukkan cara mengaitkan grup keamanan klaster dengan Cluster.command yang ditentukan:  

```
aws redshift modify-cluster --cluster-identifier mycluster --cluster-security-groups mysecuritygroup
```
Ubah Jendela Pemeliharaan untuk ClusterThis menunjukkan cara mengubah jendela pemeliharaan pilihan mingguan untuk cluster menjadi jendela minimum empat jam mulai hari Minggu pukul 11:15, dan berakhir Senin pukul 3:15 pagi. Perintah:  

```
aws redshift modify-cluster --cluster-identifier mycluster --preferred-maintenance-window Sun:23:15-Mon:03:15
```
Ubah Kata Sandi Master untuk ClusterThis contoh menunjukkan cara mengubah kata sandi master untuk cluster.Command:  

```
aws redshift modify-cluster --cluster-identifier mycluster --master-user-password A1b2c3d4
```
+  Untuk detail API, lihat [ModifyCluster](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/modify-cluster.html)di *Referensi AWS CLI Perintah*. 

### `modify-event-subscription`
<a name="redshift_ModifyEventSubscription_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`modify-event-subscription`.

**AWS CLI**  
**Untuk memodifikasi langganan acara**  
`modify-event-subscription`Contoh berikut menonaktifkan langganan pemberitahuan acara yang ditentukan.  

```
aws redshift modify-event-subscription \
    --subscription-name mysubscription \
    --no-enabled
```
Output:  

```
{
    "EventSubscription": {
        "CustomerAwsId": "123456789012",
        "CustSubscriptionId": "mysubscription",
        "SnsTopicArn": "arn:aws:sns:us-west-2:123456789012:MySNStopic",
        "Status": "active",
        "SubscriptionCreationTime": "2019-12-09T21:50:21.332Z",
        "SourceIdsList": [],
        "EventCategoriesList": [
            "management"
        ],
        "Severity": "ERROR",
        "Enabled": false,
        "Tags": []
    }
}
```
Untuk informasi selengkapnya, lihat [Berlangganan Pemberitahuan Peristiwa Amazon Redshift](https://docs.aws.amazon.com/redshift/latest/mgmt/working-with-event-notifications.html) di Panduan Manajemen Cluster *Amazon Redshift*.  
+  Untuk detail API, lihat [ModifyEventSubscription](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/modify-event-subscription.html)di *Referensi AWS CLI Perintah*. 

### `modify-scheduled-action`
<a name="redshift_ModifyScheduledAction_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`modify-scheduled-action`.

**AWS CLI**  
**Untuk memodifikasi tindakan terjadwal**  
`modify-scheduled-action`Contoh berikut menambahkan deskripsi untuk tindakan terjadwal tertentu yang ada.  

```
aws redshift modify-scheduled-action \
    --scheduled-action-name myscheduledaction \
    --scheduled-action-description "My scheduled action"
```
Output:  

```
{
    "ScheduledActionName": "myscheduledaction",
    "TargetAction": {
        "ResizeCluster": {
            "ClusterIdentifier": "mycluster",
            "NumberOfNodes": 2,
            "Classic": false
        }
    },
    "Schedule": "at(2019-12-25T00:00:00)",
    "IamRole": "arn:aws:iam::123456789012:role/myRedshiftRole",
    "ScheduledActionDescription": "My scheduled action",
    "State": "ACTIVE",
    "NextInvocations": [
        "2019-12-25T00:00:00Z"
    ]
}
```
+  Untuk detail API, lihat [ModifyScheduledAction](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/modify-scheduled-action.html)di *Referensi AWS CLI Perintah*. 

### `modify-snapshot-copy-retention-period`
<a name="redshift_ModifySnapshotCopyRetentionPeriod_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`modify-snapshot-copy-retention-period`.

**AWS CLI**  
**Untuk mengubah periode penyimpanan salinan snapshot**  
`modify-snapshot-copy-retention-period`Contoh berikut memodifikasi jumlah hari untuk menyimpan snapshot untuk cluster yang ditentukan di AWS Wilayah tujuan setelah disalin dari Wilayah sumber. AWS   

```
aws redshift modify-snapshot-copy-retention-period \
    --cluster-identifier mycluster \
    --retention-period 15
```
Output:  

```
{
    "Cluster": {
        "ClusterIdentifier": "mycluster",
        "NodeType": "dc2.large",
        "ClusterStatus": "available",
        "ClusterAvailabilityStatus": "Available",
        "MasterUsername": "adminuser",
        "DBName": "dev",
        "Endpoint": {
            "Address": "mycluster.cmeaswqeuae.us-west-2.redshift.amazonaws.com",
            "Port": 5439
        },
        "ClusterCreateTime": "2019-12-05T18:44:36.991Z",
        "AutomatedSnapshotRetentionPeriod": 3,
        "ManualSnapshotRetentionPeriod": -1,
        "ClusterSecurityGroups": [],
        "VpcSecurityGroups": [
            {
                "VpcSecurityGroupId": "sh-a1a123ab",
                "Status": "active"
            }
        ],
        "ClusterParameterGroups": [
            {
                "ParameterGroupName": "default.redshift-1.0",
                "ParameterApplyStatus": "in-sync"
            }
        ],
        "ClusterSubnetGroupName": "default",
        "VpcId": "vpc-b1fet7t9",
        "AvailabilityZone": "us-west-2f",
        "PreferredMaintenanceWindow": "sat:16:00-sat:16:30",
        "PendingModifiedValues": {
            "NodeType": "dc2.large",
            "NumberOfNodes": 2,
            "ClusterType": "multi-node"
        },
        "ClusterVersion": "1.0",
        "AllowVersionUpgrade": true,
        "NumberOfNodes": 4,
        "PubliclyAccessible": false,
        "Encrypted": false,
        "ClusterSnapshotCopyStatus": {
            "DestinationRegion": "us-west-1",
            "RetentionPeriod": 15,
            "ManualSnapshotRetentionPeriod": -1
        },
        "Tags": [
            {
                "Key": "mytags",
                "Value": "tag1"
            }
        ],
        "EnhancedVpcRouting": false,
        "IamRoles": [],
        "MaintenanceTrackName": "current",
        "DeferredMaintenanceWindows": [
            {
                "DeferMaintenanceIdentifier": "dfm-mUdVSfDcT1F4SGhw6fyF",
                "DeferMaintenanceStartTime": "2019-12-10T18:18:39.354Z",
                "DeferMaintenanceEndTime": "2020-01-09T18:18:39.354Z"
            }
        ],
        "NextMaintenanceWindowStartTime": "2020-01-11T16:00:00Z"
    }
}
```
Untuk informasi selengkapnya, lihat [Format Jadwal Snapshot](https://docs.aws.amazon.com/redshift/latest/mgmt/working-with-snapshots.html#working-with-snapshot-scheduling) di Panduan Manajemen *Cluster Amazon Redshift*.  
+  Untuk detail API, lihat [ModifySnapshotCopyRetentionPeriod](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/modify-snapshot-copy-retention-period.html)di *Referensi AWS CLI Perintah*. 

### `modify-snapshot-schedule`
<a name="redshift_ModifySnapshotSchedule_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`modify-snapshot-schedule`.

**AWS CLI**  
**Untuk mengubah jadwal snapshot**  
`modify-snapshot-schedule`Contoh berikut memodifikasi tingkat jadwal snapshot yang ditentukan untuk setiap 10 jam.  

```
aws redshift modify-snapshot-schedule \
    --schedule-identifier mysnapshotschedule \
    --schedule-definitions "rate(10 hours)"
```
Output:  

```
{
    "ScheduleDefinitions": [
        "rate(10 hours)"
    ],
    "ScheduleIdentifier": "mysnapshotschedule",
    "ScheduleDescription": "My schedule description",
    "Tags": []
}
```
Untuk informasi selengkapnya, lihat [Format Jadwal Snapshot](https://docs.aws.amazon.com/redshift/latest/mgmt/working-with-snapshots.html#working-with-snapshot-scheduling) di Panduan Manajemen *Cluster Amazon Redshift*.  
+  Untuk detail API, lihat [ModifySnapshotSchedule](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/modify-snapshot-schedule.html)di *Referensi AWS CLI Perintah*. 

### `purchase-reserved-node-offering`
<a name="redshift_PurchaseReservedNodeOffering_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`purchase-reserved-node-offering`.

**AWS CLI**  
Membeli NodeThis contoh Reserved menunjukkan cara membeli penawaran node reserved. `reserved-node-offering-id`Ini diperoleh dengan `describe-reserved-node-offerings` memanggil.Command:  

```
aws redshift purchase-reserved-node-offering --reserved-node-offering-id ceb6a579-cf4c-4343-be8b-d832c45ab51c
```
Hasil:  

```
{
   "ReservedNode": {
      "OfferingType": "Heavy Utilization",
      "FixedPrice": "",
      "NodeType": "dw.hs1.xlarge",
      "ReservedNodeId": "1ba8e2e3-bc01-4d65-b35d-a4a3e931547e",
      "UsagePrice": "",
      "RecurringCharges": [
         {
            "RecurringChargeAmount": "",
            "RecurringChargeFrequency": "Hourly"
         }
      ],
      "NodeCount": 1,
      "State": "payment-pending",
      "StartTime": "2013-02-13T17:08:39.051Z",
      "Duration": 31536000,
      "ReservedNodeOfferingId": "ceb6a579-cf4c-4343-be8b-d832c45ab51c"
   },
   "ResponseMetadata": {
      "RequestId": "01bda7bf-7600-11e2-b605-2568d7396e7f"
   }
}
```
+  Untuk detail API, lihat [PurchaseReservedNodeOffering](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/purchase-reserved-node-offering.html)di *Referensi AWS CLI Perintah*. 

### `reboot-cluster`
<a name="redshift_RebootCluster_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`reboot-cluster`.

**AWS CLI**  
Reboot ClusterThis contoh me-reboot sebuah cluster. Secara default, output dalam format JSON.Command:  

```
aws redshift reboot-cluster --cluster-identifier mycluster
```
Hasil:  

```
{
   "Cluster": {
      "NodeType": "dw.hs1.xlarge",
      "Endpoint": {
         "Port": 5439,
         "Address": "mycluster.coqoarplqhsn.us-east-1.redshift.amazonaws.com"
      },
      "ClusterVersion": "1.0",
      "PubliclyAccessible": "true",
      "MasterUsername": "adminuser",
      "ClusterParameterGroups": [
         {
         "ParameterApplyStatus": "in-sync",
         "ParameterGroupName": "default.redshift-1.0"
         }
      ],
      "ClusterSecurityGroups": [
         {
         "Status": "active",
         "ClusterSecurityGroupName": "default"
         }
      ],
      "AllowVersionUpgrade": true,
      "VpcSecurityGroups": \[],
      "AvailabilityZone": "us-east-1a",
      "ClusterCreateTime": "2013-01-22T21:59:29.559Z",
      "PreferredMaintenanceWindow": "sun:23:15-mon:03:15",
      "AutomatedSnapshotRetentionPeriod": 1,
      "ClusterStatus": "rebooting",
      "ClusterIdentifier": "mycluster",
      "DBName": "dev",
      "NumberOfNodes": 2,
      "PendingModifiedValues": {}
   },
   "ResponseMetadata": {
      "RequestId": "61c8b564-64e8-11e2-8f7d-3b939af52818"
   }
}
```
+  Untuk detail API, lihat [RebootCluster](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/reboot-cluster.html)di *Referensi AWS CLI Perintah*. 

### `reset-cluster-parameter-group`
<a name="redshift_ResetClusterParameterGroup_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`reset-cluster-parameter-group`.

**AWS CLI**  
Reset Parameter dalam GroupThis contoh Parameter menunjukkan cara mengatur ulang semua parameter dalam parameter Group.Command:  

```
aws redshift reset-cluster-parameter-group --parameter-group-name myclusterparametergroup --reset-all-parameters
```
+  Untuk detail API, lihat [ResetClusterParameterGroup](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/reset-cluster-parameter-group.html)di *Referensi AWS CLI Perintah*. 

### `resize-cluster`
<a name="redshift_ResizeCluster_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`resize-cluster`.

**AWS CLI**  
**Untuk mengubah ukuran cluster**  
`resize-cluster`Contoh berikut mengubah ukuran cluster yang ditentukan.  

```
aws redshift resize-cluster \
    --cluster-identifier mycluster \
    --cluster-type multi-node \
    --node-type dc2.large \
    --number-of-nodes 6 \
    --classic
```
Output:  

```
{
    "Cluster": {
        "ClusterIdentifier": "mycluster",
        "NodeType": "dc2.large",
        "ClusterStatus": "resizing",
        "ClusterAvailabilityStatus": "Modifying",
        "MasterUsername": "adminuser",
        "DBName": "dev",
        "Endpoint": {
            "Address": "mycluster.cmeaswqeuae.us-west-2.redshift.amazonaws.com",
            "Port": 5439
        },
        "ClusterCreateTime": "2019-12-05T18:44:36.991Z",
        "AutomatedSnapshotRetentionPeriod": 3,
        "ManualSnapshotRetentionPeriod": -1,
        "ClusterSecurityGroups": [],
        "VpcSecurityGroups": [
            {
                "VpcSecurityGroupId": "sh-a1a123ab",
                "Status": "active"
            }
        ],
        "ClusterParameterGroups": [
            {
                "ParameterGroupName": "default.redshift-1.0",
                "ParameterApplyStatus": "in-sync"
            }
        ],
        "ClusterSubnetGroupName": "default",
        "VpcId": "vpc-a1abc1a1",
        "AvailabilityZone": "us-west-2f",
        "PreferredMaintenanceWindow": "sat:16:00-sat:16:30",
        "PendingModifiedValues": {
            "NodeType": "dc2.large",
            "NumberOfNodes": 6,
            "ClusterType": "multi-node"
        },
        "ClusterVersion": "1.0",
        "AllowVersionUpgrade": true,
        "NumberOfNodes": 4,
        "PubliclyAccessible": false,
        "Encrypted": false,
        "ClusterSnapshotCopyStatus": {
            "DestinationRegion": "us-west-1",
            "RetentionPeriod": 15,
            "ManualSnapshotRetentionPeriod": -1
        },
        "Tags": [
            {
                "Key": "mytags",
                "Value": "tag1"
            }
        ],
        "EnhancedVpcRouting": false,
        "IamRoles": [],
        "MaintenanceTrackName": "current",
        "DeferredMaintenanceWindows": [
            {
                "DeferMaintenanceIdentifier": "dfm-mUdVCfDcT1B4SGhw6fyF",
                "DeferMaintenanceStartTime": "2019-12-10T18:18:39.354Z",
                "DeferMaintenanceEndTime": "2020-01-09T18:18:39.354Z"
            }
        ],
        "NextMaintenanceWindowStartTime": "2020-01-11T16:00:00Z",
        "ResizeInfo": {
            "ResizeType": "ClassicResize",
            "AllowCancelResize": true
        }
    }
}
```
Untuk informasi selengkapnya, lihat [Mengubah Ukuran Cluster](https://docs.aws.amazon.com/redshift/latest/mgmt/working-with-clusters.html#cluster-resize-intro) di Panduan Manajemen *Cluster Amazon Redshift*.  
+  Untuk detail API, lihat [ResizeCluster](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/resize-cluster.html)di *Referensi AWS CLI Perintah*. 

### `restore-from-cluster-snapshot`
<a name="redshift_RestoreFromClusterSnapshot_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`restore-from-cluster-snapshot`.

**AWS CLI**  
Memulihkan Cluster Dari SnapshotThis contoh mengembalikan cluster dari Snapshot.Command:  

```
aws redshift restore-from-cluster-snapshot --cluster-identifier mycluster-clone --snapshot-identifier my-snapshot-id
```
Hasil:  

```
{
   "Cluster": {
      "NodeType": "dw.hs1.xlarge",
      "ClusterVersion": "1.0",
      "PubliclyAccessible": "true",
      "MasterUsername": "adminuser",
      "ClusterParameterGroups": [
         {
         "ParameterApplyStatus": "in-sync",
         "ParameterGroupName": "default.redshift-1.0"
         }
      ],
      "ClusterSecurityGroups": [
         {
         "Status": "active",
         "ClusterSecurityGroupName": "default"
         }
      ],
      "AllowVersionUpgrade": true,
      "VpcSecurityGroups": \[],
      "PreferredMaintenanceWindow": "sun:23:15-mon:03:15",
      "AutomatedSnapshotRetentionPeriod": 1,
      "ClusterStatus": "creating",
      "ClusterIdentifier": "mycluster-clone",
      "DBName": "dev",
      "NumberOfNodes": 2,
      "PendingModifiedValues": {}
   },
   "ResponseMetadata": {
      "RequestId": "77fd512b-64e3-11e2-8f5b-e90bd6c77476"
   }
}
```
+  Untuk detail API, lihat [RestoreFromClusterSnapshot](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/restore-from-cluster-snapshot.html)di *Referensi AWS CLI Perintah*. 

### `restore-table-from-cluster-snapshot`
<a name="redshift_RestoreTableFromClusterSnapshot_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`restore-table-from-cluster-snapshot`.

**AWS CLI**  
**Untuk mengembalikan tabel dari snapshot cluster**  
`restore-table-from-cluster-snapshot`Contoh berikut membuat tabel baru dari tabel yang ditentukan dalam snapshot cluster tertentu.  

```
aws redshift restore-table-from-cluster-snapshot /
    --cluster-identifier mycluster /
    --snapshot-identifier mycluster-2019-11-19-16-17 /
    --source-database-name dev /
    --source-schema-name public /
    --source-table-name mytable /
    --target-database-name dev /
    --target-schema-name public /
    --new-table-name mytable-clone
```
Output:  

```
{
    "TableRestoreStatus": {
        "TableRestoreRequestId": "a123a12b-abc1-1a1a-a123-a1234ab12345",
        "Status": "PENDING",
        "RequestTime": "2019-12-20T00:20:16.402Z",
        "ClusterIdentifier": "mycluster",
        "SnapshotIdentifier": "mycluster-2019-11-19-16-17",
        "SourceDatabaseName": "dev",
        "SourceSchemaName": "public",
        "SourceTableName": "mytable",
        "TargetDatabaseName": "dev",
        "TargetSchemaName": "public",
        "NewTableName": "mytable-clone"
    }
}
```
Untuk informasi selengkapnya, lihat [Memulihkan Tabel dari Snapshot di Panduan](https://docs.aws.amazon.com/redshift/latest/mgmt/working-with-snapshots.html#working-with-snapshot-restore-table-from-snapshot) Manajemen *Cluster Amazon Redshift*.  
+  Untuk detail API, lihat [RestoreTableFromClusterSnapshot](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/restore-table-from-cluster-snapshot.html)di *Referensi AWS CLI Perintah*. 

### `revoke-cluster-security-group-ingress`
<a name="redshift_RevokeClusterSecurityGroupIngress_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`revoke-cluster-security-group-ingress`.

**AWS CLI**  
Mencabut Akses dari GroupThis contoh Keamanan EC2 mencabut akses ke grup keamanan Amazon EC2 bernama.Perintah:  

```
aws redshift revoke-cluster-security-group-ingress --cluster-security-group-name mysecuritygroup --ec2-security-group-name myec2securitygroup --ec2-security-group-owner-id 123445677890
```
Mencabut Akses ke rentang CIDRContoh ini mencabut akses ke rentang CIDR.Command:  

```
aws redshift revoke-cluster-security-group-ingress --cluster-security-group-name mysecuritygroup --cidrip 192.168.100.100/32
```
+  Untuk detail API, lihat [RevokeClusterSecurityGroupIngress](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/revoke-cluster-security-group-ingress.html)di *Referensi AWS CLI Perintah*. 

### `revoke-snapshot-access`
<a name="redshift_RevokeSnapshotAccess_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`revoke-snapshot-access`.

**AWS CLI**  
Mencabut otorisasi AWS akun untuk memulihkan SnapshotThis contoh mencabut otorisasi AWS akun `444455556666` untuk mengembalikan snapshot. `my-snapshot-id` Secara default, output dalam format JSON.Command:  

```
aws redshift revoke-snapshot-access --snapshot-id my-snapshot-id --account-with-restore-access 444455556666
```
Hasil:  

```
{
   "Snapshot": {
      "Status": "available",
      "SnapshotCreateTime": "2013-07-17T22:04:18.947Z",
      "EstimatedSecondsToCompletion": 0,
      "AvailabilityZone": "us-east-1a",
      "ClusterVersion": "1.0",
      "MasterUsername": "adminuser",
      "Encrypted": false,
      "OwnerAccount": "111122223333",
      "BackupProgressInMegabytes": 11.0,
      "ElapsedTimeInSeconds": 0,
      "DBName": "dev",
      "CurrentBackupRateInMegabytesPerSecond: 0.1534,
      "ClusterCreateTime": "2013-01-22T21:59:29.559Z",
      "ActualIncrementalBackupSizeInMegabytes"; 11.0,
      "SnapshotType": "manual",
      "NodeType": "dw.hs1.xlarge",
      "ClusterIdentifier": "mycluster",
      "TotalBackupSizeInMegabytes": 20.0,
      "Port": 5439,
      "NumberOfNodes": 2,
      "SnapshotIdentifier": "my-snapshot-id"
   }
}
```
+  Untuk detail API, lihat [RevokeSnapshotAccess](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/revoke-snapshot-access.html)di *Referensi AWS CLI Perintah*. 

### `rotate-encryption-key`
<a name="redshift_RotateEncryptionKey_cli_2_topic"></a>

Contoh kode berikut menunjukkan cara menggunakan`rotate-encryption-key`.

**AWS CLI**  
**Untuk memutar kunci enkripsi untuk klaster**  
`rotate-encryption-key`Contoh berikut memutar kunci enkripsi untuk cluster tertentu.  

```
aws redshift rotate-encryption-key \
    --cluster-identifier mycluster
```
Output:  

```
{
    "Cluster": {
        "ClusterIdentifier": "mycluster",
        "NodeType": "dc2.large",
        "ClusterStatus": "rotating-keys",
        "ClusterAvailabilityStatus": "Modifying",
        "MasterUsername": "adminuser",
        "DBName": "dev",
        "Endpoint": {
            "Address": "mycluster.cmeaswqeuae.us-west-2.redshift.amazonaws.com",
            "Port": 5439
        },
        "ClusterCreateTime": "2019-12-10T19:25:45.886Z",
        "AutomatedSnapshotRetentionPeriod": 30,
        "ManualSnapshotRetentionPeriod": -1,
        "ClusterSecurityGroups": [],
        "VpcSecurityGroups": [
            {
                "VpcSecurityGroupId": "sh-a1a123ab",
                "Status": "active"
            }
        ],
        "ClusterParameterGroups": [
            {
                "ParameterGroupName": "default.redshift-1.0",
                "ParameterApplyStatus": "in-sync"
            }
        ],
        "ClusterSubnetGroupName": "default",
        "VpcId": "vpc-a1abc1a1",
        "AvailabilityZone": "us-west-2a",
        "PreferredMaintenanceWindow": "sat:16:00-sat:16:30",
        "PendingModifiedValues": {},
        "ClusterVersion": "1.0",
        "AllowVersionUpgrade": true,
        "NumberOfNodes": 2,
        "PubliclyAccessible": false,
        "Encrypted": true,
        "Tags": [],
        "KmsKeyId": "arn:aws:kms:us-west-2:123456789012:key/bPxRfih3yCo8nvbEXAMPLEKEY",
        "EnhancedVpcRouting": false,
        "IamRoles": [
            {
                "IamRoleArn": "arn:aws:iam::123456789012:role/myRedshiftRole",
                "ApplyStatus": "in-sync"
            }
        ],
        "MaintenanceTrackName": "current",
        "DeferredMaintenanceWindows": [],
        "NextMaintenanceWindowStartTime": "2019-12-14T16:00:00Z"
    }
}
```
Untuk informasi selengkapnya, lihat [Enkripsi Database Amazon Redshift](https://docs.aws.amazon.com/redshift/latest/mgmt/working-with-db-encryption.html) di Panduan Manajemen *Cluster Amazon Redshift*.  
+  Untuk detail API, lihat [RotateEncryptionKey](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/redshift/rotate-encryption-key.html)di *Referensi AWS CLI Perintah*. 