Fix broken links to all Amazon builders (#10487)

This commit is contained in:
Pero P 2021-01-15 01:58:59 -08:00 committed by GitHub
parent f5cbb56c14
commit 5a61823082
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 6 deletions

View File

@ -12,29 +12,29 @@ Packer is able to create Amazon AMIs. To achieve this, Packer comes with
multiple builders depending on the strategy you want to use to build the AMI. multiple builders depending on the strategy you want to use to build the AMI.
Packer supports the following builders at the moment: Packer supports the following builders at the moment:
- [amazon-ebs](/docs/builders/amazon-ebs) - Create EBS-backed AMIs by - [amazon-ebs](/docs/builders/amazon/ebs) - Create EBS-backed AMIs by
launching a source AMI and re-packaging it into a new AMI after launching a source AMI and re-packaging it into a new AMI after
provisioning. If in doubt, use this builder, which is the easiest to get provisioning. If in doubt, use this builder, which is the easiest to get
started with. started with.
- [amazon-instance](/docs/builders/amazon-instance) - Create - [amazon-instance](/docs/builders/amazon/instance) - Create
instance-store AMIs by launching and provisioning a source instance, then instance-store AMIs by launching and provisioning a source instance, then
rebundling it and uploading it to S3. rebundling it and uploading it to S3.
- [amazon-chroot](/docs/builders/amazon-chroot) - Create EBS-backed AMIs - [amazon-chroot](/docs/builders/amazon/chroot) - Create EBS-backed AMIs
from an existing EC2 instance by mounting the root device and using a from an existing EC2 instance by mounting the root device and using a
[Chroot](https://en.wikipedia.org/wiki/Chroot) environment to provision [Chroot](https://en.wikipedia.org/wiki/Chroot) environment to provision
that device. This is an **advanced builder and should not be used by that device. This is an **advanced builder and should not be used by
newcomers**. However, it is also the fastest way to build an EBS-backed AMI newcomers**. However, it is also the fastest way to build an EBS-backed AMI
since no new EC2 instance needs to be launched. since no new EC2 instance needs to be launched.
- [amazon-ebssurrogate](/docs/builders/amazon-ebssurrogate) - Create EBS - [amazon-ebssurrogate](/docs/builders/amazon/ebssurrogate) - Create EBS
-backed AMIs from scratch. Works similarly to the `chroot` builder but does -backed AMIs from scratch. Works similarly to the `chroot` builder but does
not require running in AWS. This is an **advanced builder and should not be not require running in AWS. This is an **advanced builder and should not be
used by newcomers**. used by newcomers**.
-> **Don't know which builder to use?** If in doubt, use the [amazon-ebs -> **Don't know which builder to use?** If in doubt, use the [amazon-ebs
builder](/docs/builders/amazon-ebs). It is much easier to use and Amazon builder](/docs/builders/amazon/ebs). It is much easier to use and Amazon
generally recommends EBS-backed images nowadays. generally recommends EBS-backed images nowadays.
# Amazon EBS Volume Builder # Amazon EBS Volume Builder
@ -42,7 +42,7 @@ generally recommends EBS-backed images nowadays.
Packer is able to create Amazon EBS Volumes which are preinitialized with a Packer is able to create Amazon EBS Volumes which are preinitialized with a
filesystem and data. filesystem and data.
- [amazon-ebsvolume](/docs/builders/amazon-ebsvolume) - Create EBS - [amazon-ebsvolume](/docs/builders/amazon/ebsvolume) - Create EBS
volumes by launching a source AMI with block devices mapped. Provision the volumes by launching a source AMI with block devices mapped. Provision the
instance, then destroy it, retaining the EBS volumes. instance, then destroy it, retaining the EBS volumes.