-
Notifications
You must be signed in to change notification settings - Fork 3
15._EBS
Ahmad Abdo edited this page Jun 26, 2017
·
1 revision
$ awsm listVolumes --help
NAME:
awsm listVolumes - List EBS Volumes
USAGE:
awsm listVolumes [arguments...]
ARGUMENTS:
[search] - The keyword to search for
awsm listVolumes dev1
This will list all Volumes matching the term dev1, the output should look similar to this:
$ awsm listVolumes dev1
+------------------+------------+-----------------------+--------+-----------+-----------+------+---------------------+------------+--------------+-------------+-----------------+-------------------+-----------+
| NAME | CLASS | VOLUME ID | SIZE | STATE | ENCRYPTED | IOPS | INSTANCE ID | ATTACHMENT | CREATED | VOLUME TYPE | DELETE ON TERM | AVAILABILITY ZONE | REGION |
+------------------+------------+-----------------------+--------+-----------+-----------+------+---------------------+------------+--------------+-------------+-----------------+-------------------+-----------+
| mysql-data-getDB | | vol-0191071ef32a5dd94 | 100 GB | in-use | false | 0 | i-04643fa708a34815d | dev1 | 3 months ago | standard | false | us-west-2a | us-west-2 |
| dev11-mysql-data | mysql-data | vol-05372f104e102c413 | 100 GB | available | false | 100 | | | 3 weeks ago | io1 | false | us-west-2a | us-west-2 |
| dev11-code | code | vol-0d54d8c0276cb20f4 | 30 GB | in-use | true | 0 | i-012d2d038090eef0d | dev11 | 3 days ago | standard | true | us-west-2a | us-west-2 |
| dev11-mysql-data | mysql-data | vol-02cfd84f1c09f2ddc | 100 GB | in-use | false | 100 | i-012d2d038090eef0d | dev11 | 3 days ago | io1 | true | us-west-2a | us-west-2 |
+------------------+------------+-----------------------+--------+-----------+-----------+------+---------------------+------------+--------------+-------------+-----------------+-------------------+-----------+
$ awsm listSnapshots --help
NAME:
awsm listSnapshots - List EBS Snapshots
USAGE:
awsm listSnapshots [arguments...]
ARGUMENTS:
[search] - The keyword to search for
awsm listSnapshots code
This will list all Snapshots matching the name code, the output should look similar to this:
$ awsm listSnapshots code
+---------+-------+------------------------+-----------------------+-----------+--------------+----------+-------------+-----------+
| NAME | CLASS | SNAPSHOT ID | VOLUME ID | STATE | CREATED | PROGRESS | VOLUME SIZE | REGION |
+---------+-------+------------------------+-----------------------+-----------+--------------+----------+-------------+-----------+
| code-v1 | code | snap-0ba8561be24ffbc98 | vol-ffffffff | completed | 4 months ago | ready | 30 | us-east-1 |
| code-v2 | code | snap-0ca08aa29a6688b7b | vol-ffffffff | completed | 2 months ago | ready | 30 | us-east-1 |
| code-v1 | code | snap-08a11f68c2e9df04c | vol-0de5a1bdba76cb6a0 | completed | 4 months ago | ready | 30 | us-west-2 |
| code-v2 | code | snap-0fb65c42b976bc66d | vol-08597963b47c68255 | completed | 2 months ago | ready | 30 | us-west-2 |
| code-v1 | code | snap-025ff6a3ecca6e12b | vol-ffffffff | completed | 4 months ago | ready | 30 | eu-west-1 |
| code-v2 | code | snap-008148f28a863b386 | vol-ffffffff | completed | 2 months ago | ready | 30 | eu-west-1 |
+---------+-------+------------------------+-----------------------+-----------+--------------+----------+-------------+-----------+
$ awsm createSnapshot --help
NAME:
awsm createSnapshot - Create an EBS snapshot of a volume
USAGE:
awsm createSnapshot [arguments...]
ARGUMENTS:
class - The class of the new snapshot
[search] - The volume to create the snapshot from (optional, defaults setting in class configuration)
awsm createSnapshot example-snapshot
This will create a Snapshot using the example-snapshot class configuration, the output should look similar to this:
$ awsm createSnapshot example-snapshot
✓ Found Snapshot Class Configuration for [example-snapshot]!
✓ Found Volume [vol-08cd195606f4de0fb] named [mysql-data] in region [us-west-2]!
▶ Are you sure you want to create this Snapshot?
◀ y
✓ Snapshot Class [example-snapshot] has SSM Commands configured, checking if we are able to send them...
✓ Found SSM Instance [i-0fc6a657c8f693220] named [dev11] and a ping time of [4 minutes ago]!
✓ Previous version of snapshot is [0]
△ New version of snapshot is [1]
△ Running Pre-Snapshot Command...
△ Sending Command [su - ubuntu -c "cd crusher-salon/ && crusher lc pre-snapshot-salon-mysql"] to instances [dev11] in [us-west-2]!
✓ Sent Command [su - ubuntu -c "cd crusher-salon/ && crusher lc pre-snapshot-salon-mysql"] [6ca20857-6413-492d-961a-3eaa96d7d73a] to instances [dev11] in [us-west-2]!
▶ Waiting for response from [us-west-2]..
✓ Recieved a response from [us-west-2]!
✓ Found [1] SSM Command Invocations!
===========================================================================
Instance: dev11, i-0fc6a657c8f693220
Region: us-west-2
Status: Success
Requested: 11 seconds ago
Command ID: 6ca20857-6413-492d-961a-3eaa96d7d73a
Comment: awsm sendCommand: su - ubuntu -c "cd crusher-salon/ && crusher lc pre-snapshot-salon-mysql"
Command #1 [aws:runShellScript] Output:
△ Running pre-configuration command: [sudo chmod -R 775 ./specs/disks/scripts/]
✓ pre-configuration command: [sudo chmod -R 775 ./specs/disks/scripts/] Succeeded!
△ Running pre-configuration command: [./specs/disks/scripts/remove-sdb.sh]
✓ pre-configuration command: [./specs/disks/scripts/remove-sdb.sh] Succeeded!
△ Running pre-configuration command: [sudo chmod -R 775 ./specs/salon-mysql-data/scripts/]
✓ pre-configuration command: [sudo chmod -R 775 ./specs/salon-mysql-data/scripts/] Succeeded!
△ Running post-configuration command: [./specs/salon-mysql-data/scripts/salon-mysql-data-volume-pre-snapshot.sh]
✓ post-configuration command: [./specs/salon-mysql-data/scripts/salon-mysql-data-volume-pre-snapshot.sh] Succeeded!
===========================================================================
△ Running Post-Snapshot Command...
△ Sending Command [su - ubuntu -c "cd crusher-salon/ && crusher lc post-snapshot-salon-mysql"] to instances [dev11] in [us-west-2]!
✓ Sent Command [su - ubuntu -c "cd crusher-salon/ && crusher lc post-snapshot-salon-mysql"] [2b8b6124-0620-4b15-8162-3029d50f6ccb] to instances [dev11] in [us-west-2]!
▶ Waiting for response from [us-west-2]..
✓ Recieved a response from [us-west-2]!
✓ Found [1] SSM Command Invocations!
===========================================================================
Instance: dev11, i-0fc6a657c8f693220
Region: us-west-2
Status: Success
Requested: 11 seconds ago
Command ID: 2b8b6124-0620-4b15-8162-3029d50f6ccb
Comment: awsm sendCommand: su - ubuntu -c "cd crusher-salon/ && crusher lc post-snapshot-salon-mysql"
Command #1 [aws:runShellScript] Output:
△ Running pre-configuration command: [sudo chmod -R 775 ./specs/disks/scripts/]
✓ pre-configuration command: [sudo chmod -R 775 ./specs/disks/scripts/] Succeeded!
△ Running pre-configuration command: [./specs/disks/scripts/remove-sdb.sh]
✓ pre-configuration command: [./specs/disks/scripts/remove-sdb.sh] Succeeded!
△ Running pre-configuration command: [sudo chmod -R 775 ./specs/salon-mysql-data/scripts/]
✓ pre-configuration command: [sudo chmod -R 775 ./specs/salon-mysql-data/scripts/] Succeeded!
△ Running post-configuration command: [./specs/salon-mysql-data/scripts/salon-mysql-data-volume-post-snapshot.sh]
▶ starting replication... unlocking tables...
✓ post-configuration command: [./specs/salon-mysql-data/scripts/salon-mysql-data-volume-post-snapshot.sh] Succeeded!
===========================================================================
△ Created Snapshot [snap-0b857ec4ce261394d] named [example-snapshot-v1] in [us-west-2]!
▶ Propagate flag is set, waiting for initial snapshot to complete...
△ Created [snap-0fef725ed0b4ef972] from [snap-0b857ec4ce261394d] named [example-snapshot-v1] copied from region [us-west-2] to region [us-east-1]!
✓ Copied snapshot [snap-0b857ec4ce261394d] to region [us-east-1].
△ Created [snap-09e06798435ff24b8] from [snap-0b857ec4ce261394d] named [example-snapshot-v1] copied from region [us-west-2] to region [eu-west-1]!
✓ Copied snapshot [snap-0b857ec4ce261394d] to region [eu-west-1].
✓ Done!
$ awsm createVolume --help
NAME:
awsm createVolume - Create an EBS volume
USAGE:
awsm createVolume [arguments...]
ARGUMENTS:
class - The class of the new volume
name - The name of the new volume
az - The Availability Zone to create the volume in
awsm createVolume example-volume example-volume1 us-west-2a
This will create a Volume named example-volume1 using the example-volume class configuration, the output should look similar to this:
$ awsm createVolume example-volume example-volume1 us-west-2a
✓ Found Volume Class Configuration for [example-volume]!
✓ Found Availability Zone [us-west-2a]!
✓ Found Snapshot [snap-0b857ec4ce261394d] named [example-snapshot-v1] with a class of [example-snapshot] created [23 minutes ago]!
▶ Are you sure you want to create this Volume?
◀ y
△ Created Volume [vol-0bcb71bdba7b46422] named [example-volume1] in [us-west-2]!
▶ Waiting to tag EBS Volume...
△ Adding EBS Tags...
$ awsm refreshVolume --help
NAME:
awsm refreshVolume - Refreshe an EBS Volume on an EC2 Instance
USAGE:
awsm refreshVolume [command options] [arguments...]
ARGUMENTS:
volume - The volume to refresh
instance - The instance to refresh the volume on
OPTIONS:
--force force refresh
awsm refreshVolume mysql dev2
This will refresh (detach, create new, attach, destroy) the volume matching the term mysql attached to the instance matching the term dev2, the output should look similar to this:
$ awsm refreshVolume mysql dev2
✓ Found Instance [i-0dd843fbadcf7fd63] named [dev2] in [us-east-1]!
✓ Found Volume [vol-077b8b7cb43ccbe64] named [dev2-mysql-data] in [us-east-1]!
+-----------------+------------+-----------------------+--------+--------+-----------+------+---------------------+------------+-------------+-------------+-----------------+-------------------+-----------+
| NAME | CLASS | VOLUME ID | SIZE | STATE | ENCRYPTED | IOPS | INSTANCE ID | ATTACHMENT | CREATED | VOLUME TYPE | DELETE ON TERM | AVAILABILITY ZONE | REGION |
+-----------------+------------+-----------------------+--------+--------+-----------+------+---------------------+------------+-------------+-------------+-----------------+-------------------+-----------+
| dev2-mysql-data | mysql-data | vol-077b8b7cb43ccbe64 | 100 GB | in-use | false | 100 | i-0dd843fbadcf7fd63 | dev2 | 3 hours ago | io1 | false | us-east-1a | us-east-1 |
+-----------------+------------+-----------------------+--------+--------+-----------+------+---------------------+------------+-------------+-------------+-----------------+-------------------+-----------+
▶ Are you sure you want to refresh this Volume?
◀ y
✓ Volume Class [mysql-data] has SSM Commands configured, checking if we are able to send them...
✓ Found SSM Instance [i-0dd843fbadcf7fd63] named [dev2] and a ping time of [1 minute ago]!
▶ Found newer snapshot [snap-081e7b89854548739] with class of [mysql-data] named [mysql] created [2 hours ago]
△ Created Volume [vol-0f02cb7e01c18f651] named [dev2-mysql-data] in [us-east-1]!
▶ Waiting to tag EBS Volume...
△ Adding EBS Tags...
△ Running Detach Command...
△ Sending Command [su - ubuntu -c "cd crusher-salon/ && crusher lc detach-salon-mysql"] to instances [dev2-new] in [us-east-1]!
✓ Sent Command [su - ubuntu -c "cd crusher-salon/ && crusher lc detach-salon-mysql"] [1b38a3a7-03dd-461f-b4a9-9ee605f215eb] to instances [dev2-new] in [us-east-1]!
▶ Waiting for response from [us-east-1]..
▶ Waiting for response from [us-east-1]..
✓ Recieved a response from [us-east-1]!
✓ Found [1] SSM Command Invocations!
===========================================================================
Instance: dev2, i-0dd843fbadcf7fd63
Region: us-east-1
Status: Success
Requested: 22 seconds ago
Command ID: 1b38a3a7-03dd-461f-b4a9-9ee605f215eb
Comment: awsm sendCommand: su - ubuntu -c "cd crusher-salon/ && crusher lc detach-salon-mysql"
Command #1 [aws:runShellScript] Output:
△ Running pre-configuration command: [sudo chmod -R 775 ./specs/salon-mysql-data/scripts/]
✓ pre-configuration command: [sudo chmod -R 775 ./specs/salon-mysql-data/scripts/] Succeeded!
△ Running post-configuration command: [./specs/salon-mysql-data/scripts/salon-mysql-data-volume-detach.sh]
✓ post-configuration command: [./specs/salon-mysql-data/scripts/salon-mysql-data-volume-detach.sh] Succeeded!
===========================================================================
△ Detaching Volume [vol-077b8b7cb43ccbe64] named [dev2-mysql-data] from instance [i-0dd843fbadcf7fd63] in [us-east-1]...
▶ Waiting for EBS Volume to detach...
✓ Detached Volume [vol-077b8b7cb43ccbe64] named [dev2-mysql-data] in [us-east-1]!
△ Attaching Volume [vol-0f02cb7e01c18f651] named [dev2-mysql-data] to [i-0dd843fbadcf7fd63] in [us-east-1]...
✓ Attached Volume [vol-0f02cb7e01c18f651] named [dev2-mysql-data] to instance [i-0dd843fbadcf7fd63] named [dev2-new] in [us-east-1]!
△ Running Attach Command...
△ Sending Command [su - ubuntu -c "cd crusher-salon/ && crusher lc attach-salon-mysql"] to instances [dev2-new] in [us-east-1]!
✓ Sent Command [su - ubuntu -c "cd crusher-salon/ && crusher lc attach-salon-mysql"] [bc2fbbca-21e7-4ec4-86cb-2af5984d19cf] to instances [dev2-new] in [us-east-1]!
▶ Waiting for response from [us-east-1]..
▶ Waiting for response from [us-east-1]..
▶ Waiting for response from [us-east-1]..
▶ Waiting for response from [us-east-1]..
▶ Waiting for response from [us-east-1]..
▶ Waiting for response from [us-east-1]..
▶ Waiting for response from [us-east-1]..
▶ Waiting for response from [us-east-1]..
▶ Waiting for response from [us-east-1]..
▶ Waiting for response from [us-east-1]..
▶ Waiting for response from [us-east-1]..
▶ Waiting for response from [us-east-1]..
▶ Waiting for response from [us-east-1]..
▶ Waiting for response from [us-east-1]..
▶ Waiting for response from [us-east-1]..
✓ Recieved a response from [us-east-1]!
✓ Found [1] SSM Command Invocations!
===========================================================================
Instance: dev2, i-0dd843fbadcf7fd63
Region: us-east-1
Status: Success
Requested: 2 minutes ago
Command ID: bc2fbbca-21e7-4ec4-86cb-2af5984d19cf
Comment: awsm sendCommand: su - ubuntu -c "cd crusher-salon/ && crusher lc attach-salon-mysql"
Command #1 [aws:runShellScript] Output:
△ Running pre-configuration command: [sudo chmod -R 775 ./specs/disks/scripts/]
✓ pre-configuration command: [sudo chmod -R 775 ./specs/disks/scripts/] Succeeded!
△ Running pre-configuration command: [./specs/disks/scripts/remove-sdb.sh]
✓ pre-configuration command: [./specs/disks/scripts/remove-sdb.sh] Succeeded!
△ Running pre-configuration command: [sudo chmod -R 775 ./specs/salon-mysql-data/scripts/]
✓ pre-configuration command: [sudo chmod -R 775 ./specs/salon-mysql-data/scripts/] Succeeded!
△ Running post-configuration command: [./specs/salon-mysql-data/scripts/salon-mysql-data-volume-attach.sh]
✓ post-configuration command: [./specs/salon-mysql-data/scripts/salon-mysql-data-volume-attach.sh] Succeeded!
===========================================================================
△ Deleted Volume [dev2-mysql-data] in [us-east-1]!
△ Refreshed Volume [vol-077b8b7cb43ccbe64] named [dev2-mysql-data] in [us-east-1]!
✓ Done!
$ awsm attachVolume --help
NAME:
awsm attachVolume - Attach an EBS Volume to an EC2 Instance
USAGE:
awsm attachVolume [arguments...]
ARGUMENTS:
volume - The volume to attach
instance - The instance to attach the volume to
awsm attachVolume example-volume dev11
This will attach the Volume matching the term example-volume to the Instance matching the term dev (in the same AZ as the Volume), the output should look similar to this:
$ awsm attachVolume example-volume dev11
✓ Found Instance [i-0fc6a657c8f693220] named [dev11] in [us-west-2]!
+-----------------+----------------+-----------------------+--------+-----------+-----------+------+-------------+------------+----------------+-------------+-----------------+-------------------+-----------+
| NAME | CLASS | VOLUME ID | SIZE | STATE | ENCRYPTED | IOPS | INSTANCE ID | ATTACHMENT | CREATED | VOLUME TYPE | DELETE ON TERM | AVAILABILITY ZONE | REGION |
+-----------------+----------------+-----------------------+--------+-----------+-----------+------+-------------+------------+----------------+-------------+-----------------+-------------------+-----------+
| example-volume1 | example-volume | vol-0bcb71bdba7b46422 | 100 GB | available | false | 0 | | | 15 minutes ago | standard | false | us-west-2a | us-west-2 |
+-----------------+----------------+-----------------------+--------+-----------+-----------+------+-------------+------------+----------------+-------------+-----------------+-------------------+-----------+
▶ Are you sure you want to attach this Volume?
◀ y
✓ Volume Class [example-volume] has an SSM Attach Command configured, checking if we are able to send it...
✓ Found SSM Instance [i-0fc6a657c8f693220] named [dev11] and a ping time of [2 minutes ago]!
△ Attaching Volume [vol-0bcb71bdba7b46422] named [example-volume1] to [i-0fc6a657c8f693220] in [us-west-2]...
✓ Attached Volume [vol-0bcb71bdba7b46422] named [example-volume1] to instance [i-0fc6a657c8f693220] named [dev11] in [us-west-2]!
△ Running Attach Command...
△ Sending Command [uptime] to instances [dev11] in [us-west-2]!
✓ Sent Command [uptime] [9515cb1f-f12a-454a-8eef-201d90ab7839] to instances [dev11] in [us-west-2]!
▶ Waiting for response from [us-west-2]..
✓ Recieved a response from [us-west-2]!
✓ Found [1] SSM Command Invocations!
===========================================================================
Instance: dev11, i-0fc6a657c8f693220
Region: us-west-2
Status: Success
Requested: 10 seconds ago
Command ID: 9515cb1f-f12a-454a-8eef-201d90ab7839
Comment: awsm sendCommand: uptime
Command #1 [aws:runShellScript] Output:
22:49:15 up 9 days, 17:56, 1 user, load average: 3.97, 11.42, 10.23
===========================================================================
✓ Done!
$ awsm copySnapshot --help
NAME:
awsm copySnapshot - Copy an EBS Snapshot to another region
USAGE:
awsm copySnapshot [arguments...]
ARGUMENTS:
search - The snapshot to copy
region - The region to copy the snapshot to
awsm copySnapshot snap-0b857ec4ce261394d us-east-1
This will copy the Snapshot matching the term snap-0b857ec4ce261394d to the us-east-1 AWS Region, the output should look similar to this:
$ awsm copySnapshot snap-0b857ec4ce261394d us-east-1
△ Created [snap-089c2846287748574] from [snap-0b857ec4ce261394d] named [example-snapshot-v1] copied from region [us-west-2] to region [us-east-1]!
✓ Copied Snapshot [snap-0b857ec4ce261394d] named [example-snapshot-v1] to [us-east-1]!
$ awsm deleteSnapshots --help
NAME:
awsm deleteSnapshots - Delete EBS Snapshots
USAGE:
awsm deleteSnapshots [arguments...]
ARGUMENTS:
search - The search term for snapshots to delete
[region] - The region of the snapshots (optional)
awsm deleteSnapshots example-snapshot
This will delete all Snapshots matching the name example-snapshot, the output should look similar to this:
$ awsm deleteSnapshots example-snapshot
+---------------------+------------------+------------------------+-----------------------+-----------+----------------+----------+-------------+-----------+
| NAME | CLASS | SNAPSHOT ID | VOLUME ID | STATE | CREATED | PROGRESS | VOLUME SIZE | REGION |
+---------------------+------------------+------------------------+-----------------------+-----------+----------------+----------+-------------+-----------+
| example-snapshot-v1 | example-snapshot | snap-0fef725ed0b4ef972 | vol-ffffffff | completed | 36 minutes ago | ready | 100 | us-east-1 |
| example-snapshot-v1 | example-snapshot | snap-089c2846287748574 | vol-ffffffff | pending | 1 minute ago | 0% | 100 | us-east-1 |
| example-snapshot-v1 | example-snapshot | snap-0b857ec4ce261394d | vol-08cd195606f4de0fb | completed | 41 minutes ago | ready | 100 | us-west-2 |
| example-snapshot-v1 | example-snapshot | snap-09e06798435ff24b8 | vol-ffffffff | completed | 36 minutes ago | ready | 100 | eu-west-1 |
+---------------------+------------------+------------------------+-----------------------+-----------+----------------+----------+-------------+-----------+
▶ Are you sure you want to delete these Snapshots?
◀ y
△ Deleted Snapshot [snap-0fef725ed0b4ef972] named [example-snapshot-v1] in [us-east-1]!
△ Deleted Snapshot [snap-089c2846287748574] named [example-snapshot-v1] in [us-east-1]!
△ Deleted Snapshot [snap-0b857ec4ce261394d] named [example-snapshot-v1] in [us-west-2]!
△ Deleted Snapshot [snap-09e06798435ff24b8] named [example-snapshot-v1] in [eu-west-1]!
✓ Done!
$ awsm deleteVolumes --help
NAME:
awsm deleteVolumes - Delete EBS Volumes
USAGE:
awsm deleteVolumes [arguments...]
ARGUMENTS:
volume - The volume to delete
[region] - The region of the volumes (optional)
awsm deleteVolumes example-volume
This will delete all Volumes matching the term example-volume, the output should look similar to this:
$ awsm deleteVolumes example-volume
+-----------------+----------------+-----------------------+--------+-----------+-----------+------+-------------+------------+----------------+-------------+-----------------+-------------------+-----------+
| NAME | CLASS | VOLUME ID | SIZE | STATE | ENCRYPTED | IOPS | INSTANCE ID | ATTACHMENT | CREATED | VOLUME TYPE | DELETE ON TERM | AVAILABILITY ZONE | REGION |
+-----------------+----------------+-----------------------+--------+-----------+-----------+------+-------------+------------+----------------+-------------+-----------------+-------------------+-----------+
| example-volume1 | example-volume | vol-0bcb71bdba7b46422 | 100 GB | available | false | 0 | | | 19 minutes ago | standard | false | us-west-2a | us-west-2 |
+-----------------+----------------+-----------------------+--------+-----------+-----------+------+-------------+------------+----------------+-------------+-----------------+-------------------+-----------+
▶ Are you sure you want to delete these Volumes?
◀ y
△ Deleted Volume [example-volume1] in [us-west-2]!
✓ Done!
$ awsm detachVolume --help
NAME:
awsm detachVolume - Detach an EBS Volume
USAGE:
awsm detachVolume [command options] [arguments...]
ARGUMENTS:
volume - The volume to detach
instance - The instance to detach the volume from
OPTIONS:
--force force detach
awsm detachVolume example-volume dev11
This will detach the Volume matching the term example-volume from the instance matching the term dev11, the output should look similar to this:
$ awsm detachVolume example-volume dev11
✓ Found Instance [i-0fc6a657c8f693220] named [dev11] in [us-west-2]!
+-----------------+----------------+-----------------------+--------+--------+-----------+------+---------------------+------------+----------------+-------------+-----------------+-------------------+-----------+
| NAME | CLASS | VOLUME ID | SIZE | STATE | ENCRYPTED | IOPS | INSTANCE ID | ATTACHMENT | CREATED | VOLUME TYPE | DELETE ON TERM | AVAILABILITY ZONE | REGION |
+-----------------+----------------+-----------------------+--------+--------+-----------+------+---------------------+------------+----------------+-------------+-----------------+-------------------+-----------+
| example-volume1 | example-volume | vol-0bcb71bdba7b46422 | 100 GB | in-use | false | 0 | i-0fc6a657c8f693220 | dev11 | 13 minutes ago | standard | false | us-west-2a | us-west-2 |
+-----------------+----------------+-----------------------+--------+--------+-----------+------+---------------------+------------+----------------+-------------+-----------------+-------------------+-----------+
▶ Are you sure you want to detatch this Volume?
◀ y
✓ Volume Class [example-volume] has SSM Commands configured, checking if we are able to send them...
✓ Found SSM Instance [i-0fc6a657c8f693220] named [dev11] and a ping time of [9 seconds ago]!
△ Running Detach Command...
△ Sending Command [uptime] to instances [dev11] in [us-west-2]!
✓ Sent Command [uptime] [a2de836a-3f26-4a5e-93af-7e64ddda714d] to instances [dev11] in [us-west-2]!
▶ Waiting for response from [us-west-2]..
✓ Recieved a response from [us-west-2]!
✓ Found [1] SSM Command Invocations!
===========================================================================
Instance: dev11, i-0fc6a657c8f693220
Region: us-west-2
Status: Success
Requested: 11 seconds ago
Command ID: a2de836a-3f26-4a5e-93af-7e64ddda714d
Comment: awsm sendCommand: uptime
Command #1 [aws:runShellScript] Output:
22:47:21 up 9 days, 17:54, 1 user, load average: 19.62, 16.02, 11.38
===========================================================================
△ Detaching Volume [vol-0bcb71bdba7b46422] named [example-volume1] from instance [i-0fc6a657c8f693220] in [us-west-2]...
▶ Waiting for EBS Volume to detach...
✓ Detached Volume [vol-0bcb71bdba7b46422] named [example-volume1] in [us-west-2]!
✓ Done!