aws dms wait
Wait until a particular condition is satisfied. Each subcommand polls an API until the listed requirement is met
Subcommands
| Name | Description |
|---|---|
endpoint-deleted | Wait until testing endpoint is deleted. It will poll every 5 seconds until a successful state has been reached. This will exit with a return code of 255 after 60 failed checks |
replication-instance-available | Wait until DMS replication instance is available. It will poll every 60 seconds until a successful state has been reached. This will exit with a return code of 255 after 60 failed checks |
replication-instance-deleted | Wait until DMS replication instance is deleted. It will poll every 15 seconds until a successful state has been reached. This will exit with a return code of 255 after 60 failed checks |
replication-task-deleted | Wait until DMS replication task is deleted. It will poll every 15 seconds until a successful state has been reached. This will exit with a return code of 255 after 60 failed checks |
replication-task-ready | Wait until DMS replication task is ready. It will poll every 15 seconds until a successful state has been reached. This will exit with a return code of 255 after 60 failed checks |
replication-task-running | Wait until DMS replication task is running. It will poll every 15 seconds until a successful state has been reached. This will exit with a return code of 255 after 60 failed checks |
replication-task-stopped | Wait until DMS replication task is stopped. It will poll every 15 seconds until a successful state has been reached. This will exit with a return code of 255 after 60 failed checks |
test-connection-succeeds | Wait until testing connection succeeds. It will poll every 5 seconds until a successful state has been reached. This will exit with a return code of 255 after 60 failed checks |