id
stringlengths 14
16
| text
stringlengths 1
2.43k
| source
stringlengths 99
229
|
|---|---|---|
ec69281896e3-1 | ```
aws ec2 stop-instances --instance-ids i-1234567890abcdef0
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/spot-requests.md |
c3db82bc5f82-0 | You can start a Spot Instance that you previously stopped\. The steps for starting a Spot Instance are similar to the steps for starting an On\-Demand Instance\.
**Prerequisites**
You can only start a Spot Instance if:
+ You manually stopped the Spot Instance\.
+ The Spot Instance is an EBS\-backed instance\.
+ Spot Instance capacity is available\.
+ The Spot price is lower than your maximum price\.
**Limitations**
+ You can't start a Spot Instance if it is part of fleet or launch group, Availability Zone group, or Spot block\.
**To start a Spot Instance \(console\)**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the navigation pane, choose **Instances** and select the Spot Instance\.
1. Choose **Actions**, **Instance State**, **Start**\.
**To start a Spot Instance \(AWS CLI\)**
+ Use the [start\-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/start-instances.html) command to manually start one or more Spot Instances\.
```
aws ec2 start-instances --instance-ids i-1234567890abcdef0 | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/spot-requests.md |
c3db82bc5f82-1 | ```
aws ec2 start-instances --instance-ids i-1234567890abcdef0
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/spot-requests.md |
0bc005c74ef9-0 | If your Spot Instance request is `active` and has an associated running Spot Instance, or your Spot Instance request is `disabled` and has an associated stopped Spot Instance, canceling the request does not terminate the instance; you must terminate the running Spot Instance manually\. If you terminate a running or stopped Spot Instance that was launched by a persistent Spot request, the Spot request returns to the `open` state so that a new Spot Instance can be launched\. To cancel a persistent Spot request and terminate its Spot Instances, you must cancel the Spot request first and then terminate the Spot Instances\. Otherwise, the persistent Spot request can launch a new instance\. For more information about canceling a Spot Instance request, see [Canceling a Spot Instance request](#using-spot-instances-cancel)\.
**To manually terminate a Spot Instance \(AWS CLI\)**
+ Use the [terminate\-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/terminate-instances.html) command to manually terminate Spot Instances\.
```
aws ec2 terminate-instances --instance-ids i-1234567890abcdef0 i-0598c7d356eba48d7
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/spot-requests.md |
72fc41ac5f2d-0 | You can use the AMI tools commands to create and manage instance store\-backed Linux AMIs\. To set up the tools, see [Setting up the AMI tools](set-up-ami-tools.md)\.
For information about your access keys, see [Best Practices for Managing AWS Access Keys](https://docs.aws.amazon.com/general/latest/gr/aws-access-keys-best-practices.html)\.
**Topics**
+ [ec2\-ami\-tools\-version](#ami-tools-version)
+ [ec2\-bundle\-image](#ami-bundle-image)
+ [ec2\-bundle\-vol](#ami-bundle-vol)
+ [ec2\-delete\-bundle](#ami-delete-bundle)
+ [ec2\-download\-bundle](#ami-download-bundle)
+ [ec2\-migrate\-manifest](#ami-migrate-manifest)
+ [ec2\-unbundle](#ami-unbundle)
+ [ec2\-upload\-bundle](#ami-upload-bundle)
+ [Common options for AMI tools](#common-args-ami) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ami-tools-commands.md |
0dd9d7633f72-0 | Describes the version of the AMI tools\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ami-tools-commands.md |
8f13d4504244-0 | **ec2\-ami\-tools\-version** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ami-tools-commands.md |
e81e9e0f294a-0 | The version information\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ami-tools-commands.md |
d5e030ea7ba8-0 | This example command displays the version information for the AMI tools that you're using\.
```
[ec2-user ~]$ ec2-ami-tools-version
1.5.2 20071010
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ami-tools-commands.md |
d44ba03c25b4-0 | Creates an instance store\-backed Linux AMI from an operating system image created in a loopback file\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ami-tools-commands.md |
42b0be268abf-0 | **ec2\-bundle\-image \-c *path* \-k *path* \-u *account* \-i *path* \[\-d *path*\] \[\-\-ec2cert *path*\] \[\-r *architecture*\] \[\-\-productcodes *code1*,*code2*,\.\.\.\] \[\-B *mapping*\] \[\-p *prefix*\]** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ami-tools-commands.md |
524176644b83-0 | `-c, --cert` *path*
The user's PEM encoded RSA public key certificate file\.
Required: Yes
`-k, --privatekey` *path*
The path to a PEM\-encoded RSA key file\. You'll need to specify this key to unbundle this bundle, so keep it in a safe place\. Note that the key doesn't have to be registered to your AWS account\.
Required: Yes
`-u, --user ` *account*
The user's AWS account ID, without dashes\.
Required: Yes
`-i, --image` *path*
The path to the image to bundle\.
Required: Yes
`-d, --destination` *path*
The directory in which to create the bundle\.
Default: `/tmp`
Required: No
`--ec2cert` *path*
The path to the Amazon EC2 X\.509 public key certificate used to encrypt the image manifest\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ami-tools-commands.md |
524176644b83-1 | The path to the Amazon EC2 X\.509 public key certificate used to encrypt the image manifest\.
The `us-gov-west-1` and `cn-north-1` Regions use a non\-default public key certificate and the path to that certificate must be specified with this option\. The path to the certificate varies based on the installation method of the AMI tools\. For Amazon Linux, the certificates are located at `/opt/aws/amitools/ec2/etc/ec2/amitools/`\. If you installed the AMI tools from the RPM or ZIP file in [Setting up the AMI tools](set-up-ami-tools.md), the certificates are located at `$EC2_AMITOOL_HOME/etc/ec2/amitools/`\.
Required: Only for the `us-gov-west-1` and `cn-north-1` Regions\.
`-r, --arch` *architecture*
Image architecture\. If you don't provide the architecture on the command line, you'll be prompted for it when bundling starts\.
Valid values: `i386` \| `x86_64`
Required: No
`--productcodes` *code1,code2,\.\.\.*
Product codes to attach to the image at registration time, separated by commas\.
Required: No
`-B, --block-device-mapping` *mapping*
Defines how block devices are exposed to an instance of this AMI if its instance type supports the specified device\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ami-tools-commands.md |
524176644b83-2 | Defines how block devices are exposed to an instance of this AMI if its instance type supports the specified device\.
Specify a comma\-separated list of key\-value pairs, where each key is a virtual name and each value is the corresponding device name\. Virtual names include the following:
+ `ami`—The root file system device, as seen by the instance
+ `root`—The root file system device, as seen by the kernel
+ `swap`—The swap device, as seen by the instance
+ `ephemeralN`—The Nth instance store volume
Required: No
`-p, --prefix` *prefix*
The filename prefix for bundled AMI files\.
Default: The name of the image file\. For example, if the image path is `/var/spool/my-image/version-2/debian.img`, then the default prefix is `debian.img`\.
Required: No
`--kernel` *kernel\_id*
Deprecated\. Use [register\-image](https://docs.aws.amazon.com/cli/latest/reference/ec2/register-image.html) to set the kernel\.
Required: No
`--ramdisk` *ramdisk\_id*
Deprecated\. Use [register\-image](https://docs.aws.amazon.com/cli/latest/reference/ec2/register-image.html) to set the RAM disk if required\.
Required: No | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ami-tools-commands.md |
6a4fd0102a23-0 | Status messages describing the stages and status of the bundling process\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ami-tools-commands.md |
7afc3591d6ff-0 | This example creates a bundled AMI from an operating system image that was created in a loopback file\.
```
[ec2-user ~]$ ec2-bundle-image -k pk-HKZYKTAIG2ECMXYIBH3HXV4ZBEXAMPLE.pem -c cert-HKZYKTAIG2ECMXYIBH3HXV4ZBEXAMPLE.pem -u 111122223333 -i image.img -d bundled/ -r x86_64
Please specify a value for arch [i386]:
Bundling image file...
Splitting bundled/image.gz.crypt...
Created image.part.00
Created image.part.01
Created image.part.02
Created image.part.03
Created image.part.04
Created image.part.05
Created image.part.06
Created image.part.07
Created image.part.08
Created image.part.09
Created image.part.10
Created image.part.11
Created image.part.12
Created image.part.13
Created image.part.14
Generating digests for each part...
Digests generated.
Creating bundle manifest...
ec2-bundle-image complete.
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ami-tools-commands.md |
f5d4808266eb-0 | Creates an instance store\-backed Linux AMI by compressing, encrypting, and signing a copy of the root device volume for the instance\.
Amazon EC2 attempts to inherit product codes, kernel settings, RAM disk settings, and block device mappings from the instance\.
By default, the bundle process excludes files that might contain sensitive information\. These files include `*.sw`, `*.swo`, `*.swp`, `*.pem`, `*.priv`, `*id_rsa*`, `*id_dsa*` `*.gpg`, `*.jks`, `*/.ssh/authorized_keys`, and `*/.bash_history`\. To include all of these files, use the `--no-filter` option\. To include some of these files, use the `--include` option\.
For more information, see [Creating an instance store\-backed Linux AMI](creating-an-ami-instance-store.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ami-tools-commands.md |
9f0665a55464-0 | **ec2\-bundle\-vol \-c *path* \-k *path* \-u *account* \[\-d *path*\] \[\-\-ec2cert *path*\] \[\-r *architecture*\] \[\-\-productcodes *code1*,*code2*,\.\.\.\] \[\-B *mapping*\] \[\-\-all\] \[\-e *directory1*,*directory2*,\.\.\.\] \[\-i *file1*,*file2*,\.\.\.\] \[\-\-no\-filter\] \[\-p *prefix*\] \[\-s *size*\] \[\-\-\[no\-\]inherit\] \[\-v *volume*\] \[\-P *type*\] \[\-S *script*\] \[\-\-fstab *path*\] | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ami-tools-commands.md |
9f0665a55464-1 | \[\-S *script*\] \[\-\-fstab *path*\] \[\-\-generate\-fstab\] \[\-\-grub\-config *path*\]** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ami-tools-commands.md |
53f5eef2e411-0 | `-c, --cert` *path*
The user's PEM encoded RSA public key certificate file\.
Required: Yes
`-k, --privatekey ` *path*
The path to the user's PEM\-encoded RSA key file\.
Required: Yes
`-u, --user` *account*
The user's AWS account ID, without dashes\.
Required: Yes
`-d, --destination` *destination*
The directory in which to create the bundle\.
Default: `/tmp`
Required: No
`--ec2cert` *path*
The path to the Amazon EC2 X\.509 public key certificate used to encrypt the image manifest\.
The `us-gov-west-1` and `cn-north-1` Regions use a non\-default public key certificate and the path to that certificate must be specified with this option\. The path to the certificate varies based on the installation method of the AMI tools\. For Amazon Linux, the certificates are located at `/opt/aws/amitools/ec2/etc/ec2/amitools/`\. If you installed the AMI tools from the RPM or ZIP file in [Setting up the AMI tools](set-up-ami-tools.md), the certificates are located at `$EC2_AMITOOL_HOME/etc/ec2/amitools/`\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ami-tools-commands.md |
53f5eef2e411-1 | Required: Only for the `us-gov-west-1` and `cn-north-1` Regions\.
`-r, --arch ` *architecture*
The image architecture\. If you don't provide this on the command line, you'll be prompted to provide it when the bundling starts\.
Valid values: `i386` \| `x86_64`
Required: No
`--productcodes` *code1,code2,\.\.\.*
Product codes to attach to the image at registration time, separated by commas\.
Required: No
`-B, --block-device-mapping` *mapping*
Defines how block devices are exposed to an instance of this AMI if its instance type supports the specified device\.
Specify a comma\-separated list of key\-value pairs, where each key is a virtual name and each value is the corresponding device name\. Virtual names include the following:
+ `ami`—The root file system device, as seen by the instance
+ `root`—The root file system device, as seen by the kernel
+ `swap`—The swap device, as seen by the instance
+ `ephemeralN`—The Nth instance store volume
Required: No
`-a, --all`
Bundle all directories, including those on remotely mounted file systems\.
Required: No
`-e, --exclude ` *directory1,directory2,\.\.\.* | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ami-tools-commands.md |
53f5eef2e411-2 | Required: No
`-e, --exclude ` *directory1,directory2,\.\.\.*
A list of absolute directory paths and files to exclude from the bundle operation\. This parameter overrides the `--all` option\. When exclude is specified, the directories and subdirectories listed with the parameter will not be bundled with the volume\.
Required: No
`-i, --include ` *file1,file2,\.\.\.*
A list of files to include in the bundle operation\. The specified files would otherwise be excluded from the AMI because they might contain sensitive information\.
Required: No
`--no-filter`
If specified, we won't exclude files from the AMI because they might contain sensitive information\.
Required: No
`-p, --prefix ` *prefix*
The file name prefix for bundled AMI files\.
Default: `image`
Required: No
`-s, --size` *size*
The size, in MB \(1024 \* 1024 bytes\), of the image file to create\. The maximum size is 10240 MB\.
Default: 10240
Required: No
`--[no-]inherit`
Indicates whether the image should inherit the instance's metadata \(the default is to inherit\)\. Bundling fails if you enable `--inherit` but the instance metadata is not accessible\.
Required: No | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ami-tools-commands.md |
53f5eef2e411-3 | Required: No
`-v, --volume ` *volume*
The absolute path to the mounted volume from which to create the bundle\.
Default: The root directory \(/\)
Required: No
`-P, --partition` *type*
Indicates whether the disk image should use a partition table\. If you don't specify a partition table type, the default is the type used on the parent block device of the volume, if applicable, otherwise the default is `gpt`\.
Valid values: `mbr` \| `gpt` \| `none`
Required: No
`-S, --script` *script*
A customization script to be run right before bundling\. The script must expect a single argument, the mount point of the volume\.
Required: No
`--fstab` *path*
The path to the fstab to bundle into the image\. If this is not specified, Amazon EC2 bundles /etc/fstab\.
Required: No
`--generate-fstab`
Bundles the volume using an Amazon EC2\-provided fstab\.
Required: No
`--grub-config` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ami-tools-commands.md |
53f5eef2e411-4 | Bundles the volume using an Amazon EC2\-provided fstab\.
Required: No
`--grub-config`
The path to an alternate grub configuration file to bundle into the image\. By default, `ec2-bundle-vol` expects either `/boot/grub/menu.lst` or `/boot/grub/grub.conf` to exist on the cloned image\. This option allows you to specify a path to an alternative grub configuration file, which will then be copied over the defaults \(if present\)\.
Required: No
`--kernel` *kernel\_id*
Deprecated\. Use [register\-image](https://docs.aws.amazon.com/cli/latest/reference/ec2/register-image.html) to set the kernel\.
Required: No
`--ramdisk`*ramdisk\_id*
Deprecated\. Use [register\-image](https://docs.aws.amazon.com/cli/latest/reference/ec2/register-image.html) to set the RAM disk if required\.
Required: No | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ami-tools-commands.md |
0e4f027886a0-0 | Status messages describing the stages and status of the bundling\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ami-tools-commands.md |
c2a1a8338852-0 | This example creates a bundled AMI by compressing, encrypting and signing a snapshot of the local machine's root file system\.
```
[ec2-user ~]$ ec2-bundle-vol -d /mnt -k pk-HKZYKTAIG2ECMXYIBH3HXV4ZBEXAMPLE.pem -c cert-HKZYKTAIG2ECMXYIBH3HXV4ZBEXAMPLE.pem -u 111122223333 -r x86_64
Copying / into the image file /mnt/image...
Excluding:
sys
dev/shm
proc
dev/pts
proc/sys/fs/binfmt_misc
dev
media
mnt
proc
sys
tmp/image
mnt/img-mnt
1+0 records in
1+0 records out
mke2fs 1.38 (30-Jun-2005)
warning: 256 blocks unused.
Splitting /mnt/image.gz.crypt...
Created image.part.00
Created image.part.01
Created image.part.02
Created image.part.03
...
Created image.part.22
Created image.part.23
Generating digests for each part...
Digests generated. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ami-tools-commands.md |
c2a1a8338852-1 | Created image.part.22
Created image.part.23
Generating digests for each part...
Digests generated.
Creating bundle manifest...
Bundle Volume complete.
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ami-tools-commands.md |
24360b1dc2f7-0 | Deletes the specified bundle from Amazon S3 storage\. After you delete a bundle, you can't launch instances from the corresponding AMI\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ami-tools-commands.md |
b76e14c5888b-0 | **ec2\-delete\-bundle \-b *bucket* \-a *access\_key\_id* \-s *secret\_access\_key* \[\-t *token*\] \[\-\-url *url*\] \[\-\-region *region*\] \[\-\-sigv *version*\] \[\-m *path*\] \[\-p *prefix*\] \[\-\-clear\] \[\-\-retry\] \[\-y\]** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ami-tools-commands.md |
6e4144972769-0 | `-b, --bucket `*bucket*
The name of the Amazon S3 bucket containing the bundled AMI, followed by an optional '/'\-delimited path prefix
Required: Yes
`-a, --access-key` *access\_key\_id*
The AWS access key ID\.
Required: Yes
`-s, --secret-key` *secret\_access\_key*
The AWS secret access key\.
Required: Yes
`-t, --delegation-token` *token*
The delegation token to pass along to the AWS request\. For more information, see the [Using Temporary Security Credentials](https://docs.aws.amazon.com/STS/latest/UsingSTS/)\.
Required: Only when you are using temporary security credentials\.
Default: The value of the `AWS_DELEGATION_TOKEN` environment variable \(if set\)\.
`--region`*region*
The Region to use in the request signature\.
Default: `us-east-1`
Required: Required if using signature version 4
`--sigv`*version*
The signature version to use when signing the request\.
Valid values: `2` \| `4`
Default: `4`
Required: No
`-m, --manifest`*path*
The path to the manifest file\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ami-tools-commands.md |
6e4144972769-1 | Required: No
`-m, --manifest`*path*
The path to the manifest file\.
Required: You must specify `--prefix` or `--manifest`\.
`-p, --prefix` *prefix*
The bundled AMI filename prefix\. Provide the entire prefix\. For example, if the prefix is image\.img, use `-p image.img` and not `-p image`\.
Required: You must specify `--prefix` or `--manifest`\.
`--clear`
Deletes the Amazon S3 bucket if it's empty after deleting the specified bundle\.
Required: No
`--retry`
Automatically retries on all Amazon S3 errors, up to five times per operation\.
Required: No
`-y, --yes`
Automatically assumes the answer to all prompts is yes\.
Required: No | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ami-tools-commands.md |
1a769a92ed94-0 | Amazon EC2 displays status messages indicating the stages and status of the delete process\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ami-tools-commands.md |
8b1e871f52c3-0 | This example deletes a bundle from Amazon S3\.
```
[ec2-user ~]$ ec2-delete-bundle -b DOC-EXAMPLE-BUCKET1 -a your_access_key_id -s your_secret_access_key
Deleting files:
DOC-EXAMPLE-BUCKET1/image.manifest.xml
DOC-EXAMPLE-BUCKET1/image.part.00
DOC-EXAMPLE-BUCKET1/image.part.01
DOC-EXAMPLE-BUCKET1/image.part.02
DOC-EXAMPLE-BUCKET1/image.part.03
DOC-EXAMPLE-BUCKET1/image.part.04
DOC-EXAMPLE-BUCKET1/image.part.05
DOC-EXAMPLE-BUCKET1/image.part.06
Continue? [y/n]
y
Deleted DOC-EXAMPLE-BUCKET1/image.manifest.xml
Deleted DOC-EXAMPLE-BUCKET1/image.part.00
Deleted DOC-EXAMPLE-BUCKET1/image.part.01
Deleted DOC-EXAMPLE-BUCKET1/image.part.02
Deleted DOC-EXAMPLE-BUCKET1/image.part.03
Deleted DOC-EXAMPLE-BUCKET1/image.part.04
Deleted DOC-EXAMPLE-BUCKET1/image.part.05
Deleted DOC-EXAMPLE-BUCKET1/image.part.06
ec2-delete-bundle complete.
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ami-tools-commands.md |
a2e97383ba56-0 | Downloads the specified instance store\-backed Linux AMIs from Amazon S3 storage\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ami-tools-commands.md |
fcb25c52646e-0 | **ec2\-download\-bundle \-b *bucket* \-a *access\_key\_id* \-s *secret\_access\_key* \-k *path* \[\-\-url *url*\] \[\-\-region *region*\] \[\-\-sigv *version*\] \[\-m *file*\] \[\-p *prefix*\] \[\-d *directory*\] \[\-\-retry\]** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ami-tools-commands.md |
5c7ded445a2f-0 | `-b, --bucket` *bucket*
The name of the Amazon S3 bucket where the bundle is located, followed by an optional '/'\-delimited path prefix\.
Required: Yes
`-a, --access-key` *access\_key\_id*
The AWS access key ID\.
Required: Yes
`-s, --secret-key` *secret\_access\_key*
The AWS secret access key\.
Required: Yes
`-k, --privatekey` *path*
The private key used to decrypt the manifest\.
Required: Yes
`--url` *url*
The Amazon S3 service URL\.
Default: `https://s3.amazonaws.com/`
Required: No
`--region` *region*
The Region to use in the request signature\.
Default: `us-east-1`
Required: Required if using signature version 4
`--sigv` *version*
The signature version to use when signing the request\.
Valid values: `2` \| `4`
Default: `4`
Required: No
`-m, --manifest` *file* | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ami-tools-commands.md |
5c7ded445a2f-1 | Default: `4`
Required: No
`-m, --manifest` *file*
The name of the manifest file \(without the path\)\. We recommend that you specify either the manifest \(`-m`\) or a prefix \(`-p`\)\.
Required: No
`-p, --prefix ` *prefix*
The filename prefix for the bundled AMI files\.
Default: `image`
Required: No
`-d, --directory ` *directory*
The directory where the downloaded bundle is saved\. The directory must exist\.
Default: The current working directory\.
Required: No
`--retry`
Automatically retries on all Amazon S3 errors, up to five times per operation\.
Required: No | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ami-tools-commands.md |
fff01b405cc3-0 | Status messages indicating the various stages of the download process are displayed\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ami-tools-commands.md |
19be5e48c1fe-0 | This example creates the `bundled` directory \(using the Linux mkdir command\) and downloads the bundle from the `DOC-EXAMPLE-BUCKET1` Amazon S3 bucket\.
```
[ec2-user ~]$ mkdir bundled
[ec2-user ~]$ ec2-download-bundle -b DOC-EXAMPLE-BUCKET1/bundles/bundle_name -m image.manifest.xml -a your_access_key_id -s your_secret_access_key -k pk-HKZYKTAIG2ECMXYIBH3HXV4ZBEXAMPLE.pem -d mybundle
Downloading manifest image.manifest.xml from DOC-EXAMPLE-BUCKET1 to mybundle/image.manifest.xml ...
Downloading part image.part.00 from DOC-EXAMPLE-BUCKET1/bundles/bundle_name to mybundle/image.part.00 ...
Downloaded image.part.00 from DOC-EXAMPLE-BUCKET1
Downloading part image.part.01 from DOC-EXAMPLE-BUCKET1/bundles/bundle_name to mybundle/image.part.01 ...
Downloaded image.part.01 from DOC-EXAMPLE-BUCKET1
Downloading part image.part.02 from DOC-EXAMPLE-BUCKET1/bundles/bundle_name to mybundle/image.part.02 ...
Downloaded image.part.02 from DOC-EXAMPLE-BUCKET1
Downloading part image.part.03 from DOC-EXAMPLE-BUCKET1/bundles/bundle_name to mybundle/image.part.03 ... | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ami-tools-commands.md |
19be5e48c1fe-1 | Downloading part image.part.03 from DOC-EXAMPLE-BUCKET1/bundles/bundle_name to mybundle/image.part.03 ...
Downloaded image.part.03 from DOC-EXAMPLE-BUCKET1
Downloading part image.part.04 from DOC-EXAMPLE-BUCKET1/bundles/bundle_name to mybundle/image.part.04 ...
Downloaded image.part.04 from DOC-EXAMPLE-BUCKET1
Downloading part image.part.05 from DOC-EXAMPLE-BUCKET1/bundles/bundle_name to mybundle/image.part.05 ...
Downloaded image.part.05 from DOC-EXAMPLE-BUCKET1
Downloading part image.part.06 from DOC-EXAMPLE-BUCKET1/bundles/bundle_name to mybundle/image.part.06 ...
Downloaded image.part.06 from DOC-EXAMPLE-BUCKET1
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ami-tools-commands.md |
4c4b6f6a93e3-0 | Modifies an instance store\-backed Linux AMI \(for example, its certificate, kernel, and RAM disk\) so that it supports a different Region\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ami-tools-commands.md |
d5a4c27c3e4f-0 | **ec2\-migrate\-manifest \-c *path* \-k *path* \-m *path* \{\(\-a *access\_key\_id* \-s *secret\_access\_key* \-\-region *region*\) \| \(\-\-no\-mapping\)\} \[\-\-ec2cert *ec2\_cert\_path*\] \[\-\-kernel *kernel\-id*\] \[\-\-ramdisk *ramdisk\_id*\]** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ami-tools-commands.md |
d5abd2af862f-0 | `-c, --cert` *path*
The user's PEM encoded RSA public key certificate file\.
Required: Yes
`-k, --privatekey` *path*
The path to the user's PEM\-encoded RSA key file\.
Required: Yes
`--manifest` *path*
The path to the manifest file\.
Required: Yes
`-a, --access-key` *access\_key\_id*
The AWS access key ID\.
Required: Required if using automatic mapping\.
`-s, --secret-key ` *secret\_access\_key*
The AWS secret access key\.
Required: Required if using automatic mapping\.
`--region` *region*
The Region to look up in the mapping file\.
Required: Required if using automatic mapping\.
`--no-mapping`
Disables automatic mapping of kernels and RAM disks\.
During migration, Amazon EC2 replaces the kernel and RAM disk in the manifest file with a kernel and RAM disk designed for the destination region\. Unless the `--no-mapping` parameter is given, `ec2-migrate-bundle` might use the `DescribeRegions` and `DescribeImages` operations to perform automated mappings\.
Required: Required if you're not providing the `-a`, `-s`, and `--region` options used for automatic mapping\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ami-tools-commands.md |
d5abd2af862f-1 | Required: Required if you're not providing the `-a`, `-s`, and `--region` options used for automatic mapping\.
`--ec2cert` *path*
The path to the Amazon EC2 X\.509 public key certificate used to encrypt the image manifest\.
The `us-gov-west-1` and `cn-north-1` Regions use a non\-default public key certificate and the path to that certificate must be specified with this option\. The path to the certificate varies based on the installation method of the AMI tools\. For Amazon Linux, the certificates are located at `/opt/aws/amitools/ec2/etc/ec2/amitools/`\. If you installed the AMI tools from the ZIP file in [Setting up the AMI tools](set-up-ami-tools.md), the certificates are located at `$EC2_AMITOOL_HOME/etc/ec2/amitools/`\.
Required: Only for the `us-gov-west-1` and `cn-north-1` Regions\.
`--kernel` *kernel\_id*
The ID of the kernel to select\.
We recommend that you use PV\-GRUB instead of kernels and RAM disks\. For more information, see [User provided kernels](UserProvidedKernels.md)\.
Required: No
`--ramdisk` *ramdisk\_id*
The ID of the RAM disk to select\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ami-tools-commands.md |
d5abd2af862f-2 | Required: No
`--ramdisk` *ramdisk\_id*
The ID of the RAM disk to select\.
We recommend that you use PV\-GRUB instead of kernels and RAM disks\. For more information, see [User provided kernels](UserProvidedKernels.md)\.
Required: No | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ami-tools-commands.md |
39a4f1eb956a-0 | Status messages describing the stages and status of the bundling process\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ami-tools-commands.md |
466474d07c5d-0 | This example copies the AMI specified in the `my-ami.manifest.xml` manifest from the US to the EU\.
```
[ec2-user ~]$ ec2-migrate-manifest --manifest my-ami.manifest.xml --cert cert-HKZYKTAIG2ECMXYIBH3HXV4ZBZQ55CLO.pem --privatekey pk-HKZYKTAIG2ECMXYIBH3HXV4ZBZQ55CLO.pem --region eu-west-1
Backing up manifest...
Successfully migrated my-ami.manifest.xml It is now suitable for use in eu-west-1.
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ami-tools-commands.md |
d8964e574a44-0 | Re\-creates the bundle from an instance store\-backed Linux AMI\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ami-tools-commands.md |
3a5572308862-0 | **ec2\-unbundle \-k *path* \-m *path* \[\-s *source\_directory*\] \[\-d *destination\_directory*\]** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ami-tools-commands.md |
fb588125ed7c-0 | `-k, --privatekey` *path*
The path to your PEM\-encoded RSA key file\.
Required: Yes
`-m, --manifest` *path*
The path to the manifest file\.
Required: Yes
`-s, --source` *source\_directory*
The directory containing the bundle\.
Default: The current directory\.
Required: No
`-d, --destination` *destination\_directory*
The directory in which to unbundle the AMI\. The destination directory must exist\.
Default: The current directory\.
Required: No | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ami-tools-commands.md |
3cbc2f5005d7-0 | This Linux and UNIX example unbundles the AMI specified in the `image.manifest.xml` file\.
```
[ec2-user ~]$ mkdir unbundled
$ ec2-unbundle -m mybundle/image.manifest.xml -k pk-HKZYKTAIG2ECMXYIBH3HXV4ZBEXAMPLE.pem -s mybundle -d unbundled
$ ls -l unbundled
total 1025008
-rw-r--r-- 1 root root 1048578048 Aug 25 23:46 image.img
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ami-tools-commands.md |
4dd2b7e66909-0 | Status messages indicating the various stages of the unbundling process are displayed\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ami-tools-commands.md |
b9494b9a224a-0 | Uploads the bundle for an instance store\-backed Linux AMI to Amazon S3 and sets the appropriate ACLs on the uploaded objects\. For more information, see [Creating an instance store\-backed Linux AMI](creating-an-ami-instance-store.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ami-tools-commands.md |
4d4c0ba28fc1-0 | **ec2\-upload\-bundle \-b *bucket* \-a *access\_key\_id* \-s *secret\_access\_key* \[\-t *token*\] \-m *path* \[\-\-url *url*\] \[\-\-region *region*\] \[\-\-sigv *version*\] \[\-\-acl *acl*\] \[\-d *directory*\] \[\-\-part *part*\] \[\-\-retry\] \[\-\-skipmanifest\]** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ami-tools-commands.md |
371cd491e467-0 | `-b, --bucket` *bucket*
The name of the Amazon S3 bucket in which to store the bundle, followed by an optional '/'\-delimited path prefix\. If the bucket doesn't exist, it's created if the bucket name is available\.
Required: Yes
`-a, --access-key` *access\_key\_id*
Your AWS access key ID\.
Required: Yes
`-s, --secret-key` *secret\_access\_key*
Your AWS secret access key\.
Required: Yes
`-t, --delegation-token` *token*
The delegation token to pass along to the AWS request\. For more information, see the [Using Temporary Security Credentials](https://docs.aws.amazon.com/STS/latest/UsingSTS/)\.
Required: Only when you are using temporary security credentials\.
Default: The value of the `AWS_DELEGATION_TOKEN` environment variable \(if set\)\.
`-m, --manifest` *path*
The path to the manifest file\. The manifest file is created during the bundling process and can be found in the directory containing the bundle\.
Required: Yes
`--url` *url* | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ami-tools-commands.md |
371cd491e467-1 | Required: Yes
`--url` *url*
Deprecated\. Use the `--region` option instead unless your bucket is constrained to the `EU` location \(and not `eu-west-1`\)\. The `--location` flag is the only way to target that specific location restraint\.
The Amazon S3 endpoint service URL\.
Default: `https://s3.amazonaws.com/`
Required: No
`--region` *region*
The Region to use in the request signature for the destination S3 bucket\.
+ If the bucket doesn't exist and you don't specify a Region, the tool creates the bucket without a location constraint \(in `us-east-1`\)\.
+ If the bucket doesn't exist and you specify a Region, the tool creates the bucket in the specified Region\.
+ If the bucket exists and you don't specify a Region, the tool uses the bucket's location\.
+ If the bucket exists and you specify `us-east-1` as the Region, the tool uses the bucket's actual location without any error message, any existing matching files are over\-written\.
+ If the bucket exists and you specify a Region \(other than `us-east-1`\) that doesn't match the bucket's actual location, the tool exits with an error\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ami-tools-commands.md |
371cd491e467-2 | If your bucket is constrained to the `EU` location \(and not `eu-west-1`\), use the `--location` flag instead\. The `--location` flag is the only way to target that specific location restraint\.
Default: `us-east-1`
Required: Required if using signature version 4
`--sigv` *version*
The signature version to use when signing the request\.
Valid values: `2` \| `4`
Default: `4`
Required: No
`--acl` *acl*
The access control list policy of the bundled image\.
Valid values: `public-read` \| `aws-exec-read`
Default: `aws-exec-read`
Required: No
`-d, --directory` *directory*
The directory containing the bundled AMI parts\.
Default: The directory containing the manifest file \(see the `-m` option\)\.
Required: No
`--part` *part*
Starts uploading the specified part and all subsequent parts\. For example, `--part 04`\.
Required: No
`--retry`
Automatically retries on all Amazon S3 errors, up to five times per operation\.
Required: No
`--skipmanifest`
Does not upload the manifest\.
Required: No | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ami-tools-commands.md |
371cd491e467-3 | Required: No
`--skipmanifest`
Does not upload the manifest\.
Required: No
`--location` *location*
Deprecated\. Use the `--region` option instead, unless your bucket is constrained to the `EU` location \(and not `eu-west-1`\)\. The `--location` flag is the only way to target that specific location restraint\.
The location constraint of the destination Amazon S3 bucket\. If the bucket exists and you specify a location that doesn't match the bucket's actual location, the tool exits with an error\. If the bucket exists and you don't specify a location, the tool uses the bucket's location\. If the bucket doesn't exist and you specify a location, the tool creates the bucket in the specified location\. If the bucket doesn't exist and you don't specify a location, the tool creates the bucket without a location constraint \(in `us-east-1`\)\.
Default: If `--region` is specified, the location is set to that specified Region\. If `--region` is not specified, the location defaults to `us-east-1`\.
Required: No | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ami-tools-commands.md |
ede764342f1a-0 | Amazon EC2 displays status messages that indicate the stages and status of the upload process\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ami-tools-commands.md |
2ad4404e2eda-0 | This example uploads the bundle specified by the `image.manifest.xml` manifest\.
```
[ec2-user ~]$ ec2-upload-bundle -b DOC-EXAMPLE-BUCKET1/bundles/bundle_name -m image.manifest.xml -a your_access_key_id -s your_secret_access_key
Creating bucket...
Uploading bundled image parts to the S3 bucket DOC-EXAMPLE-BUCKET1 ...
Uploaded image.part.00
Uploaded image.part.01
Uploaded image.part.02
Uploaded image.part.03
Uploaded image.part.04
Uploaded image.part.05
Uploaded image.part.06
Uploaded image.part.07
Uploaded image.part.08
Uploaded image.part.09
Uploaded image.part.10
Uploaded image.part.11
Uploaded image.part.12
Uploaded image.part.13
Uploaded image.part.14
Uploading manifest ...
Uploaded manifest.
Bundle upload completed.
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ami-tools-commands.md |
e49693c4bed3-0 | Most of the AMI tools accept the following optional parameters\.
`--help, -h`
Displays the help message\.
`--version`
Displays the version and copyright notice\.
`--manual`
Displays the manual entry\.
`--batch`
Runs in batch mode, suppressing interactive prompts\.
`--debug`
Displays information that can be useful when troubleshooting problems\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ami-tools-commands.md |
8badad11a09f-0 | If you have created a public AMI, or shared an AMI with another AWS user, you can create a *bookmark* that allows a user to access your AMI and launch an instance in their own account immediately\. This is an easy way to share AMI references, so users don't have to spend time finding your AMI in order to use it\.
Note that your AMI must be public, or you must have shared it with the user to whom you want to send the bookmark\.
**To create a bookmark for your AMI**
1. Type a URL with the following information, where *region* is the Region in which your AMI resides:
```
https://console.aws.amazon.com/ec2/v2/home?region=region#LaunchInstanceWizard:ami=ami_id
```
For example, this URL launches an instance from the ami\-0abcdef1234567890 AMI in the us\-east\-1 Region:
```
https://console.aws.amazon.com/ec2/v2/home?region=us-east-1#LaunchInstanceWizard:ami=ami-0abcdef1234567890
```
1. Distribute the link to users who want to use your AMI\.
1. To use a bookmark, choose the link or copy and paste it into your browser\. The launch wizard opens, with the AMI already selected\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-bookmarks.md |
24a01b915701-0 | The following steps help you to get started with one of the following AWS Deep Learning AMIs:
+ Deep Learning AMI \(Amazon Linux 2\) Version 25\.0 and later
+ Deep Learning AMI \(Amazon Linux\) Version 25\.0 and later
+ Deep Learning AMI \(Ubuntu 18\.04\) Version 25\.0 and later
+ Deep Learning AMI \(Ubuntu 16\.04\) Version 25\.0 and later
For more information, see the [ *AWS Deep Learning AMI User Guide*](https://docs.aws.amazon.com/dlami/latest/devguide/what-is-dlami.html)\.
**Topics**
+ [Step 1: Prepare an EFA\-enabled security group](#nccl-start-dlami-sg)
+ [Step 2: Launch a temporary instance](#nccl-start-dlami-temp)
+ [Step 3: Test your EFA and NCCL configuration](#nccl-start-dlami-test)
+ [Step 4: Install your machine learning applications](#nccl-start-dlami-app)
+ [Step 5: Create an EFA and NCCL\-enabled AMI](#nccl-start-dlami-ami)
+ [Step 6: Terminate the temporary instance](#nccl-start-dlami-terminate)
+ [Step 7: Launch EFA and NCCL\-enabled instances into a cluster placement group](#nccl-start-dlami-cluster) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/efa-start-nccl-dlami.md |
24a01b915701-1 | + [Step 7: Launch EFA and NCCL\-enabled instances into a cluster placement group](#nccl-start-dlami-cluster)
+ [Step 8: Enable passwordless SSH](#nccl-start-dlami-passwordless) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/efa-start-nccl-dlami.md |
f124a06eb37d-0 | An EFA requires a security group that allows all inbound and outbound traffic to and from the security group itself\.
**To create an EFA\-enabled security group**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the navigation pane, choose **Security Groups** and then choose **Create Security Group**\.
1. In the **Create Security Group** window, do the following:
1. For **Security group name**, enter a descriptive name for the security group, such as `EFA-enabled security group`\.
1. \(Optional\) For **Description**, enter a brief description of the security group\.
1. For **VPC**, select the VPC into which you intend to launch your EFA\-enabled instances\.
1. Choose **Create**\.
1. Select the security group that you created, and on the **Description** tab, copy the **Group ID**\.
1. On the **Inbound** and **Outbound** tabs, do the following:
1. Choose **Edit**\.
1. For **Type**, choose **All traffic**\.
1. For **Source**, choose **Custom**\.
1. Paste the security group ID that you copied into the field\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/efa-start-nccl-dlami.md |
f124a06eb37d-1 | 1. For **Source**, choose **Custom**\.
1. Paste the security group ID that you copied into the field\.
1. Choose **Save**\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/efa-start-nccl-dlami.md |
b28a123d77f7-0 | Launch a temporary instance that you can use to install and configure the EFA software components\. You use this instance to create an EFA\-enabled AMI from which you can launch your EFA\-enabled instances\.
**To launch a temporary instance**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. Choose **Launch Instance**\.
1. On the **Choose an AMI** page, choose a supported **AWS Deep Learning AMI Version 25\.0** or later\.
1. On the **Choose an Instance Type** page, select `p3dn.24xlarge` and then choose **Next: Configure Instance Details**\.
1. On the **Configure Instance Details** page, do the following:
1. For **Elastic Fabric Adapter**, choose **Enable**\.
1. In the **Network Interfaces** section, for device **eth0**, choose **New network interface**\.
1. Choose **Next: Add Storage**\.
1. On the **Add Storage** page, specify the volumes to attach to the instances, in addition to the volumes specified by the AMI \(such as the root device volume\)\. Then choose **Next: Add Tags**\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/efa-start-nccl-dlami.md |
b28a123d77f7-1 | 1. On the **Add Tags** page, specify a tag that you can use to identify the temporary instance, and then choose **Next: Configure Security Group**\.
1. On the **Configure Security Group** page, for **Assign a security group**, select **Select an existing security group**\. Then select the security group that you created in **Step 1**\.
1. On the **Review Instance Launch** page, review the settings, and then choose **Launch** to choose a key pair and to launch your instance\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/efa-start-nccl-dlami.md |
0ebe5acc111d-0 | Run a test to ensure that your temporary instance is properly configured for EFA and NCCL\.
**To test your EFA and NCCL configuration**
1. Create a host file that specifies the hosts on which to run the tests\. The following command creates a host file named `my-hosts` that includes a reference to the instance itself\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/efa-start-nccl-dlami.md |
0c0bd7b051cf-0 | ```
[ec2-user ~]$ TOKEN=`curl -X PUT "http://169.254.169.254/latest/api/token" -H "X-aws-ec2-metadata-token-ttl-seconds: 21600"` \
&& curl -H "X-aws-ec2-metadata-token: $TOKEN" –v http://169.254.169.254/latest/meta-data/local-ipv4 >> my-hosts
```
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/efa-start-nccl-dlami.md |
c6a4cfc8940c-0 | ```
[ec2-user ~]$ curl http://169.254.169.254/latest/meta-data/local-ipv4 >> my-hosts
```
------
1. Run the test and specify the host file \(`--hostfile`\) and the number of GPUs to use \(`-n`\)\. The following command runs the `all_reduce_perf` test on 8 GPUs on the instance itself, and specifies the following environment variables\.
+ `FI_PROVIDER="efa"`—specifies the fabric interface provider\. This must be set to `"efa"`\.
+ `FI_EFA_TX_MIN_CREDITS=64`—specifies the minimum number of send credits that the sender requests from the receiver\. `64` is the recommended value for NCCL jobs using EFA\. The value should only be increased for message transfers that are larger than 256 MB\.
+ `NCCL_DEBUG=INFO`—enables detailed debugging output\. You can also specify `VERSION` to print only the NCCL version at the start of the test, or `WARN` to receive only error messages\.
+ `NCCL_TREE_THRESHOLD=0`—disables tree algorithms for the test\.
For more information about the NCCL test arguments, see the [NCCL Tests README](https://github.com/NVIDIA/nccl-tests/blob/master/README.md) in the official nccl\-tests repository\.
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/efa-start-nccl-dlami.md |
c6a4cfc8940c-1 | ```
/opt/amazon/openmpi/bin/mpirun \
-x FI_PROVIDER="efa" \
-x FI_EFA_TX_MIN_CREDITS=64 \
-x NCCL_DEBUG=INFO \
-x NCCL_TREE_THRESHOLD=0 \
--hostfile my-hosts -n 8 -N 8 \
--mca btl tcp,self --mca btl_tcp_if_exclude lo,docker0 --bind-to none \
$HOME/src/bin/efa-tests/efa-cuda-10.0/all_reduce_perf -b 8 -e 1G -f 2 -g 1 -c 1 -n 100
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/efa-start-nccl-dlami.md |
3dbf50373172-0 | Install the machine learning applications on the temporary instance\. The installation procedure varies depending on the specific machine learning application\. For more information about installing software on your Linux instance, see [Managing Software on Your Linux Instance](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/managing-software.html)\.
**Note**
You might need to refer to your machine learning application’s documentation for installation instructions\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/efa-start-nccl-dlami.md |
aaff8cb16821-0 | After you have installed the required software components, you create an AMI that you can reuse to launch your EFA\-enabled instances\.
**To create an AMI from your temporary instance**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the navigation pane, choose **Instances**\.
1. Select the temporary instance that you created and choose **Actions**, **Image**, **Create Image**\.
1. In the **Create Image** window, do the following:
1. For **Image name**, enter a descriptive name for the AMI\.
1. \(Optional\) For **Image description**, enter a brief description of the AMI\.
1. Choose **Create Image** and then choose **Close**\.
1. In the navigation pane, choose **AMIs**\.
1. Locate the AMI you created in the list\. Wait for the Status to transition from `pending` to `available` before continuing to the next step\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/efa-start-nccl-dlami.md |
cf01ee275a51-0 | At this point, you no longer need the temporary instance that you launched\. You can terminate the instance to stop incurring charges for it\.
**To terminate the temporary instance**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the navigation pane, choose **Instances**\.
1. Select the temporary instance that you created and then choose **Actions**, **Instance State**, **Terminate**, **Yes, Terminate**\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/efa-start-nccl-dlami.md |
78b8b7d01bd5-0 | Launch your EFA and NCCL\-enabled instances into a cluster placement group using the EFA\-enabled AMI and the EFA\-enabled security group that you created earlier\.
**To launch your EFA and NCCL\-enabled instances into a cluster placement group**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. Choose **Launch Instance**\.
1. On the **Choose an AMI** page, choose **My AMIs**, find the AMI that you created earlier, and then choose **Select**\.
1. On the **Choose an Instance Type** page, select **p3dn\.24xlarge** and then choose **Next: Configure Instance Details**\.
1. On the **Configure Instance Details** page, do the following:
1. For **Number of instances**, enter the number of EFA and NCCL\-enabled instances that you want to launch\.
1. For **Network** and **Subnet**, select the VPC and subnet into which to launch the instances\.
1. For **Placement group**, select **Add instance to placement group**\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/efa-start-nccl-dlami.md |
78b8b7d01bd5-1 | 1. For **Placement group**, select **Add instance to placement group**\.
1. For **Placement group name**, select **Add to a new placement group**, and then enter a descriptive name for the placement group\. Then for **Placement group strategy**, select **cluster**\.
1. For **EFA**, choose **Enable**\.
1. In the **Network Interfaces** section, for device **eth0**, choose **New network interface**\. You can optionally specify a primary IPv4 address and one or more secondary IPv4 addresses\. If you are launching the instance into a subnet that has an associated IPv6 CIDR block, you can optionally specify a primary IPv6 address and one or more secondary IPv6 addresses\.
1. Choose **Next: Add Storage**\.
1. On the **Add Storage** page, specify the volumes to attach to the instances in addition to the volumes specified by the AMI \(such as the root device volume\)\. Then choose **Next: Add Tags**\.
1. On the **Add Tags** page, specify tags for the instances, such as a user\-friendly name, and then choose **Next: Configure Security Group**\.
1. On the **Configure Security Group** page, for **Assign a security group**, select **Select an existing security group**, and then select the security group that you created earlier\.
1. Choose **Review and Launch**\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/efa-start-nccl-dlami.md |
78b8b7d01bd5-2 | 1. Choose **Review and Launch**\.
1. On the **Review Instance Launch** page, review the settings, and then choose **Launch** to choose a key pair and to launch your instances\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/efa-start-nccl-dlami.md |
27473acff016-0 | To enable your applications to run across all of the instances in your cluster, you must enable passwordless SSH access from the leader node to the member nodes\. The leader node is the instance from which you run your applications\. The remaining instances in the cluster are the member nodes\.
**To enable passwordless SSH between the instances in the cluster**
1. Select one instance in the cluster as the leader node, and connect to it\.
1. Disable `strictHostKeyChecking` and enable `ForwardAgent` on the leader node\. Open `~/.ssh/config` using your preferred text editor and add the following\.
```
Host *
ForwardAgent yes
Host *
StrictHostKeyChecking no
```
1. Generate an RSA key pair\.
```
$ ssh-keygen -t rsa -N "" -f /home/ubuntu/.ssh/id_rsa
```
The key pair is created in the `$HOME/.ssh/` directory\.
1. Change the permissions of the private key on the leader node\.
```
$ chmod 600 ~/.ssh/id_rsa
```
1. Open `~/.ssh/id_rsa.pub` using your preferred text editor and copy the key\.
1. For each member node in the cluster, do the following: | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/efa-start-nccl-dlami.md |
27473acff016-1 | 1. For each member node in the cluster, do the following:
1. Connect to the instance\.
1. Open `~/.ssh/authorized_keys` using your preferred text editor and add the public key that you copied earlier\.
1. To test that the passwordless SSH is functioning as expected, connect to your leader node and run the following command\.
```
$ ssh member_node_private_ip
```
You should connect to the member node without being prompted for a key or password\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/efa-start-nccl-dlami.md |
15b58d53c97e-0 | The maximum transmission unit \(MTU\) of a network connection is the size, in bytes, of the largest permissible packet that can be passed over the connection\. The larger the MTU of a connection, the more data that can be passed in a single packet\. Ethernet packets consist of the frame, or the actual data you are sending, and the network overhead information that surrounds it\.
Ethernet frames can come in different formats, and the most common format is the standard Ethernet v2 frame format\. It supports 1500 MTU, which is the largest Ethernet packet size supported over most of the internet\. The maximum supported MTU for an instance depends on its instance type\. All Amazon EC2 instance types support 1500 MTU, and many current instance sizes support 9001 MTU, or jumbo frames\.
If your instance runs in a Wavelength Zone, the maximum MTU value is 1300\.
**Topics**
+ [Jumbo frames \(9001 MTU\)](#jumbo_frame_instances)
+ [Path MTU Discovery](#path_mtu_discovery)
+ [Check the path MTU between two hosts](#check_path_mtu)
+ [Check and set the MTU on your Linux instance](#set_mtu)
+ [Troubleshooting](#mtu-troubleshooting) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/network_mtu.md |
dad904ec2c53-0 | Jumbo frames allow more than 1500 bytes of data by increasing the payload size per packet, and thus increasing the percentage of the packet that is not packet overhead\. Fewer packets are needed to send the same amount of usable data\. However, outside of a given AWS Region \(EC2\-Classic\), a single VPC, or a VPC peering connection, you will experience a maximum path of 1500 MTU\. VPN connections and traffic sent over an internet gateway are limited to 1500 MTU\. If packets are over 1500 bytes, they are fragmented, or they are dropped if the `Don't Fragment` flag is set in the IP header\.
Jumbo frames should be used with caution for internet\-bound traffic or any traffic that leaves a VPC\. Packets are fragmented by intermediate systems, which slows down this traffic\. To use jumbo frames inside a VPC and not slow traffic that's bound for outside the VPC, you can configure the MTU size by route, or use multiple elastic network interfaces with different MTU sizes and different routes\.
For instances that are collocated inside a cluster placement group, jumbo frames help to achieve the maximum network throughput possible, and they are recommended in this case\. For more information, see [Placement groups](placement-groups.md)\.
You can use jumbo frames for traffic between your VPCs and your on\-premises networks over AWS Direct Connect\. For more information, and for how to verify Jumbo Frame capability, see [Setting Network MTU](https://docs.aws.amazon.com/directconnect/latest/UserGuide/set-jumbo-frames-vif.html) in the *AWS Direct Connect User Guide*\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/network_mtu.md |
dad904ec2c53-1 | All [current generation instances](instance-types.md#instance-type-summary-table) support jumbo frames\. The following previous generation instances support jumbo frames: C3, G2, I2, M3, and R3\.
For more information about supported MTU sizes for transit gateways, see [MTU](https://docs.aws.amazon.com/vpc/latest/tgw/transit-gateway-quotas.html#mtu-quota) in *Amazon VPC Transit Gateways*\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/network_mtu.md |
bd9ec7c09bc8-0 | Path MTU Discovery \(PMTUD\) is used to determine the maximum transmission unit \(MTU\) of a network path\. Path MTU is the maximum packet size between the originating host and the receiving host\. If a host sends a packet that's larger than the MTU of the receiving host or that's larger than the MTU of a device along the path, the receiving host or device returns the following ICMP message: `Destination Unreachable: Fragmentation Needed and Don't Fragment was Set` \(Type 3, Code 4\)\. This instructs the original host to adjust the MTU until the packet can be transmitted\.
By default, security groups do not allow any inbound ICMP traffic\. However, security groups are stateful, therefore ICMP responses to outbound requests are allowed to flow in, regardless of security group rules\. Therefore, you do not need to explicitly add an inbound ICMP rule to ensure that your instance can receive the ICMP message response\. For more information about configuring ICMP rules in a network ACL, see [Path MTU Discovery](https://docs.aws.amazon.com/vpc/latest/userguide/vpc-network-acls.html#path_mtu_discovery) in the *Amazon VPC User Guide*\.
**Important**
Path MTU Discovery does not guarantee that jumbo frames will not be dropped by some routers\. An internet gateway in your VPC will forward packets up to 1500 bytes only\. 1500 MTU packets are recommended for internet traffic\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/network_mtu.md |
a09606a73216-0 | You can check the path MTU between two hosts using the tracepath command, which is part of the `iputils` package that is available by default on many Linux distributions, including Amazon Linux\.
**To check path MTU using tracepath**
Use the following command to check the path MTU between your EC2 instance and another host\. You can use a DNS name or an IP address as the destination\. If the destination is another EC2 instance, verify that the security group allows inbound UDP traffic\. This example checks the path MTU between an EC2 instance and `amazon.com`\.
```
[ec2-user ~]$ tracepath amazon.com
1?: [LOCALHOST] pmtu 9001
1: ip-172-31-16-1.us-west-1.compute.internal (172.31.16.1) 0.187ms pmtu 1500
1: no reply
2: no reply
3: no reply
4: 100.64.16.241 (100.64.16.241) 0.574ms
5: 72.21.222.221 (72.21.222.221) 84.447ms asymm 21
6: 205.251.229.97 (205.251.229.97) 79.970ms asymm 19
7: 72.21.222.194 (72.21.222.194) 96.546ms asymm 16
8: 72.21.222.239 (72.21.222.239) 79.244ms asymm 15 | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/network_mtu.md |
a09606a73216-1 | 8: 72.21.222.239 (72.21.222.239) 79.244ms asymm 15
9: 205.251.225.73 (205.251.225.73) 91.867ms asymm 16
...
31: no reply
Too many hops: pmtu 1500
Resume: pmtu 1500
```
In this example, the path MTU is 1500\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/network_mtu.md |
12e23281cfb6-0 | Some instances are configured to use jumbo frames, and others are configured to use standard frame sizes\. You may want to use jumbo frames for network traffic within your VPC or you may want to use standard frames for internet traffic\. Whatever your use case, we recommend verifying that your instance will behave the way you expect it to\. You can use the procedures in this section to check your network interface's MTU setting and modify it if needed\.
**To check the MTU setting on a Linux instance**
You can check the current MTU value using the following ip command\. Note that in the example output, *mtu 9001* indicates that this instance uses jumbo frames\.
```
[ec2-user ~]$ ip link show eth0
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9001 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
link/ether 02:90:c0:b7:9e:d1 brd ff:ff:ff:ff:ff:ff
```
**To set the MTU value on a Linux instance**
1. You can set the MTU value using the ip command\. The following command sets the desired MTU value to 1500, but you could use 9001 instead\.
```
[ec2-user ~]$ sudo ip link set dev eth0 mtu 1500
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/network_mtu.md |
12e23281cfb6-1 | ```
[ec2-user ~]$ sudo ip link set dev eth0 mtu 1500
```
1. \(Optional\) To persist your network MTU setting after a reboot, modify the following configuration files, based on your operating system type\.
+ For Amazon Linux 2, add the following line to the `/etc/sysconfig/network-scripts/ifcfg-eth0` file:
```
MTU=1500
```
Add the following line to the `/etc/dhcp/dhclient.conf` file:
```
request subnet-mask, broadcast-address, time-offset, routers, domain-name, domain-search, domain-name-servers, host-name, nis-domain, nis-servers, ntp-servers;
```
+ For Amazon Linux, add the following lines to your `/etc/dhcp/dhclient-eth0.conf` file\.
```
interface "eth0" {
supersede interface-mtu 1500;
}
```
+ For other Linux distributions, consult their specific documentation\.
1. \(Optional\) Reboot your instance and verify that the MTU setting is correct\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/network_mtu.md |
9866ebd9aa15-0 | If you experience connectivity issues between your EC2 instance and an Amazon Redshift cluster when using jumbo frames, see [Queries Appear to Hang](https://docs.aws.amazon.com/redshift/latest/mgmt/connecting-drop-issues.html) in the *Amazon Redshift Cluster Management Guide* | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/network_mtu.md |
5cf41f9ee68e-0 | After you [increase the size of an EBS volume](requesting-ebs-volume-modifications.md), you must use file system–specific commands to extend the file system to the larger size\. You can resize the file system as soon as the volume enters the `optimizing` state\.
**Important**
Before extending a file system that contains valuable data, it is best practice to create a snapshot of the volume, in case you need to roll back your changes\. For more information, see [Creating Amazon EBS snapshots](ebs-creating-snapshot.md)\. If your Linux AMI uses the MBR partitioning scheme, you are limited to a boot volume size of up to 2 TiB\. For more information, see [Requirements for Linux volumes](modify-volume-requirements.md#linux-volumes) and [Constraints on the size and configuration of an EBS volume](volume_constraints.md)\.
The process for extending a file system on Linux is as follows:
1. Your EBS volume might have a partition that contains the file system and data\. Increasing the size of a volume does not increase the size of the partition\. Before you extend the file system on a resized volume, check whether the volume has a partition that must be extended to the new size of the volume\.
1. Use a file system\-specific command to resize each file system to the new volume capacity\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/recognize-expanded-volume-linux.md |
5cf41f9ee68e-1 | 1. Use a file system\-specific command to resize each file system to the new volume capacity\.
For information about extending a Windows file system, see [Extending a Windows File System after Resizing a Volume](https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/recognize-expanded-volume-windows.html) in the *Amazon EC2 User Guide for Windows Instances*\.
The following examples walk you through the process of extending a Linux file system\. For file systems and partitioning schemes other than the ones shown here, refer to the documentation for those file systems and partitioning schemes for instructions\.
**Topics**
+ [Example: Extending the file system of NVMe EBS volumes](#extend-file-system-nvme)
+ [Example: Extending the file system of EBS volumes](#extend-file-system) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/recognize-expanded-volume-linux.md |
8b8060d89e9a-0 | For this example, suppose that you have an instance built on the [Nitro System](instance-types.md#ec2-nitro-instances), such as an M5 instance\. You resized the boot volume from 8 GB to 16 GB and an additional volume from 8 GB to 30 GB\. Use the following procedure to extend the file system of the resized volumes\.
**To extend the file system of NVMe EBS volumes**
1. [Connect to your instance](AccessingInstances.md)\.
1. To verify the file system for each volume, use the df \-hT command\.
```
[ec2-user ~]$ df -hT
```
The following is example output for an instance that has a boot volume with an XFS file system and an additional volume with an XFS file system\. The naming convention `/dev/nvme[0-26]n1` indicates that the volumes are exposed as NVMe block devices\.
```
[ec2-user ~]$ df -hT
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p1 xfs 8.0G 1.6G 6.5G 20% /
/dev/nvme1n1 xfs 8.0G 33M 8.0G 1% /data
...
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/recognize-expanded-volume-linux.md |
8b8060d89e9a-1 | ...
```
1. To check whether the volume has a partition that must be extended, use the lsblk command to display information about the NVMe block devices attached to your instance\.
```
[ec2-user ~]$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
nvme1n1 259:0 0 30G 0 disk /data
nvme0n1 259:1 0 16G 0 disk
└─nvme0n1p1 259:2 0 8G 0 part /
└─nvme0n1p128 259:3 0 1M 0 part
```
This example output shows the following:
+ The root volume, `/dev/nvme0n1`, has a partition, `/dev/nvme0n1p1`\. While the size of the root volume reflects the new size, 16 GB, the size of the partition reflects the original size, 8 GB, and must be extended before you can extend the file system\.
+ The volume `/dev/nvme1n1` has no partitions\. The size of the volume reflects the new size, 30 GB\.
1. To extend the partition on the root volume, use the following growpart command\. Notice that there is a space between the device name and the partition number\.
```
[ec2-user ~]$ sudo growpart /dev/nvme0n1 1
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/recognize-expanded-volume-linux.md |
8b8060d89e9a-2 | ```
[ec2-user ~]$ sudo growpart /dev/nvme0n1 1
```
1. \(Optional\) Use the lsblk command again to verify that the partition reflects the increased volume size\.
```
[ec2-user ~]$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
nvme1n1 259:0 0 30G 0 disk /data
nvme0n1 259:1 0 16G 0 disk
└─nvme0n1p1 259:2 0 16G 0 part /
└─nvme0n1p128 259:3 0 1M 0 part
```
1. Use the df \-h command to verify the size of the file system for each volume\. In this example output, each file system reflects the original volume size, 8 GB\.
```
[ec2-user ~]$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/nvme0n1p1 8.0G 1.6G 6.5G 20% /
/dev/nvme1n1 8.0G 33M 8.0G 1% /data
...
```
1. Use the xfs\_growfs command to extend the XFS file system on each volume\. In this example, `/` and `/data` are the volume mount points shown in the output for df \-h\.
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/recognize-expanded-volume-linux.md |
8b8060d89e9a-3 | ```
[ec2-user ~]$ sudo xfs_growfs -d /
[ec2-user ~]$ sudo xfs_growfs -d /data
```
If the XFS tools are not already installed, you can install them as follows\.
```
[ec2-user ~]$ sudo yum install xfsprogs
```
1. \(Optional\) Use the df \-h command again to verify that each file system reflects the increased volume size\.
```
[ec2-user ~]$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/nvme0n1p1 16G 1.6G 15G 10% /
/dev/nvme1n1 30G 33M 30G 1% /data
...
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/recognize-expanded-volume-linux.md |
ca143bdf05c3-0 | For this example, suppose that you have resized the boot volume of an instance, such as a T2 instance, from 8 GB to 16 GB and an additional volume from 8 GB to 30 GB\. Use the following procedure to extend the file system of the resized volumes\.
**To extend the file system of EBS volumes**
1. [Connect to your instance](AccessingInstances.md)\.
1. To verify the file system in use for each volume, use the df \-hT command\.
```
[ec2-user ~]$ df -hT
```
The following is example output for an instance that has a boot volume with an ext4 file system and an additional volume with an XFS file system\.
```
[ec2-user ~]$ df -hT
Filesystem Type Size Used Avail Use% Mounted on
/dev/xvda1 ext4 8.0G 1.9G 6.2G 24% /
/dev/xvdf1 xfs 8.0G 45M 8.0G 1% /data
...
```
1. To check whether the volume has a partition that must be extended, use the lsblk command to display information about the block devices attached to your instance\.
```
[ec2-user ~]$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
xvda 202:0 0 16G 0 disk | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/recognize-expanded-volume-linux.md |
ca143bdf05c3-1 | NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
xvda 202:0 0 16G 0 disk
└─xvda1 202:1 0 8G 0 part /
xvdf 202:80 0 30G 0 disk
└─xvdf1 202:81 0 8G 0 part /data
```
This example output shows the following:
+ The root volume, `/dev/xvda`, has a partition, `/dev/xvda1`\. While the size of the volume is 16 GB, the size of the partition is still 8 GB and must be extended\.
+ The volume `/dev/xvdf` has a partition, `/dev/xvdf1`\. While the size of the volume is 30G, the size of the partition is still 8 GB and must be extended\.
1. To extend the partition on each volume, use the following growpart commands\. Notice that there is a space between the device name and the partition number\.
```
[ec2-user ~]$ sudo growpart /dev/xvda 1
[ec2-user ~]$ sudo growpart /dev/xvdf 1
```
1. \(Optional\) Use the lsblk command again to verify that the partitions reflect the increased volume size\.
```
[ec2-user ~]$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
xvda 202:0 0 16G 0 disk
└─xvda1 202:1 0 16G 0 part / | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/recognize-expanded-volume-linux.md |
ca143bdf05c3-2 | NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
xvda 202:0 0 16G 0 disk
└─xvda1 202:1 0 16G 0 part /
xvdf 202:80 0 30G 0 disk
└─xvdf1 202:81 0 30G 0 part /data
```
1. Use the df \-h command to verify the size of the file system for each volume\. In this example output, both `/dev/xvda1` and `/dev/xvdf` reflect the original size of the volumes, 8 GB\.
```
[ec2-user ~]$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/xvda1 8.0G 1.9G 6.2G 24% /
/dev/xvdf1 8.0G 45M 8.0G 1% /data
...
```
1. Use the resize2fs command to extend the file system on each volume\.
```
[ec2-user ~]$ sudo resize2fs /dev/xvda1
[ec2-user ~]$ sudo resize2fs /dev/xvdf1
```
1. \(Optional\) Use the df \-h command again to verify that each file system reflects the increased volume size\.
```
[ec2-user ~]$ df -h
Filesystem Size Used Avail Use% Mounted on | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/recognize-expanded-volume-linux.md |
ca143bdf05c3-3 | ```
[ec2-user ~]$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/xvda1 16G 1.9G 14G 12% /
/dev/xvdf1 30G 45M 30G 1% /data
...
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/recognize-expanded-volume-linux.md |
3a09938a5d95-0 | The following topics explain the structure of an IAM policy\.
**Topics**
+ [Policy syntax](#policy-syntax)
+ [Actions for Amazon EC2](#UsingWithEC2_Actions)
+ [Supported resource\-level permissions for Amazon EC2 API actions](#ec2-supported-iam-actions-resources)
+ [Amazon Resource Names \(ARNs\) for Amazon EC2](#EC2_ARN_Format)
+ [Condition keys for Amazon EC2](#amazon-ec2-keys)
+ [Checking that users have the required permissions](#check-required-permissions) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/iam-policy-structure.md |
Subsets and Splits