Sono disponibili altri esempi AWS SDK nel repository [AWS Doc SDK](https://github.com/awsdocs/aws-doc-sdk-examples) Examples. GitHub
Le traduzioni sono generate tramite traduzione automatica. In caso di conflitto tra il contenuto di una traduzione e la versione originale in Inglese, quest'ultima prevarrà.
# AWS DMS esempi che utilizzano AWS CLI
I seguenti esempi di codice mostrano come eseguire azioni e implementare scenari comuni utilizzando AWS Command Line Interface with AWS DMS.
Le *azioni* sono estratti di codice da programmi più grandi e devono essere eseguite nel contesto. Sebbene le azioni mostrino come richiamare le singole funzioni del servizio, è possibile visualizzarle contestualizzate negli scenari correlati.
Ogni esempio include un link al codice sorgente completo, in cui vengono fornite le istruzioni su come configurare ed eseguire il codice nel contesto.
**Topics**
+ [Azioni](#actions)
## Azioni
### `add-tags-to-resource`
Il seguente esempio di codice mostra come utilizzare`add-tags-to-resource`.
**AWS CLI**
**Come aggiungere tag a una risorsa**
L’esempio `add-tags-to-resource` seguente aggiunge dei tag all’istanza di replica.
```
aws dms add-tags-to-resource \
--resource-arn arn:aws:dms:us-east-1:123456789012:rep:T3OM7OUB5NM2LCVZF7JPGJRNUE \
--tags Key=Environment,Value=PROD Key=Project,Value=dbMigration
```
Questo comando non produce alcun output.
Per ulteriori informazioni, consulta [Assegnazione di tag alle risorse](https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Tagging.html) nella *Guida per l’utente di AWS Database Migration Service*.
+ Per i dettagli sull'API, consulta [AddTagsToResource AWS CLI](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/dms/add-tags-to-resource.html)*Command Reference*.
### `create-endpoint`
Il seguente esempio di codice mostra come utilizzare`create-endpoint`.
**AWS CLI**
**Come creare un endpoint**
L’esempio `create-endpoint` seguente crea un endpoint per un’origine Amazon S3.
```
aws dms create-endpoint \
--endpoint-type source \
--engine-name s3 \
--endpoint-identifier src-endpoint \
--s3-settings file://s3-settings.json
```
Contenuto di `s3-settings.json`:
```
{
"BucketName":"my-corp-data",
"BucketFolder":"sourcedata",
"ServiceAccessRoleArn":"arn:aws:iam::123456789012:role/my-s3-access-role"
}
```
Output:
```
{
"Endpoint": {
"EndpointIdentifier": "src-endpoint",
"EndpointType": "SOURCE",
"EngineName": "s3",
"EngineDisplayName": "Amazon S3",
"ExtraConnectionAttributes": "bucketFolder=sourcedata;bucketName=my-corp-data;compressionType=NONE;csvDelimiter=,;csvRowDelimiter=\\n;",
"Status": "active",
"EndpointArn": "arn:aws:dms:us-east-1:123456789012:endpoint:GUVAFG34EECUOJ6QVZ56DAHT3U",
"SslMode": "none",
"ServiceAccessRoleArn": "arn:aws:iam::123456789012:role/my-s3-access-role",
"S3Settings": {
"ServiceAccessRoleArn": "arn:aws:iam::123456789012:role/my-s3-access-role",
"CsvRowDelimiter": "\\n",
"CsvDelimiter": ",",
"BucketFolder": "sourcedata",
"BucketName": "my-corp-data",
"CompressionType": "NONE",
"EnableStatistics": true
}
}
}
```
Per ulteriori informazioni, vedere [Working with AWS DMS Endpoints](https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Endpoints.html) nella *AWS Database Migration Service User Guide*.
+ Per i dettagli sull'API, consulta *AWS CLI Command [CreateEndpoint](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/dms/create-endpoint.html)Reference*.
### `create-event-subscription`
Il seguente esempio di codice mostra come utilizzare`create-event-subscription`.
**AWS CLI**
**Come elencare le sottoscrizioni agli eventi**
L'`create-event-subscription`esempio seguente crea una sottoscrizione a un evento a un argomento Amazon SNS ()my-sns-topic.
```
aws dms create-event-subscription \
--subscription-name my-dms-events \
--sns-topic-arn arn:aws:sns:us-east-1:123456789012:my-sns-topic
```
Output:
```
{
"EventSubscription": {
"CustomerAwsId": "123456789012",
"CustSubscriptionId": "my-dms-events",
"SnsTopicArn": "arn:aws:sns:us-east-1:123456789012:my-sns-topic",
"Status": "creating",
"SubscriptionCreationTime": "2020-05-21 21:58:38.598",
"Enabled": true
}
}
```
Per ulteriori informazioni, consulta [Utilizzo di eventi e notifiche](https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Events.html) nella *Guida per l’utente di AWS Database Migration Service*.
+ Per i dettagli sull'API, consulta [CreateEventSubscription AWS CLI](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/dms/create-event-subscription.html)*Command Reference.*
### `create-replication-instance`
Il seguente esempio di codice mostra come utilizzare`create-replication-instance`.
**AWS CLI**
**Come creare un’istanza di replica**
L’esempio `create-replication-instance` seguente crea un’istanza di replica.
```
aws dms create-replication-instance \
--replication-instance-identifier my-repl-instance \
--replication-instance-class dms.t2.micro \
--allocated-storage 5
```
Output:
```
{
"ReplicationInstance": {
"ReplicationInstanceIdentifier": "my-repl-instance",
"ReplicationInstanceClass": "dms.t2.micro",
"ReplicationInstanceStatus": "creating",
"AllocatedStorage": 5,
"VpcSecurityGroups": [
{
"VpcSecurityGroupId": "sg-f839b688",
"Status": "active"
}
],
"ReplicationSubnetGroup": {
"ReplicationSubnetGroupIdentifier": "default",
"ReplicationSubnetGroupDescription": "default",
"VpcId": "vpc-136a4c6a",
"SubnetGroupStatus": "Complete",
"Subnets": [
{
"SubnetIdentifier": "subnet-da327bf6",
"SubnetAvailabilityZone": {
"Name": "us-east-1a"
},
"SubnetStatus": "Active"
},
{
"SubnetIdentifier": "subnet-42599426",
"SubnetAvailabilityZone": {
"Name": "us-east-1d"
},
"SubnetStatus": "Active"
},
{
"SubnetIdentifier": "subnet-bac383e0",
"SubnetAvailabilityZone": {
"Name": "us-east-1c"
},
"SubnetStatus": "Active"
},
{
"SubnetIdentifier": "subnet-6746046b",
"SubnetAvailabilityZone": {
"Name": "us-east-1f"
},
"SubnetStatus": "Active"
},
{
"SubnetIdentifier": "subnet-d7c825e8",
"SubnetAvailabilityZone": {
"Name": "us-east-1e"
},
"SubnetStatus": "Active"
},
{
"SubnetIdentifier": "subnet-cbfff283",
"SubnetAvailabilityZone": {
"Name": "us-east-1b"
},
"SubnetStatus": "Active"
}
]
},
"PreferredMaintenanceWindow": "sat:12:35-sat:13:05",
"PendingModifiedValues": {},
"MultiAZ": false,
"EngineVersion": "3.3.2",
"AutoMinorVersionUpgrade": true,
"KmsKeyId": "arn:aws:kms:us-east-1:123456789012:key/f7bc0f8e-1a3a-4ace-9faa-e8494fa3921a",
"ReplicationInstanceArn": "arn:aws:dms:us-east-1:123456789012:rep:ZK2VQBUWFDBAWHIXHAYG5G2PKY",
"PubliclyAccessible": true
}
}
```
Per ulteriori informazioni, vedere [Working with an AWS DMS Replication Instance](https://docs.aws.amazon.com/dms/latest/userguide/CHAP_ReplicationInstance.html) nella *AWS Database Migration Service User Guide*.
+ Per i dettagli sull'API, consulta *AWS CLI Command [CreateReplicationInstance](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/dms/create-replication-instance.html)Reference*.
### `create-replication-subnet-group`
Il seguente esempio di codice mostra come utilizzare`create-replication-subnet-group`.
**AWS CLI**
**Come creare un gruppo di sottoreti**
L’esempio `create-replication-subnet-group` seguente crea un gruppo composto da 3 sottoreti.
```
aws dms create-replication-subnet-group \
--replication-subnet-group-identifier my-subnet-group \
--replication-subnet-group-description "my subnet group" \
--subnet-ids subnet-da327bf6 subnet-bac383e0 subnet-d7c825e8
```
Output:
```
{
"ReplicationSubnetGroup": {
"ReplicationSubnetGroupIdentifier": "my-subnet-group",
"ReplicationSubnetGroupDescription": "my subnet group",
"VpcId": "vpc-136a4c6a",
"SubnetGroupStatus": "Complete",
"Subnets": [
{
"SubnetIdentifier": "subnet-da327bf6",
"SubnetAvailabilityZone": {
"Name": "us-east-1a"
},
"SubnetStatus": "Active"
},
{
"SubnetIdentifier": "subnet-bac383e0",
"SubnetAvailabilityZone": {
"Name": "us-east-1c"
},
"SubnetStatus": "Active"
},
{
"SubnetIdentifier": "subnet-d7c825e8",
"SubnetAvailabilityZone": {
"Name": "us-east-1e"
},
"SubnetStatus": "Active"
}
]
}
}
```
Per ulteriori informazioni, consulta [Impostazione di una rete per un’istanza di replica](https://docs.aws.amazon.com/dms/latest/userguide/CHAP_ReplicationInstance.VPC.html) nella *Guida per l’utente di AWS Database Migration Service*.
+ Per i dettagli sull'API, consulta [CreateReplicationSubnetGroup AWS CLI](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/dms/create-replication-subnet-group.html)*Command Reference*.
### `create-replication-task`
Il seguente esempio di codice mostra come utilizzare`create-replication-task`.
**AWS CLI**
**Come creare un’attività di replica**
L’esempio `create-replication-task` seguente crea un’attività di replica.
```
aws dms create-replication-task \
--replication-task-identifier movedata \
--source-endpoint-arn arn:aws:dms:us-east-1:123456789012:endpoint:6GGI6YPWWGAYUVLKIB732KEVWA \
--target-endpoint-arn arn:aws:dms:us-east-1:123456789012:endpoint:EOM4SFKCZEYHZBFGAGZT3QEC5U \
--replication-instance-arn $RI_ARN \
--migration-type full-load \
--table-mappings file://table-mappings.json
```
Contenuto di `table-mappings.json`:
```
{
"rules": [
{
"rule-type": "selection",
"rule-id": "1",
"rule-name": "1",
"object-locator": {
"schema-name": "prodrep",
"table-name": "%"
},
"rule-action": "include",
"filters": []
}
]
}
```
Output:
```
{
"ReplicationTask": {
"ReplicationTaskIdentifier": "moveit2",
"SourceEndpointArn": "arn:aws:dms:us-east-1:123456789012:endpoint:6GGI6YPWWGAYUVLKIB732KEVWA",
"TargetEndpointArn": "arn:aws:dms:us-east-1:123456789012:endpoint:EOM4SFKCZEYHZBFGAGZT3QEC5U",
"ReplicationInstanceArn": "arn:aws:dms:us-east-1:123456789012:rep:T3OM7OUB5NM2LCVZF7JPGJRNUE",
"MigrationType": "full-load",
"TableMappings": ...output omitted... ,
"ReplicationTaskSettings": ...output omitted... ,
"Status": "creating",
"ReplicationTaskCreationDate": 1590524772.505,
"ReplicationTaskArn": "arn:aws:dms:us-east-1:123456789012:task:K55IUCGBASJS5VHZJIINA45FII"
}
}
```
Per ulteriori informazioni, vedere [Working with AWS DMS Tasks](https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Tasks.html) nella *AWS Database Migration Service User Guide*.
+ Per i dettagli sull'API, consulta [CreateReplicationTask AWS CLI](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/dms/create-replication-task.html)*Command Reference.*
### `delete-connection`
Il seguente esempio di codice mostra come utilizzare`delete-connection`.
**AWS CLI**
**Come eliminare una connessione**
L’esempio `delete-connection` seguente dissocia un endpoint da un’istanza di replica.
```
aws dms delete-connection \
--endpoint-arn arn:aws:dms:us-east-1:123456789012:endpoint:6GGI6YPWWGAYUVLKIB732KEVWA \
--replication-instance-arn arn:aws:dms:us-east-1:123456789012:rep:T3OM7OUB5NM2LCVZF7JPGJRNUE
```
Output:
```
{
"Connection": {
"ReplicationInstanceArn": "arn:aws:dms:us-east-1:123456789012:rep:T3OM7OUB5NM2LCVZF7JPGJRNUE",
"EndpointArn": "arn:aws:dms:us-east-1:123456789012:endpoint:6GGI6YPWWGAYUVLKIB732KEVWA",
"Status": "deleting",
"EndpointIdentifier": "src-database-1",
"ReplicationInstanceIdentifier": "my-repl-instance"
}
}
```
*Per ulteriori informazioni, vedere [https://docs.aws.amazon.com/dms/latest/userguide/CHAP\$1endpoints.creating.html nella Database Migration AWS Service User](https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Endpoints.Creating.html) Guide.*
+ *Per i dettagli sull'API, consulta Command Reference. [DeleteConnection](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/dms/delete-connection.html)AWS CLI *
### `delete-endpoint`
Il seguente esempio di codice mostra come utilizzare`delete-endpoint`.
**AWS CLI**
**Come eliminare un endpoint**
L’esempio `delete-endpoint` seguente elimina un endpoint.
```
aws dms delete-endpoint \
--endpoint-arn arn:aws:dms:us-east-1:123456789012:endpoint:OUJJVXO4XZ4CYTSEG5XGMN2R3Y
```
Output:
```
{
"Endpoint": {
"EndpointIdentifier": "src-endpoint",
"EndpointType": "SOURCE",
"EngineName": "s3",
"EngineDisplayName": "Amazon S3",
"ExtraConnectionAttributes": "bucketFolder=sourcedata;bucketName=my-corp-data;compressionType=NONE;csvDelimiter=,;csvRowDelimiter=\\n;",
"Status": "deleting",
"EndpointArn": "arn:aws:dms:us-east-1:123456789012:endpoint:OUJJVXO4XZ4CYTSEG5XGMN2R3Y",
"SslMode": "none",
"ServiceAccessRoleArn": "arn:aws:iam::123456789012:role/my-s3-access-role",
"S3Settings": {
"ServiceAccessRoleArn": "arn:aws:iam::123456789012:role/my-s3-access-role",
"CsvRowDelimiter": "\\n",
"CsvDelimiter": ",",
"BucketFolder": "sourcedata",
"BucketName": "my-corp-data",
"CompressionType": "NONE",
"EnableStatistics": true
}
}
}
```
Per ulteriori informazioni, vedere [Working with AWS DMS Endpoints](https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Endpoints.html) nella *AWS Database Migration Service User Guide*.
+ Per i dettagli sull'API, consulta *AWS CLI Command [DeleteEndpoint](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/dms/delete-endpoint.html)Reference*.
### `delete-event-subscription`
Il seguente esempio di codice mostra come utilizzare`delete-event-subscription`.
**AWS CLI**
**Come eliminare un abbonamento all’evento**
L’esempio `delete-event-subscription` seguente elimina un abbonamento a un argomento Amazon SNS.
```
aws dms delete-event-subscription \
--subscription-name "my-dms-events"
```
Output:
```
{
"EventSubscription": {
"CustomerAwsId": "123456789012",
"CustSubscriptionId": "my-dms-events",
"SnsTopicArn": "arn:aws:sns:us-east-1:123456789012:my-sns-topic",
"Status": "deleting",
"SubscriptionCreationTime": "2020-05-21 21:58:38.598",
"Enabled": true
}
}
```
Per ulteriori informazioni, consulta [Utilizzo di eventi e notifiche](https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Events.html) nella *Guida per l’utente di AWS Database Migration Service*.
+ Per i dettagli sull'API, consulta [DeleteEventSubscription AWS CLI](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/dms/delete-event-subscription.html)*Command Reference*.
### `delete-replication-instance`
Il seguente esempio di codice mostra come utilizzare`delete-replication-instance`.
**AWS CLI**
**Come eliminare un’istanza di replica**
L’esempio `delete-replication-instance` seguente elimina un’istanza di replica.
```
aws dms delete-replication-instance \
--replication-instance-arn arn:aws:dms:us-east-1:123456789012:rep:T3OM7OUB5NM2LCVZF7JPGJRNUE
```
Output:
```
{
"ReplicationInstance": {
"ReplicationInstanceIdentifier": "my-repl-instance",
"ReplicationInstanceClass": "dms.t2.micro",
"ReplicationInstanceStatus": "deleting",
"AllocatedStorage": 5,
"InstanceCreateTime": 1590011235.952,
"VpcSecurityGroups": [
{
"VpcSecurityGroupId": "sg-f839b688",
"Status": "active"
}
],
"AvailabilityZone": "us-east-1e",
"ReplicationSubnetGroup": {
"ReplicationSubnetGroupIdentifier": "default",
"ReplicationSubnetGroupDescription": "default",
"VpcId": "vpc-136a4c6a",
"SubnetGroupStatus": "Complete",
"Subnets": [
{
"SubnetIdentifier": "subnet-da327bf6",
"SubnetAvailabilityZone": {
"Name": "us-east-1a"
},
"SubnetStatus": "Active"
},
{
"SubnetIdentifier": "subnet-42599426",
"SubnetAvailabilityZone": {
"Name": "us-east-1d"
},
"SubnetStatus": "Active"
},
{
"SubnetIdentifier": "subnet-bac383e0",
"SubnetAvailabilityZone": {
"Name": "us-east-1c"
},
"SubnetStatus": "Active"
},
{
"SubnetIdentifier": "subnet-6746046b",
"SubnetAvailabilityZone": {
"Name": "us-east-1f"
},
"SubnetStatus": "Active"
},
{
"SubnetIdentifier": "subnet-d7c825e8",
"SubnetAvailabilityZone": {
"Name": "us-east-1e"
},
"SubnetStatus": "Active"
},
{
"SubnetIdentifier": "subnet-cbfff283",
"SubnetAvailabilityZone": {
"Name": "us-east-1b"
},
"SubnetStatus": "Active"
}
]
},
"PreferredMaintenanceWindow": "wed:11:42-wed:12:12",
"PendingModifiedValues": {},
"MultiAZ": true,
"EngineVersion": "3.3.2",
"AutoMinorVersionUpgrade": true,
"KmsKeyId": "arn:aws:kms:us-east-1:123456789012:key/f7bc0f8e-1a3a-4ace-9faa-e8494fa3921a",
"ReplicationInstanceArn": "arn:aws:dms:us-east-1:123456789012:rep:T3OM7OUB5NM2LCVZF7JPGJRNUE",
"ReplicationInstancePublicIpAddress": "54.225.120.92",
"ReplicationInstancePrivateIpAddress": "172.31.30.121",
"ReplicationInstancePublicIpAddresses": [
"54.225.120.92",
"3.230.18.248"
],
"ReplicationInstancePrivateIpAddresses": [
"172.31.30.121",
"172.31.75.90"
],
"PubliclyAccessible": true,
"SecondaryAvailabilityZone": "us-east-1b"
}
}
```
Per ulteriori informazioni, vedere [Working with an AWS DMS Replication Instance](https://docs.aws.amazon.com/dms/latest/userguide/CHAP_ReplicationInstance.html) nella *AWS Database Migration Service User Guide*.
+ Per i dettagli sull'API, consulta *AWS CLI Command [DeleteReplicationInstance](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/dms/delete-replication-instance.html)Reference*.
### `delete-replication-subnet-group`
Il seguente esempio di codice mostra come utilizzare`delete-replication-subnet-group`.
**AWS CLI**
**Come eliminare un gruppo di sottoreti**
L’esempio `delete-replication-subnet-group` seguente elimina un gruppo di sottoreti.
```
aws dms delete-replication-subnet-group \
--replication-subnet-group-identifier my-subnet-group
```
Output:
```
(none)
```
Per ulteriori informazioni, consulta [Impostazione di una rete per un’istanza di replica](https://docs.aws.amazon.com/dms/latest/userguide/CHAP_ReplicationInstance.VPC.html) nella *Guida per l’utente di AWS Database Migration Service*.
+ Per i dettagli sull'API, consulta [DeleteReplicationSubnetGroup AWS CLI](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/dms/delete-replication-subnet-group.html)*Command Reference*.
### `delete-replication-task`
Il seguente esempio di codice mostra come utilizzare`delete-replication-task`.
**AWS CLI**
**Come eliminare un’attività di replica**
L’esempio `delete-replication-task` seguente elimina un’istanza di replica.
```
aws dms delete-replication-task \
--replication-task-arn arn:aws:dms:us-east-1:123456789012:task:K55IUCGBASJS5VHZJIINA45FII
```
Output:
```
{
"ReplicationTask": {
"ReplicationTaskIdentifier": "moveit2",
"SourceEndpointArn": "arn:aws:dms:us-east-1:123456789012:endpoint:6GGI6YPWWGAYUVLKIB732KEVWA",
"TargetEndpointArn": "arn:aws:dms:us-east-1:123456789012:endpoint:EOM4SFKCZEYHZBFGAGZT3QEC5U",
"ReplicationInstanceArn": "arn:aws:dms:us-east-1:123456789012:rep:T3OM7OUB5NM2LCVZF7JPGJRNUE",
"MigrationType": "full-load",
"TableMappings": ...output omitted...,
"ReplicationTaskSettings": ...output omitted...,
"Status": "deleting",
"StopReason": "Stop Reason FULL_LOAD_ONLY_FINISHED",
"ReplicationTaskCreationDate": 1590524772.505,
"ReplicationTaskStartDate": 1590789988.677,
"ReplicationTaskArn": "arn:aws:dms:us-east-1:123456789012:task:K55IUCGBASJS5VHZJIINA45FII"
}
}
```
Per ulteriori informazioni, vedere [Working with AWS DMS Tasks](https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Tasks.html) nella *AWS Database Migration Service User Guide*.
+ Per i dettagli sull'API, consulta [DeleteReplicationTask AWS CLI](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/dms/delete-replication-task.html)*Command Reference.*
### `describe-account-attributes`
Il seguente esempio di codice mostra come utilizzare`describe-account-attributes`.
**AWS CLI**
**Come descrivere gli attributi dell’account**
L'`describe-account-attributes`esempio seguente elenca gli attributi del tuo AWS account.
```
aws dms describe-account-attributes
```
Output:
```
{
"AccountQuotas": [
{
"AccountQuotaName": "ReplicationInstances",
"Used": 1,
"Max": 20
},
{
"AccountQuotaName": "AllocatedStorage",
"Used": 5,
"Max": 10000
},
...remaining output omitted...
],
"UniqueAccountIdentifier": "cqahfbfy5xee"
}
```
+ Per i dettagli sull'API, consulta [DescribeAccountAttributes AWS CLI](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/dms/describe-account-attributes.html)*Command Reference*.
### `describe-certificates`
Il seguente esempio di codice mostra come utilizzare`describe-certificates`.
**AWS CLI**
**Come elencare i certificati disponibili**
L'`describe-certificates`esempio seguente elenca i certificati disponibili nel tuo AWS account.
```
aws dms describe-certificates
```
Output:
```
{
"Certificates": [
{
"CertificateIdentifier": "my-cert",
"CertificateCreationDate": 1543259542.506,
"CertificatePem": "-----BEGIN CERTIFICATE-----\nMIID9DCCAtygAwIBAgIBQjANBgkqhkiG9w0BAQ ...U"
... remaining output omittted ...
}
]
}
```
Per ulteriori informazioni, consulta [Utilizzo di SSL](https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Security.html#CHAP_Security.SSL) nella *Guida per l’utente di AWS Database Migration Service*.
+ Per i dettagli sull'API, consulta [DescribeCertificates AWS CLI](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/dms/describe-certificates.html)*Command Reference*.
### `describe-connections`
Il seguente esempio di codice mostra come utilizzare`describe-connections`.
**AWS CLI**
**Come descrivere le connessioni**
L’esempio `describe-connections` seguente elenca le connessioni che sono state testate tra un’istanza di replica e un endpoint.
```
aws dms describe-connections
```
Output:
```
{
"Connections": [
{
"Status": "successful",
"ReplicationInstanceIdentifier": "test",
"EndpointArn": "arn:aws:dms:us-east-arn:aws:dms:us-east-1:123456789012:endpoint:ZW5UAN6P4E77EC7YWHK4RZZ3BE",
"EndpointIdentifier": "testsrc1",
"ReplicationInstanceArn": "arn:aws:dms:us-east-1:123456789012:rep:6UTDJGBOUS3VI3SUWA66XFJCJQ"
}
]
}
```
Per ulteriori informazioni, consulta [Creazione di endpoint sorgente e obiettivo](https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Endpoints.Creating.html) nella *Guida per l’utente di AWS Database Migration Service*.
+ Per i dettagli sull'API, consulta [DescribeConnections AWS CLI](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/dms/describe-connections.html)*Command Reference*.
### `describe-endpoint-types`
Il seguente esempio di codice mostra come utilizzare`describe-endpoint-types`.
**AWS CLI**
**Come elencare i tipi di endpoint disponibili**
L’esempio `describe-endpoint-types` seguente elenca i tipi di endpoint MySQL disponibili.
```
aws dms describe-endpoint-types \
--filters "Name=engine-name,Values=mysql"
```
Output:
```
{
"SupportedEndpointTypes": [
{
"EngineName": "mysql",
"SupportsCDC": true,
"EndpointType": "source",
"EngineDisplayName": "MySQL"
},
{
"EngineName": "mysql",
"SupportsCDC": true,
"EndpointType": "target",
"EngineDisplayName": "MySQL"
}
]
}
```
*Per ulteriori informazioni, vedere Working with AWS DMS Endpoints < https://docs.aws.amazon.com/dms/ latest/userguide/CHAP \$1endpoints.html>`\$1\$1 nella Database Migration Service User Guide.AWS *
+ Per *AWS CLI i* dettagli sull'API, consulta Command [DescribeEndpointTypes](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/dms/describe-endpoint-types.html)Reference.
### `describe-endpoints`
Il seguente esempio di codice mostra come utilizzare`describe-endpoints`.
**AWS CLI**
**Come descrivere gli endpoint**
L'`describe-endpoints`esempio seguente elenca gli endpoint del tuo AWS account.
```
aws dms describe-endpoints
```
Output:
```
{
"Endpoints": [
{
"Username": "dms",
"Status": "active",
"EndpointArn": "arn:aws:dms:us-east-1:123456789012:endpoint:SF2WOFLWYWKVEOHID2EKLP3SJI",
"ServerName": "ec2-52-32-48-61.us-west-2.compute.amazonaws.com",
"EndpointType": "SOURCE",
"KmsKeyId": "arn:aws:kms:us-east-1:123456789012:key/94d5c4e7-4e4c-44be-b58a-c8da7adf57cd",
"DatabaseName": "test",
"EngineName": "mysql",
"EndpointIdentifier": "pri100",
"Port": 8193
},
{
"Username": "admin",
"Status": "active",
"EndpointArn": "arn:aws:dms:us-east-1:123456789012:endpoint:TJJZCIH3CJ24TJRU4VC32WEWFR",
"ServerName": "test.example.com",
"EndpointType": "SOURCE",
"KmsKeyId": "arn:aws:kms:us-east-1:123456789012:key/2431021b-1cf2-a2d4-77b2-59a9e4bce323",
"DatabaseName": "EMPL",
"EngineName": "oracle",
"EndpointIdentifier": "test",
"Port": 1521
}
]
}
```
Per ulteriori informazioni, vedere [Working with AWS DMS Endpoints](https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Endpoints.html) nella *AWS Database Migration Service User Guide*.
+ Per i dettagli sull'API, consulta *AWS CLI Command [DescribeEndpoints](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/dms/describe-endpoints.html)Reference*.
### `describe-event-categories`
Il seguente esempio di codice mostra come utilizzare`describe-event-categories`.
**AWS CLI**
**Come descrivere le categorie di eventi**
L’esempio `describe-event-categories` seguente elenca le categorie di eventi disponibili.
```
aws dms describe-event-categories
```
Output:
```
{
"EventCategoryGroupList": [
{
"SourceType": "replication-instance",
"EventCategories": [
"low storage",
"configuration change",
"maintenance",
"deletion",
"creation",
"failover",
"failure"
]
},
{
"SourceType": "replication-task",
"EventCategories": [
"configuration change",
"state change",
"deletion",
"creation",
"failure"
]
}
]
}
```
Per ulteriori informazioni, consulta [Utilizzo di eventi e notifiche](https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Events.html) nella *Guida per l’utente di AWS Database Migration Service*.
+ Per i dettagli sull'API, consulta [DescribeEventCategories AWS CLI](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/dms/describe-event-categories.html)*Command Reference*.
### `describe-event-subscriptions`
Il seguente esempio di codice mostra come utilizzare`describe-event-subscriptions`.
**AWS CLI**
**Come descrivere le sottoscrizioni a eventi**
L’esempio `describe-event-subscriptions` seguente elenca gli abbonamenti agli eventi di un argomento Amazon SNS.
```
aws dms describe-event-subscriptions
```
Output:
```
{
"EventSubscriptionsList": [
{
"CustomerAwsId": "123456789012",
"CustSubscriptionId": "my-dms-events",
"SnsTopicArn": "arn:aws:sns:us-east-1:123456789012:my-sns-topic",
"Status": "deleting",
"SubscriptionCreationTime": "2020-05-21 22:28:51.924",
"Enabled": true
}
]
}
```
Per ulteriori informazioni, consulta [Utilizzo di eventi e notifiche](https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Events.html) nella *Guida per l’utente di AWS Database Migration Service*.
+ Per i dettagli sull'API, consulta [DescribeEventSubscriptions AWS CLI](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/dms/describe-event-subscriptions.html)*Command Reference*.
### `describe-events`
Il seguente esempio di codice mostra come utilizzare`describe-events`.
**AWS CLI**
**Come elencare gli eventi DMS**
L’esempio `describe-events` seguente elenca gli eventi che hanno avuto origine da un’istanza di replica.
```
aws dms describe-events \
--source-type "replication-instance"
```
Output:
```
{
"Events": [
{
"SourceIdentifier": "my-repl-instance",
"SourceType": "replication-instance",
"Message": "Replication application shutdown",
"EventCategories": [],
"Date": 1590771645.776
}
]
}
```
Per ulteriori informazioni, consulta [Utilizzo di eventi e notifiche](https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Events.html) nella *Guida per l’utente di AWS Database Migration Service*.
+ Per i dettagli sull'API, consulta [DescribeEvents AWS CLI](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/dms/describe-events.html)*Command Reference*.
### `describe-orderable-replication-instances`
Il seguente esempio di codice mostra come utilizzare`describe-orderable-replication-instances`.
**AWS CLI**
**Come descrivere le istanze di replica ordinabili**
L’esempio `describe-orderable-replication-instances` seguente elenca i tipi di istanze di replica che è possibile ordinare.
```
aws dms describe-orderable-replication-instances
```
Output:
```
{
"OrderableReplicationInstances": [
{
"EngineVersion": "3.3.2",
"ReplicationInstanceClass": "dms.c4.2xlarge",
"StorageType": "gp2",
"MinAllocatedStorage": 5,
"MaxAllocatedStorage": 6144,
"DefaultAllocatedStorage": 100,
"IncludedAllocatedStorage": 100,
"AvailabilityZones": [
"us-east-1a",
"us-east-1b",
"us-east-1c",
"us-east-1d",
"us-east-1e",
"us-east-1f"
]
},
{
"EngineVersion": "3.3.2",
"ReplicationInstanceClass": "dms.c4.4xlarge",
"StorageType": "gp2",
"MinAllocatedStorage": 5,
"MaxAllocatedStorage": 6144,
"DefaultAllocatedStorage": 100,
"IncludedAllocatedStorage": 100,
"AvailabilityZones": [
"us-east-1a",
"us-east-1b",
"us-east-1c",
"us-east-1d",
"us-east-1e",
"us-east-1f"
]
},
...remaining output omitted...
}
```
Per ulteriori informazioni, vedere [Working with an AWS DMS Replication Instance](https://docs.aws.amazon.com/dms/latest/userguide/CHAP_ReplicationInstance.html) nella *AWS Database Migration Service User Guide*.
+ Per i dettagli sull'API, consulta *AWS CLI Command [DescribeOrderableReplicationInstances](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/dms/describe-orderable-replication-instances.html)Reference*.
### `describe-refresh-schemas-status`
Il seguente esempio di codice mostra come utilizzare`describe-refresh-schemas-status`.
**AWS CLI**
**Come elencare lo stato di aggiornamento di un endpoint**
L’esempio `describe-refresh-schemas-status` seguente restituisce lo stato di una precedente richiesta di aggiornamento.
```
aws dms describe-refresh-schemas-status \
--endpoint-arn arn:aws:dms:us-east-1:123456789012:endpoint:6GGI6YPWWGAYUVLKIB732KEVWA
```
Output:
```
{
"RefreshSchemasStatus": {
"EndpointArn": "arn:aws:dms:us-east-1:123456789012:endpoint:6GGI6YPWWGAYUVLKIB732KEVWA",
"ReplicationInstanceArn": "arn:aws:dms:us-east-1:123456789012:rep:T3OM7OUB5NM2LCVZF7JPGJRNUE",
"Status": "successful",
"LastRefreshDate": 1590786544.605
}
}
```
+ Per i dettagli sull'API, consulta [DescribeRefreshSchemasStatus AWS CLI](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/dms/describe-refresh-schemas-status.html)*Command Reference*.
### `describe-replication-instances`
Il seguente esempio di codice mostra come utilizzare`describe-replication-instances`.
**AWS CLI**
**Come descrivere le istanze di replica**
L'`describe-replication-instances`esempio seguente elenca le istanze di replica presenti nell'account AWS .
```
aws dms describe-replication-instances
```
Output:
```
{
"ReplicationInstances": [
{
"ReplicationInstanceIdentifier": "my-repl-instance",
"ReplicationInstanceClass": "dms.t2.micro",
"ReplicationInstanceStatus": "available",
"AllocatedStorage": 5,
"InstanceCreateTime": 1590011235.952,
"VpcSecurityGroups": [
{
"VpcSecurityGroupId": "sg-f839b688",
"Status": "active"
}
],
"AvailabilityZone": "us-east-1e",
"ReplicationSubnetGroup": {
"ReplicationSubnetGroupIdentifier": "default",
"ReplicationSubnetGroupDescription": "default",
"VpcId": "vpc-136a4c6a",
"SubnetGroupStatus": "Complete",
"Subnets": [
{
"SubnetIdentifier": "subnet-da327bf6",
"SubnetAvailabilityZone": {
"Name": "us-east-1a"
},
"SubnetStatus": "Active"
},
{
"SubnetIdentifier": "subnet-42599426",
"SubnetAvailabilityZone": {
"Name": "us-east-1d"
},
"SubnetStatus": "Active"
},
{
"SubnetIdentifier": "subnet-bac383e0",
"SubnetAvailabilityZone": {
"Name": "us-east-1c"
},
"SubnetStatus": "Active"
},
{
"SubnetIdentifier": "subnet-6746046b",
"SubnetAvailabilityZone": {
"Name": "us-east-1f"
},
"SubnetStatus": "Active"
},
{
"SubnetIdentifier": "subnet-d7c825e8",
"SubnetAvailabilityZone": {
"Name": "us-east-1e"
},
"SubnetStatus": "Active"
},
{
"SubnetIdentifier": "subnet-cbfff283",
"SubnetAvailabilityZone": {
"Name": "us-east-1b"
},
"SubnetStatus": "Active"
}
]
},
"PreferredMaintenanceWindow": "wed:11:42-wed:12:12",
"PendingModifiedValues": {
"MultiAZ": true
},
"MultiAZ": false,
"EngineVersion": "3.3.2",
"AutoMinorVersionUpgrade": true,
"KmsKeyId": "arn:aws:kms:us-east-1:123456789012:key/f7bc0f8e-1a3a-4ace-9faa-e8494fa3921a",
"ReplicationInstanceArn": "arn:aws:dms:us-east-1:123456789012:rep:T3OM7OUB5NM2LCVZF7JPGJRNUE",
"ReplicationInstancePublicIpAddress": "3.230.18.248",
"ReplicationInstancePrivateIpAddress": "172.31.75.90",
"ReplicationInstancePublicIpAddresses": [
"3.230.18.248"
],
"ReplicationInstancePrivateIpAddresses": [
"172.31.75.90"
],
"PubliclyAccessible": true,
"FreeUntil": 1590194829.267
}
]
}
```
Per ulteriori informazioni, vedere [Working with an AWS DMS Replication Instance](https://docs.aws.amazon.com/dms/latest/userguide/CHAP_ReplicationInstance.html) nella *AWS Database Migration Service User Guide*.
+ Per i dettagli sull'API, consulta *AWS CLI Command [DescribeReplicationInstances](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/dms/describe-replication-instances.html)Reference*.
### `describe-replication-subnet-groups`
Il seguente esempio di codice mostra come utilizzare`describe-replication-subnet-groups`.
**AWS CLI**
**Come visualizzare i gruppi di sottoreti disponibili**
L’esempio `describe-replication-subnet-groups` seguente elenca i gruppi di sottoreti disponibili.
```
aws dms describe-replication-subnet-groups \
--filter "Name=replication-subnet-group-id,Values=my-subnet-group"
```
Output:
```
{
"ReplicationSubnetGroups": [
{
"ReplicationSubnetGroupIdentifier": "my-subnet-group",
"ReplicationSubnetGroupDescription": "my subnet group",
"VpcId": "vpc-136a4c6a",
"SubnetGroupStatus": "Complete",
"Subnets": [
{
"SubnetIdentifier": "subnet-da327bf6",
"SubnetAvailabilityZone": {
"Name": "us-east-1a"
},
"SubnetStatus": "Active"
},
{
"SubnetIdentifier": "subnet-bac383e0",
"SubnetAvailabilityZone": {
"Name": "us-east-1c"
},
"SubnetStatus": "Active"
},
{
"SubnetIdentifier": "subnet-d7c825e8",
"SubnetAvailabilityZone": {
"Name": "us-east-1e"
},
"SubnetStatus": "Active"
}
]
}
]
}
```
Per ulteriori informazioni, consulta [Impostazione di una rete per un’istanza di replica](https://docs.aws.amazon.com/dms/latest/userguide/CHAP_ReplicationInstance.VPC.html) nella *Guida per l’utente di AWS Database Migration Service*.
+ Per i dettagli sull'API, consulta [DescribeReplicationSubnetGroups AWS CLI](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/dms/describe-replication-subnet-groups.html)*Command Reference*.
### `describe-replication-task-assessment-results`
Il seguente esempio di codice mostra come utilizzare`describe-replication-task-assessment-results`.
**AWS CLI**
**Come elencare i risultati delle valutazioni delle attività di replica**
L’esempio `describe-replication-task-assessment-results` seguente elenca i risultati di una precedente valutazione delle attività.
```
aws dms describe-replication-task-assessment-results
```
Output:
```
{
"ReplicationTaskAssessmentResults": [
{
"ReplicationTaskIdentifier": "moveit2",
"ReplicationTaskArn": "arn:aws:dms:us-east-1:123456789012:task:K55IUCGBASJS5VHZJIINA45FII",
"ReplicationTaskLastAssessmentDate": 1590790230.0,
"AssessmentStatus": "No issues found",
"AssessmentResultsFile": "moveit2/2020-05-29-22-10"
}
]
}
```
Per ulteriori informazioni, consulta [Creazione di un report di valutazione del task](https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Tasks.AssessmentReport.html) nella *Guida per l’utente di AWS Database Migration Service*.
+ Per i dettagli sull'API, consulta [DescribeReplicationTaskAssessmentResults AWS CLI](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/dms/describe-replication-task-assessment-results.html)*Command Reference*.
### `describe-replication-tasks`
Il seguente esempio di codice mostra come utilizzare`describe-replication-tasks`.
**AWS CLI**
**Come descrivere un’attività di replica**
L’esempio `describe-replication-tasks` seguente descrive le attività di replica correnti.
```
aws dms describe-replication-tasks
```
Output:
```
{
"ReplicationTasks": [
{
"ReplicationTaskIdentifier": "moveit2",
"SourceEndpointArn": "arn:aws:dms:us-east-1:123456789012:endpoint:6GGI6YPWWGAYUVLKIB732KEVWA",
"TargetEndpointArn": "arn:aws:dms:us-east-1:123456789012:endpoint:EOM4SFKCZEYHZBFGAGZT3QEC5U",
"ReplicationInstanceArn": "arn:aws:dms:us-east-1:123456789012:rep:T3OM7OUB5NM2LCVZF7JPGJRNUE",
"MigrationType": "full-load",
"TableMappings": ...output omitted... ,
"ReplicationTaskSettings": ...output omitted... ,
"Status": "stopped",
"StopReason": "Stop Reason FULL_LOAD_ONLY_FINISHED",
"ReplicationTaskCreationDate": 1590524772.505,
"ReplicationTaskStartDate": 1590619805.212,
"ReplicationTaskArn": "arn:aws:dms:us-east-1:123456789012:task:K55IUCGBASJS5VHZJIINA45FII",
"ReplicationTaskStats": {
"FullLoadProgressPercent": 100,
"ElapsedTimeMillis": 0,
"TablesLoaded": 0,
"TablesLoading": 0,
"TablesQueued": 0,
"TablesErrored": 0,
"FreshStartDate": 1590619811.528,
"StartDate": 1590619811.528,
"StopDate": 1590619842.068
}
}
]
}
```
Per ulteriori informazioni, vedere [Working with AWS DMS Tasks](https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Tasks.html) nella *AWS Database Migration Service User Guide*.
+ Per i dettagli sull'API, consulta [DescribeReplicationTasks AWS CLI](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/dms/describe-replication-tasks.html)*Command Reference.*
### `describe-schemas`
Il seguente esempio di codice mostra come utilizzare`describe-schemas`.
**AWS CLI**
**Per descrivere gli schemi dei database**
L’esempio `describe-schemas` seguente elenca le tabelle disponibili in un endpoint.
```
aws dms describe-schemas \
--endpoint-arn "arn:aws:dms:us-east-1:123456789012:endpoint:6GGI6YPWWGAYUVLKIB732KEVWA"
```
Output:
```
{
"Schemas": [
"prodrep"
]
}
```
Per ulteriori informazioni, consulta il [seguente argomento](https://link.to.the/topic/page) nella *Guida per l’utente di AWS Database Migration Service*.
+ Per i dettagli sull'API, vedere [DescribeSchemas](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/dms/describe-schemas.html)in *AWS CLI Command Reference.*
### `list-tags-for-resource`
Il seguente esempio di codice mostra come utilizzare`list-tags-for-resource`.
**AWS CLI**
**Come elencare i tag per una risorsa**
L’esempio `list-tags-for-resource` seguente elenca tutti i tag associati a un’istanza di replica.
```
aws dms list-tags-for-resource \
--resource-arn arn:aws:dms:us-east-1:123456789012:rep:T3OM7OUB5NM2LCVZF7JPGJRNUE
```
Output:
```
{
"TagList": [
{
"Key": "Project",
"Value": "dbMigration"
},
{
"Key": "Environment",
"Value": "PROD"
}
]
}
```
Per ulteriori informazioni, consulta [Assegnazione di tag alle risorse](https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Tagging.html) nella *Guida per l’utente di AWS Database Migration Service*.
+ Per i dettagli sull'API, consulta [ListTagsForResource AWS CLI](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/dms/list-tags-for-resource.html)*Command Reference*.
### `modify-endpoint`
Il seguente esempio di codice mostra come utilizzare`modify-endpoint`.
**AWS CLI**
**Come modificare un endpoint**
L’esempio `modify-endpoint` seguente aggiunge un attributo di connessione aggiuntivo a un endpoint.
```
aws dms modify-endpoint \
--endpoint-arn "arn:aws:dms:us-east-1:123456789012:endpoint:GUVAFG34EECUOJ6QVZ56DAHT3U" \
--extra-connection-attributes "compressionType=GZIP"
```
Output:
```
{
"Endpoint": {
"EndpointIdentifier": "src-endpoint",
"EndpointType": "SOURCE",
"EngineName": "s3",
"EngineDisplayName": "Amazon S3",
"ExtraConnectionAttributes": "compressionType=GZIP;csvDelimiter=,;csvRowDelimiter=\\n;",
"Status": "active",
"EndpointArn": "arn:aws:dms:us-east-1:123456789012:endpoint:GUVAFG34EECUOJ6QVZ56DAHT3U",
"SslMode": "none",
"ServiceAccessRoleArn": "arn:aws:iam::123456789012:role/my-s3-access-role",
"S3Settings": {
"ServiceAccessRoleArn": "arn:aws:iam::123456789012:role/my-s3-access-role",
"CsvRowDelimiter": "\\n",
"CsvDelimiter": ",",
"BucketFolder": "",
"BucketName": "",
"CompressionType": "GZIP",
"EnableStatistics": true
}
}
}
```
*Per ulteriori informazioni, vedere Working with AWS DMS Endpoints < https://docs.aws.amazon.com/dms/ latest/userguide/CHAP \$1endpoints.html>`\$1\$1 nella Database Migration Service User Guide.AWS *
+ Per *AWS CLI i* dettagli sull'API, consulta Command [ModifyEndpoint](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/dms/modify-endpoint.html)Reference.
### `modify-event-subscription`
Il seguente esempio di codice mostra come utilizzare`modify-event-subscription`.
**AWS CLI**
**Come modificare un abbonamento all’evento**
L’esempio `modify-event-subscription` seguente modifica il tipo di origine di una sottoscrizione a un evento.
```
aws dms modify-event-subscription \
--subscription-name "my-dms-events" \
--source-type replication-task
```
Output:
```
{
"EventSubscription": {
"CustomerAwsId": "123456789012",
"CustSubscriptionId": "my-dms-events",
"SnsTopicArn": "arn:aws:sns:us-east-1:123456789012:my-sns-topic",
"Status": "modifying",
"SubscriptionCreationTime": "2020-05-29 17:04:40.262",
"SourceType": "replication-task",
"Enabled": true
}
}
```
Per ulteriori informazioni, consulta [Utilizzo di eventi e notifiche](https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Events.html) nella *Guida per l’utente di AWS Database Migration Service*.
+ Per i dettagli sull'API, consulta [ModifyEventSubscription AWS CLI](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/dms/modify-event-subscription.html)*Command Reference*.
### `modify-replication-instance`
Il seguente esempio di codice mostra come utilizzare`modify-replication-instance`.
**AWS CLI**
**Come modificare un’istanza di replica**
L’esempio `modify-replication-instance` seguente modifica un’istanza di replica in modo che utilizzi un’implementazione Multi-AZ.
```
aws dms modify-replication-instance \
--replication-instance-arn arn:aws:dms:us-east-1:123456789012:rep:T3OM7OUB5NM2LCVZF7JPGJRNUE \
--multi-az
```
Output:
```
{
"ReplicationInstance": {
"ReplicationInstanceIdentifier": "my-repl-instance",
"ReplicationInstanceClass": "dms.t2.micro",
"ReplicationInstanceStatus": "available",
"AllocatedStorage": 5,
"InstanceCreateTime": 1590011235.952,
...output omitted...
"PendingModifiedValues": {
"MultiAZ": true
},
"MultiAZ": false,
"EngineVersion": "3.3.2",
"AutoMinorVersionUpgrade": true,
"KmsKeyId": "arn:aws:kms:us-east-1:123456789012:key/f7bc0f8e-1a3a-4ace-9faa-e8494fa3921a",
...output omitted...
}
}
```
Per ulteriori informazioni, vedere [Working with an AWS DMS Replication Instance](https://docs.aws.amazon.com/dms/latest/userguide/CHAP_ReplicationInstance.html) nella *AWS Database Migration Service User Guide*.
+ Per i dettagli sull'API, consulta *AWS CLI Command [ModifyReplicationInstance](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/dms/modify-replication-instance.html)Reference*.
### `modify-replication-subnet-group`
Il seguente esempio di codice mostra come utilizzare`modify-replication-subnet-group`.
**AWS CLI**
**Come modificare un gruppo di sottoreti**
L’esempio `modify-replication-subnet-group` seguente modifica gli elenchi delle sottoreti associate a un gruppo di sottoreti.
```
aws dms modify-replication-subnet-group \
--replication-subnet-group-identifier my-subnet-group \
--subnet-id subnet-da327bf6 subnet-bac383e0
```
Output:
```
{
"ReplicationSubnetGroup": {
"ReplicationSubnetGroupIdentifier": "my-subnet-group",
"ReplicationSubnetGroupDescription": "my subnet group",
"VpcId": "vpc-136a4c6a",
"SubnetGroupStatus": "Complete",
"Subnets": [
{
"SubnetIdentifier": "subnet-da327bf6",
"SubnetAvailabilityZone": {
"Name": "us-east-1a"
},
"SubnetStatus": "Active"
},
{
"SubnetIdentifier": "subnet-bac383e0",
"SubnetAvailabilityZone": {
"Name": "us-east-1c"
},
"SubnetStatus": "Active"
}
]
}
}
```
Per ulteriori informazioni, consulta [Impostazione di una rete per un’istanza di replica](https://docs.aws.amazon.com/dms/latest/userguide/CHAP_ReplicationInstance.VPC.html) nella *Guida per l’utente di AWS Database Migration Service*.
+ Per i dettagli sull'API, consulta [ModifyReplicationSubnetGroup AWS CLI](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/dms/modify-replication-subnet-group.html)*Command Reference*.
### `modify-replication-task`
Il seguente esempio di codice mostra come utilizzare`modify-replication-task`.
**AWS CLI**
**Come modificare un’attività di replica**
L’esempio `modify-replication-task` seguente modifica i mapping delle tabelle per un’attività.
```
aws dms modify-replication-task \
--replication-task-arn "arn:aws:dms:us-east-1:123456789012:task:K55IUCGBASJS5VHZJIINA45FII" \
--table-mappings file://table-mappings.json
```
Contenuto di `table-mappings.json`:
```
{
"rules": [
{
"rule-type": "selection",
"rule-id": "1",
"rule-name": "1",
"object-locator": {
"schema-name": "prodrep",
"table-name": "ACCT_%"
},
"rule-action": "include",
"filters": []
}
]
}
```
Output:
```
{
"ReplicationTask": {
"ReplicationTaskIdentifier": "moveit2",
"SourceEndpointArn": "arn:aws:dms:us-east-1:123456789012:endpoint:6GGI6YPWWGAYUVLKIB732KEVWA",
"TargetEndpointArn": "arn:aws:dms:us-east-1:123456789012:endpoint:EOM4SFKCZEYHZBFGAGZT3QEC5U",
"ReplicationInstanceArn": "arn:aws:dms:us-east-1:123456789012:rep:T3OM7OUB5NM2LCVZF7JPGJRNUE",
"MigrationType": "full-load",
"TableMappings": ...output omitted...,
"ReplicationTaskSettings": ...output omitted...,
"Status": "modifying",
"StopReason": "Stop Reason FULL_LOAD_ONLY_FINISHED",
"ReplicationTaskCreationDate": 1590524772.505,
"ReplicationTaskStartDate": 1590789424.653,
"ReplicationTaskArn": "arn:aws:dms:us-east-1:123456789012:task:K55IUCGBASJS5VHZJIINA45FII"
}
}
```
Per ulteriori informazioni, vedere [Working with AWS DMS Tasks](https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Tasks.html) nella *AWS Database Migration Service User Guide*.
+ Per i dettagli sull'API, consulta [ModifyReplicationTask AWS CLI](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/dms/modify-replication-task.html)*Command Reference.*
### `reboot-replication-instance`
Il seguente esempio di codice mostra come utilizzare`reboot-replication-instance`.
**AWS CLI**
**Come riavviare un’istanza di replica**
L’esempio `reboot-replication-instance` seguente riavvia un’istanza di replica.
```
aws dms reboot-replication-instance \
--replication-instance-arn arn:aws:dms:us-east-1:123456789012:rep:T3OM7OUB5NM2LCVZF7JPGJRNUE
```
Output:
```
{
"ReplicationInstance": {
"ReplicationInstanceIdentifier": "my-repl-instance",
"ReplicationInstanceClass": "dms.t2.micro",
"ReplicationInstanceStatus": "rebooting",
"AllocatedStorage": 5,
"InstanceCreateTime": 1590011235.952,
... output omitted ...
}
}
```
Per ulteriori informazioni, vedere [Working with an AWS DMS Replication Instance](https://docs.aws.amazon.com/dms/latest/userguide/CHAP_ReplicationInstance.html) nella *AWS Database Migration Service User Guide*.
+ Per i dettagli sull'API, consulta *AWS CLI Command [RebootReplicationInstance](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/dms/reboot-replication-instance.html)Reference*.
### `refresh-schemas`
Il seguente esempio di codice mostra come utilizzare`refresh-schemas`.
**AWS CLI**
**Come aggiornare gli schemi di database**
L'`refresh-schemas`esempio seguente richiede che AWS DMS aggiorni l'elenco degli schemi su un endpoint.
```
aws dms refresh-schemas \
--replication-instance-arn arn:aws:dms:us-east-1:123456789012:rep:T3OM7OUB5NM2LCVZF7JPGJRNUE \
--endpoint-arn "arn:aws:dms:us-east-1:123456789012:endpoint:6GGI6YPWWGAYUVLKIB732KEVWA"
```
Output:
```
{
"RefreshSchemasStatus": {
"EndpointArn": "arn:aws:dms:us-east-1:123456789012:endpoint:6GGI6YPWWGAYUVLKIB732KEVWA",
"ReplicationInstanceArn": "arn:aws:dms:us-east-1:123456789012:rep:T3OM7OUB5NM2LCVZF7JPGJRNUE",
"Status": "refreshing",
"LastRefreshDate": 1590019949.103
}
}
```
+ *Per i dettagli sull'API, vedere [RefreshSchemas](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/dms/refresh-schemas.html)in Command Reference.AWS CLI *
### `reload-tables`
Il seguente esempio di codice mostra come utilizzare`reload-tables`.
**AWS CLI**
**Come aggiornare l’elenco delle tabelle disponibili in un endpoint**
L’esempio `reload-tables` seguente ricarica l’elenco delle tabelle disponibili in un endpoint.
```
aws dms reload-tables \
--replication-task-arn "arn:aws:dms:us-east-1:123456789012:task:K55IUCGBASJS5VHZJIINA45FII" \
--tables-to-reload "SchemaName=prodrep,TableName=ACCT_BAL"
```
Output:
```
{
"ReplicationTaskArn": "arn:aws:dms:us-east-1:123456789012:task:K55IUCGBASJS5VHZJIINA45FII"
}
```
+ Per i dettagli sull'API, consulta [ReloadTables AWS CLI](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/dms/reload-tables.html)*Command Reference*.
### `remove-tags-from-resource`
Il seguente esempio di codice mostra come utilizzare`remove-tags-from-resource`.
**AWS CLI**
**Come rimuovere i tag da un’istanza di replica**
L’esempio `remove-tags-from-resource` seguente elimina i tag da un’istanza di replica.
```
aws dms remove-tags-from-resource \
--resource-arn arn:aws:dms:us-east-1:123456789012:rep:T3OM7OUB5NM2LCVZF7JPGJRNUE \
--tag-keys Environment Project
```
Questo comando non produce alcun output.
Per ulteriori informazioni, consulta [Assegnazione di tag alle risorse](https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Tagging.html) nella *Guida per l’utente di AWS Database Migration Service*.
+ Per i dettagli sull'API, consulta [RemoveTagsFromResource AWS CLI](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/dms/remove-tags-from-resource.html)*Command Reference*.
### `start-replication-task-assessment`
Il seguente esempio di codice mostra come utilizzare`start-replication-task-assessment`.
**AWS CLI**
**Come avviare una valutazione delle attività**
L’esempio `start-replication-task-assessment` seguente avvia una valutazione dell’attività di replica.
```
aws dms start-replication-task-assessment \
--replication-task-arn arn:aws:dms:us-east-1:123456789012:task:K55IUCGBASJS5VHZJIINA45FII
```
Output:
```
{
"ReplicationTask": {
"ReplicationTaskIdentifier": "moveit2",
"SourceEndpointArn": "arn:aws:dms:us-east-1:123456789012:endpoint:6GGI6YPWWGAYUVLKIB732KEVWA",
"TargetEndpointArn": "arn:aws:dms:us-east-1:123456789012:endpoint:EOM4SFKCZEYHZBFGAGZT3QEC5U",
"ReplicationInstanceArn": "arn:aws:dms:us-east-1:123456789012:rep:T3OM7OUB5NM2LCVZF7JPGJRNUE",
"MigrationType": "full-load",
"TableMappings": ...output omitted...,
"ReplicationTaskSettings": ...output omitted...,
"Status": "testing",
"StopReason": "Stop Reason FULL_LOAD_ONLY_FINISHED",
"ReplicationTaskCreationDate": 1590524772.505,
"ReplicationTaskStartDate": 1590789988.677,
"ReplicationTaskArn": "arn:aws:dms:us-east-1:123456789012:task:K55IUCGBASJS5VHZJIINA45FII"
}
}
```
Per ulteriori informazioni, consulta [Creazione di un report di valutazione del task](https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Tasks.AssessmentReport.html) nella *Guida per l’utente di AWS Database Migration Service*.
+ Per i dettagli sull'API, consulta [StartReplicationTaskAssessment AWS CLI](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/dms/start-replication-task-assessment.html)*Command Reference*.
### `start-replication-task`
Il seguente esempio di codice mostra come utilizzare`start-replication-task`.
**AWS CLI**
**Come avviare un’attività di replica**
L'`command-name`esempio seguente elenca i widget disponibili nel tuo AWS account.
```
aws dms start-replication-task \
--replication-task-arn arn:aws:dms:us-east-1:123456789012:task:K55IUCGBASJS5VHZJIINA45FII \
--start-replication-task-type reload-target
```
Output:
```
{
"ReplicationTask": {
"ReplicationTaskIdentifier": "moveit2",
"SourceEndpointArn": "arn:aws:dms:us-east-1:123456789012:endpoint:6GGI6YPWWGAYUVLKIB732KEVWA",
"TargetEndpointArn": "arn:aws:dms:us-east-1:123456789012:endpoint:EOM4SFKCZEYHZBFGAGZT3QEC5U",
"ReplicationInstanceArn": "arn:aws:dms:us-east-1:123456789012:rep:T3OM7OUB5NM2LCVZF7JPGJRNUE",
"MigrationType": "full-load",
"TableMappings": ...output omitted... ,
"ReplicationTaskSettings": ...output omitted... ,
"Status": "starting",
"ReplicationTaskCreationDate": 1590524772.505,
"ReplicationTaskStartDate": 1590619805.212,
"ReplicationTaskArn": "arn:aws:dms:us-east-1:123456789012:task:K55IUCGBASJS5VHZJIINA45FII"
}
}
```
Per ulteriori informazioni, vedere [Working with AWS DMS Tasks](https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Tasks.html) nella *AWS Database Migration Service User Guide*.
+ Per i dettagli sull'API, consulta [StartReplicationTask AWS CLI](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/dms/start-replication-task.html)*Command Reference.*
### `stop-replication-task`
Il seguente esempio di codice mostra come utilizzare`stop-replication-task`.
**AWS CLI**
**Come arrestare un’attività**
L’esempio `stop-replication-task` seguente arresta un’attività.
```
aws dms stop-replication-task \
--replication-task-arn arn:aws:dms:us-east-1:123456789012:task:K55IUCGBASJS5VHZJIINA45FII
```
Output:
```
{
"ReplicationTask": {
"ReplicationTaskIdentifier": "moveit2",
"SourceEndpointArn": "arn:aws:dms:us-east-1:123456789012:endpoint:6GGI6YPWWGAYUVLKIB732KEVWA",
"TargetEndpointArn": "arn:aws:dms:us-east-1:123456789012:endpoint:EOM4SFKCZEYHZBFGAGZT3QEC5U",
"ReplicationInstanceArn": "arn:aws:dms:us-east-1:123456789012:rep:T3OM7OUB5NM2LCVZF7JPGJRNUE",
"MigrationType": "full-load",
"TableMappings": ...output omitted...,
"ReplicationTaskSettings": ...output omitted...,
"Status": "stopping",
"ReplicationTaskCreationDate": 1590524772.505,
"ReplicationTaskStartDate": 1590789424.653,
"ReplicationTaskArn": "arn:aws:dms:us-east-1:123456789012:task:K55IUCGBASJS5VHZJIINA45FII"
}
}
```
Per ulteriori informazioni, vedere [Working with AWS DMS Tasks](https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Tasks.html) nella *AWS Database Migration Service User Guide*.
+ Per i dettagli sull'API, consulta [StopReplicationTask AWS CLI](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/dms/stop-replication-task.html)*Command Reference.*
### `test-connection`
Il seguente esempio di codice mostra come utilizzare`test-connection`.
**AWS CLI**
**Come testare una connessione a un endpoint**
L’esempio `test-connection` seguente verifica se è possibile accedere a un endpoint da un’istanza di replica.
```
aws dms test-connection \
--replication-instance-arn arn:aws:dms:us-east-1:123456789012:rep:T3OM7OUB5NM2LCVZF7JPGJRNUE \
--endpoint-arn arn:aws:dms:us-east-1:123456789012:endpoint:6GGI6YPWWGAYUVLKIB732KEVWA
```
Output:
```
{
"Connection": {
"ReplicationInstanceArn": "arn:aws:dms:us-east-1:123456789012:rep:T3OM7OUB5NM2LCVZF7JPGJRNUE",
"EndpointArn": "arn:aws:dms:us-east-1:123456789012:endpoint:6GGI6YPWWGAYUVLKIB732KEVWA",
"Status": "testing",
"EndpointIdentifier": "src-database-1",
"ReplicationInstanceIdentifier": "my-repl-instance"
}
}
```
Per ulteriori informazioni, consulta [Creazione di endpoint sorgente e obiettivo](https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Endpoints.Creating.html) nella *Guida per l’utente di AWS Database Migration Service*.
+ Per i dettagli sull'API, consulta [TestConnection AWS CLI](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/dms/test-connection.html)*Command Reference*.