|
219 | 219 | {"shape":"AccountSetupInProgressException"},
|
220 | 220 | {"shape":"UnauthenticatedException"}
|
221 | 221 | ],
|
222 |
| - "documentation":"<p>Creates a snapshot of a block storage disk. You can use snapshots for backups, to make copies of disks, and to save data before shutting down a Lightsail instance.</p> <p>You can take a snapshot of an attached disk that is in use; however, snapshots only capture data that has been written to your disk at the time the snapshot command is issued. This may exclude any data that has been cached by any applications or the operating system. If you can pause any file systems on the disk long enough to take a snapshot, your snapshot should be complete. Nevertheless, if you cannot pause all file writes to the disk, you should unmount the disk from within the Lightsail instance, issue the create disk snapshot command, and then remount the disk to ensure a consistent and complete snapshot. You may remount and use your disk while the snapshot status is pending.</p> <p>The <code>create disk snapshot</code> operation supports tag-based access control via request tags. For more information, see the <a href=\"https://lightsail.aws.amazon.com/ls/docs/en/articles/amazon-lightsail-controlling-access-using-tags\">Lightsail Dev Guide</a>.</p>" |
| 222 | + "documentation":"<p>Creates a snapshot of a block storage disk. You can use snapshots for backups, to make copies of disks, and to save data before shutting down a Lightsail instance.</p> <p>You can take a snapshot of an attached disk that is in use; however, snapshots only capture data that has been written to your disk at the time the snapshot command is issued. This may exclude any data that has been cached by any applications or the operating system. If you can pause any file systems on the disk long enough to take a snapshot, your snapshot should be complete. Nevertheless, if you cannot pause all file writes to the disk, you should unmount the disk from within the Lightsail instance, issue the create disk snapshot command, and then remount the disk to ensure a consistent and complete snapshot. You may remount and use your disk while the snapshot status is pending.</p> <p>You can also use this operation to create a snapshot of an instance's system volume. You might want to do this, for example, to recover data from the system volume of a botched instance or to create a backup of the system volume like you would for a block storage disk. To create a snapshot of a system volume, just define the <code>instance name</code> parameter when issuing the snapshot command, and a snapshot of the defined instance's system volume will be created. After the snapshot is available, you can create a block storage disk from the snapshot and attach it to a running instance to access the data on the disk.</p> <p>The <code>create disk snapshot</code> operation supports tag-based access control via request tags. For more information, see the <a href=\"https://lightsail.aws.amazon.com/ls/docs/en/articles/amazon-lightsail-controlling-access-using-tags\">Lightsail Dev Guide</a>.</p>" |
223 | 223 | },
|
224 | 224 | "CreateDomain":{
|
225 | 225 | "name":"CreateDomain",
|
|
732 | 732 | {"shape":"AccountSetupInProgressException"},
|
733 | 733 | {"shape":"UnauthenticatedException"}
|
734 | 734 | ],
|
735 |
| - "documentation":"<p>Exports a Amazon Lightsail instance or block storage disk snapshot to Amazon Elastic Compute Cloud (Amazon EC2). This operation results in an export snapshot record that can be used with the <code>create cloud formation stack</code> operation to create new Amazon EC2 instances.</p> <p>Exported instance snapshots appear in Amazon EC2 as Amazon Machine Images (AMIs), and the instance system disk appears as an Amazon Elastic Block Store (Amazon EBS) volume. Exported disk snapshots appear in Amazon EC2 as Amazon EBS volumes. Snapshots are exported to the same Amazon Web Services Region in Amazon EC2 as the source Lightsail snapshot.</p> <p/> <p>The <code>export snapshot</code> operation supports tag-based access control via resource tags applied to the resource identified by sourceSnapshotName. For more information, see the <a href=\"https://lightsail.aws.amazon.com/ls/docs/en/articles/amazon-lightsail-controlling-access-using-tags\">Lightsail Dev Guide</a>.</p> <note> <p>Use the <code>get instance snapshots</code> or <code>get disk snapshots</code> operations to get a list of snapshots that you can export to Amazon EC2.</p> </note>" |
| 735 | + "documentation":"<p>Exports an Amazon Lightsail instance or block storage disk snapshot to Amazon Elastic Compute Cloud (Amazon EC2). This operation results in an export snapshot record that can be used with the <code>create cloud formation stack</code> operation to create new Amazon EC2 instances.</p> <p>Exported instance snapshots appear in Amazon EC2 as Amazon Machine Images (AMIs), and the instance system disk appears as an Amazon Elastic Block Store (Amazon EBS) volume. Exported disk snapshots appear in Amazon EC2 as Amazon EBS volumes. Snapshots are exported to the same Amazon Web Services Region in Amazon EC2 as the source Lightsail snapshot.</p> <p/> <p>The <code>export snapshot</code> operation supports tag-based access control via resource tags applied to the resource identified by sourceSnapshotName. For more information, see the <a href=\"https://lightsail.aws.amazon.com/ls/docs/en/articles/amazon-lightsail-controlling-access-using-tags\">Lightsail Dev Guide</a>.</p> <note> <p>Use the <code>get instance snapshots</code> or <code>get disk snapshots</code> operations to get a list of snapshots that you can export to Amazon EC2.</p> </note>" |
736 | 736 | },
|
737 | 737 | "GetActiveNames":{
|
738 | 738 | "name":"GetActiveNames",
|
|
1663 | 1663 | {"shape":"AccountSetupInProgressException"},
|
1664 | 1664 | {"shape":"UnauthenticatedException"}
|
1665 | 1665 | ],
|
1666 |
| - "documentation":"<p>Restarts a specific instance. When your Amazon Lightsail instance is finished rebooting, Lightsail assigns a new public IP address. To use the same IP address after restarting, create a static IP address and attach it to the instance.</p> <p>The <code>reboot instance</code> operation supports tag-based access control via resource tags applied to the resource identified by instanceName. For more information, see the <a href=\"https://lightsail.aws.amazon.com/ls/docs/en/articles/amazon-lightsail-controlling-access-using-tags\">Lightsail Dev Guide</a>.</p>" |
| 1666 | + "documentation":"<p>Restarts a specific instance.</p> <p>The <code>reboot instance</code> operation supports tag-based access control via resource tags applied to the resource identified by instanceName. For more information, see the <a href=\"https://lightsail.aws.amazon.com/ls/docs/en/articles/amazon-lightsail-controlling-access-using-tags\">Lightsail Dev Guide</a>.</p>" |
1667 | 1667 | },
|
1668 | 1668 | "RebootRelationalDatabase":{
|
1669 | 1669 | "name":"RebootRelationalDatabase",
|
|
1720 | 1720 | {"shape":"AccountSetupInProgressException"},
|
1721 | 1721 | {"shape":"UnauthenticatedException"}
|
1722 | 1722 | ],
|
1723 |
| - "documentation":"<p>Starts a specific Amazon Lightsail instance from a stopped state. To restart an instance, use the reboot instance operation.</p> <p>The <code>start instance</code> operation supports tag-based access control via resource tags applied to the resource identified by instanceName. For more information, see the <a href=\"https://lightsail.aws.amazon.com/ls/docs/en/articles/amazon-lightsail-controlling-access-using-tags\">Lightsail Dev Guide</a>.</p>" |
| 1723 | + "documentation":"<p>Starts a specific Amazon Lightsail instance from a stopped state. To restart an instance, use the <code>reboot instance</code> operation.</p> <note> <p>When you start a stopped instance, Lightsail assigns a new public IP address to the instance. To use the same IP address after stopping and starting an instance, create a static IP address and attach it to the instance. For more information, see the <a href=\"https://lightsail.aws.amazon.com/ls/docs/en/articles/lightsail-create-static-ip\">Lightsail Dev Guide</a>.</p> </note> <p>The <code>start instance</code> operation supports tag-based access control via resource tags applied to the resource identified by instanceName. For more information, see the <a href=\"https://lightsail.aws.amazon.com/ls/docs/en/articles/amazon-lightsail-controlling-access-using-tags\">Lightsail Dev Guide</a>.</p>" |
1724 | 1724 | },
|
1725 | 1725 | "StartRelationalDatabase":{
|
1726 | 1726 | "name":"StartRelationalDatabase",
|
|
1758 | 1758 | {"shape":"AccountSetupInProgressException"},
|
1759 | 1759 | {"shape":"UnauthenticatedException"}
|
1760 | 1760 | ],
|
1761 |
| - "documentation":"<p>Stops a specific Amazon Lightsail instance that is currently running.</p> <p>The <code>stop instance</code> operation supports tag-based access control via resource tags applied to the resource identified by instanceName. For more information, see the <a href=\"https://lightsail.aws.amazon.com/ls/docs/en/articles/amazon-lightsail-controlling-access-using-tags\">Lightsail Dev Guide</a>.</p>" |
| 1761 | + "documentation":"<p>Stops a specific Amazon Lightsail instance that is currently running.</p> <note> <p>When you start a stopped instance, Lightsail assigns a new public IP address to the instance. To use the same IP address after stopping and starting an instance, create a static IP address and attach it to the instance. For more information, see the <a href=\"https://lightsail.aws.amazon.com/ls/docs/en/articles/lightsail-create-static-ip\">Lightsail Dev Guide</a>.</p> </note> <p>The <code>stop instance</code> operation supports tag-based access control via resource tags applied to the resource identified by instanceName. For more information, see the <a href=\"https://lightsail.aws.amazon.com/ls/docs/en/articles/amazon-lightsail-controlling-access-using-tags\">Lightsail Dev Guide</a>.</p>" |
1762 | 1762 | },
|
1763 | 1763 | "StopRelationalDatabase":{
|
1764 | 1764 | "name":"StopRelationalDatabase",
|
|
2435 | 2435 | },
|
2436 | 2436 | "CreateDiskSnapshotRequest":{
|
2437 | 2437 | "type":"structure",
|
2438 |
| - "required":[ |
2439 |
| - "diskName", |
2440 |
| - "diskSnapshotName" |
2441 |
| - ], |
| 2438 | + "required":["diskSnapshotName"], |
2442 | 2439 | "members":{
|
2443 | 2440 | "diskName":{
|
2444 | 2441 | "shape":"ResourceName",
|
2445 |
| - "documentation":"<p>The unique name of the source disk (e.g., <code>my-source-disk</code>).</p>" |
| 2442 | + "documentation":"<p>The unique name of the source disk (e.g., <code>Disk-Virginia-1</code>).</p> <note> <p>This parameter cannot be defined together with the <code>instance name</code> parameter. The <code>disk name</code> and <code>instance name</code> parameters are mutually exclusive.</p> </note>" |
2446 | 2443 | },
|
2447 | 2444 | "diskSnapshotName":{
|
2448 | 2445 | "shape":"ResourceName",
|
2449 | 2446 | "documentation":"<p>The name of the destination disk snapshot (e.g., <code>my-disk-snapshot</code>) based on the source disk.</p>"
|
2450 | 2447 | },
|
| 2448 | + "instanceName":{ |
| 2449 | + "shape":"ResourceName", |
| 2450 | + "documentation":"<p>The unique name of the source instance (e.g., <code>Amazon_Linux-512MB-Virginia-1</code>). When this is defined, a snapshot of the instance's system volume is created.</p> <note> <p>This parameter cannot be defined together with the <code>disk name</code> parameter. The <code>instance name</code> and <code>disk name</code> parameters are mutually exclusive.</p> </note>" |
| 2451 | + }, |
2451 | 2452 | "tags":{
|
2452 | 2453 | "shape":"TagList",
|
2453 | 2454 | "documentation":"<p>The tag keys and optional values to add to the resource during create.</p> <p>To tag a resource after it has been created, see the <code>tag resource</code> operation.</p>"
|
|
3391 | 3392 | },
|
3392 | 3393 | "fromDiskName":{
|
3393 | 3394 | "shape":"ResourceName",
|
3394 |
| - "documentation":"<p>The unique name of the source disk from which you are creating the disk snapshot.</p>" |
| 3395 | + "documentation":"<p>The unique name of the source disk from which the disk snapshot was created.</p>" |
3395 | 3396 | },
|
3396 | 3397 | "fromDiskArn":{
|
3397 | 3398 | "shape":"NonEmptyString",
|
3398 |
| - "documentation":"<p>The Amazon Resource Name (ARN) of the source disk from which you are creating the disk snapshot.</p>" |
| 3399 | + "documentation":"<p>The Amazon Resource Name (ARN) of the source disk from which the disk snapshot was created.</p>" |
| 3400 | + }, |
| 3401 | + "fromInstanceName":{ |
| 3402 | + "shape":"ResourceName", |
| 3403 | + "documentation":"<p>The unique name of the source instance from which the disk (system volume) snapshot was created.</p>" |
| 3404 | + }, |
| 3405 | + "fromInstanceArn":{ |
| 3406 | + "shape":"NonEmptyString", |
| 3407 | + "documentation":"<p>The Amazon Resource Name (ARN) of the source instance from which the disk (system volume) snapshot was created.</p>" |
3399 | 3408 | }
|
3400 | 3409 | },
|
3401 | 3410 | "documentation":"<p>Describes a block storage disk snapshot.</p>"
|
|
4888 | 4897 | },
|
4889 | 4898 | "portInfoSource":{
|
4890 | 4899 | "shape":"PortInfoSourceType",
|
4891 |
| - "documentation":"<p>The port configuration to use for the new Amazon EC2 instance.</p> <p>The following configuration options are available:</p> <ul> <li> <p>DEFAULT — Use the default firewall settings from the image.</p> </li> <li> <p>INSTANCE — Use the firewall settings from the source Lightsail instance.</p> </li> <li> <p>NONE — Default to Amazon EC2.</p> </li> </ul>" |
| 4900 | + "documentation":"<p>The port configuration to use for the new Amazon EC2 instance.</p> <p>The following configuration options are available:</p> <ul> <li> <p>DEFAULT — Use the default firewall settings from the image.</p> </li> <li> <p>INSTANCE — Use the firewall settings from the source Lightsail instance.</p> </li> <li> <p>NONE — Default to Amazon EC2.</p> </li> <li> <p>CLOSED — All ports closed.</p> </li> </ul>" |
4892 | 4901 | },
|
4893 | 4902 | "userData":{
|
4894 | 4903 | "shape":"string",
|
|
6029 | 6038 | "enum":[
|
6030 | 6039 | "DEFAULT",
|
6031 | 6040 | "INSTANCE",
|
6032 |
| - "NONE" |
| 6041 | + "NONE", |
| 6042 | + "CLOSED" |
6033 | 6043 | ]
|
6034 | 6044 | },
|
6035 | 6045 | "PortList":{
|
|
0 commit comments