Use SSL for resources

10 years ago · c0b46b2fb8
parent 091760f79a
commit c0b46b2fb8
35 changed files with 79 additions and 79 deletions
--- a/website/source/assets/images/arrow-left.png
+++ b/website/source/assets/images/arrow-left.png
--- a/website/source/assets/images/arrow-right.png
+++ b/website/source/assets/images/arrow-right.png
--- a/website/source/community/index.html.markdown
+++ b/website/source/community/index.html.markdown
@ -14,7 +14,7 @@ dedicated users willing to help through various mediums.
 **IRC:** `#packer-tool` on Freenode.

 **Mailing List:** [Packer Google
-Group](http://groups.google.com/group/packer-tool)
+Group](https://groups.google.com/group/packer-tool)

 **Bug Tracker:** [Issue tracker on
 GitHub](https://github.com/mitchellh/packer/issues). Please only use this for
@ -31,14 +31,14 @@ list as contributors come and go.

 <div class="person">

-    <img class="pull-left" src="http://www.gravatar.com/avatar/54079122b67de9677c1f93933ce8b63a.png?s=125">
+    <img class="pull-left" src="https://www.gravatar.com/avatar/54079122b67de9677c1f93933ce8b63a.png?s=125">
    <div class="bio">
      <h3>Mitchell Hashimoto (<a href="https://github.com/mitchellh">@mitchellh</a>)</h3>
      <p>
      Mitchell Hashimoto is the creator of Packer. He developed the
      core of Packer as well as the Amazon, VirtualBox, and VMware
      builders. In addition to Packer, Mitchell is the creator of
-      <a href="http://www.vagrantup.com">Vagrant</a>. He is self
+      <a href="https://www.vagrantup.com">Vagrant</a>. He is self
      described as "automation obsessed."
      </p>
    </div>
@ -47,7 +47,7 @@ list as contributors come and go.

 <div class="person">

-    <img class="pull-left" src="http://www.gravatar.com/avatar/2acc31dd6370a54b18f6755cd0710ce6.png?s=125">
+    <img class="pull-left" src="https://www.gravatar.com/avatar/2acc31dd6370a54b18f6755cd0710ce6.png?s=125">
    <div class="bio">
      <h3>Jack Pearkes (<a href="https://github.com/pearkes">@pearkes</a>)</h3>
      <p>
@ -60,7 +60,7 @@ list as contributors come and go.

 <div class="person">

-    <img class="pull-left" src="http://www.gravatar.com/avatar/2f7fc9cb7558e3ea48f5a86fa90a78da.png?s=125">
+    <img class="pull-left" src="https://www.gravatar.com/avatar/2f7fc9cb7558e3ea48f5a86fa90a78da.png?s=125">
    <div class="bio">
      <h3>Mark Peek (<a href="https://github.com/markpeek">@markpeek</a>)</h3>
      <p>
@ -75,7 +75,7 @@ list as contributors come and go.

 <div class="person">

-    <img class="pull-left" src="http://www.gravatar.com/avatar/1fca64df3d7db1e2f258a8956d2b0aff.png?s=125">
+    <img class="pull-left" src="https://www.gravatar.com/avatar/1fca64df3d7db1e2f258a8956d2b0aff.png?s=125">
    <div class="bio">
      <h3>Ross Smith II (<a href="https://github.com/rasa" target="_blank">@rasa</a>)</h3>
      <p>
@ -90,7 +90,7 @@ open source enthusiast, published author, and freelance consultant.

 <div class="person">

-    <img class="pull-left" src="http://www.gravatar.com/avatar/c9f6bf7b5b865012be5eded656ebed7d.png?s=125">
+    <img class="pull-left" src="https://www.gravatar.com/avatar/c9f6bf7b5b865012be5eded656ebed7d.png?s=125">
    <div class="bio">
      <h3>Rickard von Essen<br/>(<a href="https://github.com/rickard-von-essen" target="_blank">@rickard-von-essen</a>)</h3>
      <p>
--- a/website/source/docs/builders/amazon-chroot.html.markdown
+++ b/website/source/docs/builders/amazon-chroot.html.markdown
@ -16,7 +16,7 @@ The `amazon-chroot` Packer builder is able to create Amazon AMIs backed by an
 EBS volume as the root device. For more information on the difference between
 instance storage and EBS-backed instances, see the ["storage for the root
 device" section in the EC2
-documentation](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ComponentsAMIs.html#storage-for-the-root-device).
+documentation](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ComponentsAMIs.html#storage-for-the-root-device).

 The difference between this builder and the `amazon-ebs` builder is that this
 builder is able to build an EBS-backed AMI without launching a new EC2 instance.
@ -34,7 +34,7 @@ account, it is up to you to use, delete, etc. the AMI.

 This builder works by creating a new EBS volume from an existing source AMI and
 attaching it into an already-running EC2 instance. Once attached, a
-[chroot](http://en.wikipedia.org/wiki/Chroot) is used to provision the system
+[chroot](https://en.wikipedia.org/wiki/Chroot) is used to provision the system
 within that volume. After provisioning, the volume is detached, snapshotted, and
 an AMI is made.

--- a/website/source/docs/builders/amazon-ebs.html.markdown
+++ b/website/source/docs/builders/amazon-ebs.html.markdown
@ -13,10 +13,10 @@ page_title: 'Amazon AMI Builder (EBS backed)'
 Type: `amazon-ebs`

 The `amazon-ebs` Packer builder is able to create Amazon AMIs backed by EBS
-volumes for use in [EC2](http://aws.amazon.com/ec2/). For more information on
+volumes for use in [EC2](https://aws.amazon.com/ec2/). For more information on
 the difference between EBS-backed instances and instance-store backed instances,
 see the ["storage for the root device" section in the EC2
-documentation](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ComponentsAMIs.html#storage-for-the-root-device).
+documentation](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ComponentsAMIs.html#storage-for-the-root-device).

 This builder builds an AMI by launching an EC2 instance from a source AMI,
 provisioning that running machine, and then creating an AMI from that machine.
@ -72,7 +72,7 @@ builder.
         example, "/dev/sdh" or "xvdh"). Required when specifying `volume_size`.
    -   `virtual_name` (string) - The virtual device name. See the documentation on
        [Block Device
-        Mapping](http://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_BlockDeviceMapping.html)
+        Mapping](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_BlockDeviceMapping.html)
        for more information
    -   `snapshot_id` (string) - The ID of the snapshot
    -   `volume_type` (string) - The volume type. gp2 for General Purpose (SSD)
@ -87,7 +87,7 @@ builder.
        block device mapping of the AMI
    -   `iops` (integer) - The number of I/O operations per second (IOPS) that the
        volume supports. See the documentation on
-        [IOPs](http://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_EbsBlockDevice.html)
+        [IOPs](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_EbsBlockDevice.html)
        for more information
 -   `ami_description` (string) - The description to set for the
    resulting AMI(s). By default this description is empty.
@ -117,7 +117,7 @@ builder.
    instance in. Leave this empty to allow Amazon to auto-assign.

 -   `ebs_optimized` (boolean) - Mark instance as [EBS
-    Optimized](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSOptimized.html).
+    Optimized](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSOptimized.html).
    Default `false`.

 -   `enhanced_networking` (boolean) - Enable enhanced
@ -128,7 +128,7 @@ builder.
    AMI if one with the same name already exists. Default `false`.

 -   `iam_instance_profile` (string) - The name of an [IAM instance
-    profile](http://docs.aws.amazon.com/IAM/latest/UserGuide/instance-profiles.html)
+    profile](https://docs.aws.amazon.com/IAM/latest/UserGuide/instance-profiles.html)
    to launch the EC2 instance with.

 -   `launch_block_device_mappings` (array of block device mappings) - Add the
--- a/website/source/docs/builders/amazon-instance.html.markdown
+++ b/website/source/docs/builders/amazon-instance.html.markdown
@ -16,7 +16,7 @@ The `amazon-instance` Packer builder is able to create Amazon AMIs backed by
 instance storage as the root device. For more information on the difference
 between instance storage and EBS-backed instances, see the ["storage for the
 root device" section in the EC2
-documentation](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ComponentsAMIs.html#storage-for-the-root-device).
+documentation](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ComponentsAMIs.html#storage-for-the-root-device).

 This builder builds an AMI by launching an EC2 instance from an existing
 instance-storage backed AMI, provisioning that running machine, and then
@ -29,7 +29,7 @@ The builder does *not* manage AMIs. Once it creates an AMI and stores it in your
 account, it is up to you to use, delete, etc. the AMI.

 -&gt; **Note** This builder requires that the [Amazon EC2 AMI
-Tools](http://aws.amazon.com/developertools/368) are installed onto the machine.
+Tools](https://aws.amazon.com/developertools/368) are installed onto the machine.
 This can be done within a provisioner, but must be done before the builder
 finishes running.

@ -93,7 +93,7 @@ builder.
    example, "/dev/sdh" or "xvdh"). Required when specifying `volume_size`.
 -   `virtual_name` (string) - The virtual device name. See the documentation on
    [Block Device
-    Mapping](http://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_BlockDeviceMapping.html)
+    Mapping](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_BlockDeviceMapping.html)
    for more information
 -   `snapshot_id` (string) - The ID of the snapshot
 -   `volume_type` (string) - The volume type. gp2 for General Purpose (SSD)
@ -108,7 +108,7 @@ builder.
    block device mapping of the AMI
 -   `iops` (integer) - The number of I/O operations per second (IOPS) that the
    volume supports. See the documentation on
-    [IOPs](http://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_EbsBlockDevice.html)
+    [IOPs](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_EbsBlockDevice.html)
    for more information
 -   `ami_description` (string) - The description to set for the
    resulting AMI(s). By default this description is empty.
@ -158,7 +158,7 @@ builder.
    the "custom bundle commands" section below for more information.

 -   `ebs_optimized` (boolean) - Mark instance as [EBS
-    Optimized](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSOptimized.html).
+    Optimized](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSOptimized.html).
    Default `false`.

 -   `enhanced_networking` (boolean) - Enable enhanced
@ -169,7 +169,7 @@ builder.
    AMI if one with the same name already exists. Default `false`.

 -   `iam_instance_profile` (string) - The name of an [IAM instance
-    profile](http://docs.aws.amazon.com/IAM/latest/UserGuide/instance-profiles.html)
+    profile](https://docs.aws.amazon.com/IAM/latest/UserGuide/instance-profiles.html)
    to launch the EC2 instance with.

 -   `launch_block_device_mappings` (array of block device mappings) - Add the
--- a/website/source/docs/builders/amazon.html.markdown
+++ b/website/source/docs/builders/amazon.html.markdown
@ -23,7 +23,7 @@ Packer supports the following builders at the moment:

 -   [amazon-chroot](/docs/builders/amazon-chroot.html) - Create EBS-backed AMIs
    from an existing EC2 instance by mounting the root device and using a
-    [Chroot](http://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
    newcomers**. However, it is also the fastest way to build an EBS-backed AMI
    since no new EC2 instance needs to be launched.
@ -63,7 +63,7 @@ following steps:
    -   First `AWS_SECRET_ACCESS_KEY`, then `AWS_SECRET_KEY`

 2.  Look for [local AWS configuration
-    files](http://docs.aws.amazon.com/cli/latest/userguide/cli-chap-getting-started.html#cli-config-files)
+    files](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-getting-started.html#cli-config-files)
    -   First `~/.aws/credentials`
    -   Next based on `AWS_PROFILE`

@ -80,7 +80,7 @@ packer build on your workstation, in Atlas, or on another build server.
 ## Using an IAM Instance Profile

 If AWS keys are not specified in the template, a
-[credentials](http://docs.aws.amazon.com/cli/latest/userguide/cli-chap-getting-started.html#cli-config-files)
+[credentials](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-getting-started.html#cli-config-files)
 file or through environment variables Packer will use credentials provided by
 the instance's IAM profile, if it has one.

@ -132,7 +132,7 @@ roles, you may encounter an error like this one:
    ==> amazon-ebs: Error launching source instance: You are not authorized to perform this operation.

 You can read more about why this happens on the [Amazon Security
-Blog](http://blogs.aws.amazon.com/security/post/Tx3M0IFB5XBOCQX/Granting-Permission-to-Launch-EC2-Instances-with-IAM-Roles-PassRole-Permission).
+Blog](https://blogs.aws.amazon.com/security/post/Tx3M0IFB5XBOCQX/Granting-Permission-to-Launch-EC2-Instances-with-IAM-Roles-PassRole-Permission).
 The example policy below may help packer work with IAM roles. Note that this
 example provides more than the minimal set of permissions needed for packer to
 work, but specifics will depend on your use-case.
--- a/website/source/docs/builders/digitalocean.html.markdown
+++ b/website/source/docs/builders/digitalocean.html.markdown
@ -14,7 +14,7 @@ page_title: DigitalOcean Builder
 Type: `digitalocean`

 The `digitalocean` Packer builder is able to create new images for use with
-[DigitalOcean](http://www.digitalocean.com). The builder takes a source image,
+[DigitalOcean](https://www.digitalocean.com). The builder takes a source image,
 runs any provisioning necessary on the image after launching it, then snapshots
 it into a reusable image. This reusable image can then be used as the foundation
 of new servers that are launched within DigitalOcean.
--- a/website/source/docs/builders/docker.html.markdown
+++ b/website/source/docs/builders/docker.html.markdown
@ -11,7 +11,7 @@ page_title: Docker Builder

 Type: `docker`

-The `docker` Packer builder builds [Docker](http://www.docker.io) images using
+The `docker` Packer builder builds [Docker](https://www.docker.io) images using
 Docker. The builder starts a Docker container, runs provisioners within this
 container, then exports the container for reuse or commits the image.

@ -26,7 +26,7 @@ the section on [Dockerfiles](#toc_8).
 The Docker builder must run on a machine that has Docker installed. Therefore
 the builder only works on machines that support Docker (modern Linux machines).
 If you want to use Packer to build Docker containers on another platform, use
-[Vagrant](http://www.vagrantup.com) to start a Linux environment, then run
+[Vagrant](https://www.vagrantup.com) to start a Linux environment, then run
 Packer within that environment.

 ## Basic Example: Export
@ -246,7 +246,7 @@ shown below:
 ```

 See the
-[AWS documentation](http://docs.aws.amazon.com/AmazonECR/latest/userguide/Registries.html)
+[AWS documentation](https://docs.aws.amazon.com/AmazonECR/latest/userguide/Registries.html)
 for steps to obtain Amazon ECR registry credentials.


--- a/website/source/docs/builders/parallels-iso.html.markdown
+++ b/website/source/docs/builders/parallels-iso.html.markdown
@ -11,7 +11,7 @@ page_title: 'Parallels Builder (from an ISO)'
 Type: `parallels-iso`

 The Parallels Packer builder is able to create [Parallels Desktop for
-Mac](http://www.parallels.com/products/desktop/) virtual machines and export
+Mac](https://www.parallels.com/products/desktop/) virtual machines and export
 them in the PVM format, starting from an ISO image.

 The builder builds a virtual machine by creating a new virtual machine from
--- a/website/source/docs/builders/parallels-pvm.html.markdown
+++ b/website/source/docs/builders/parallels-pvm.html.markdown
@ -12,7 +12,7 @@ page_title: 'Parallels Builder (from a PVM)'
 Type: `parallels-pvm`

 This Parallels builder is able to create [Parallels Desktop for
-Mac](http://www.parallels.com/products/desktop/) virtual machines and export
+Mac](https://www.parallels.com/products/desktop/) virtual machines and export
 them in the PVM format, starting from an existing PVM (exported virtual machine
 image).

--- a/website/source/docs/builders/parallels.html.markdown
+++ b/website/source/docs/builders/parallels.html.markdown
@ -9,7 +9,7 @@ page_title: Parallels Builder
 # Parallels Builder

 The Parallels Packer builder is able to create [Parallels Desktop for
-Mac](http://www.parallels.com/products/desktop/) virtual machines and export
+Mac](https://www.parallels.com/products/desktop/) virtual machines and export
 them in the PVM format.

 Packer actually comes with multiple builders able to create Parallels machines,
@ -30,8 +30,8 @@ the following Parallels builders:
 ## Requirements

 In addition to [Parallels Desktop for
-Mac](http://www.parallels.com/products/desktop/) this requires the [Parallels
-Virtualization SDK](http://www.parallels.com/downloads/desktop/).
+Mac](https://www.parallels.com/products/desktop/) this requires the [Parallels
+Virtualization SDK](https://www.parallels.com/downloads/desktop/).

 The SDK can be installed by downloading and following the instructions in the
 dmg.
--- a/website/source/docs/builders/virtualbox-iso.html.markdown
+++ b/website/source/docs/builders/virtualbox-iso.html.markdown
@ -322,7 +322,7 @@ directory of the SSH user.

 In order to perform extra customization of the virtual machine, a template can
 define extra calls to `VBoxManage` to perform.
-[VBoxManage](http://www.virtualbox.org/manual/ch08.html) is the command-line
+[VBoxManage](https://www.virtualbox.org/manual/ch08.html) is the command-line
 interface to VirtualBox where you can completely control VirtualBox. It can be
 used to do things such as set RAM, CPUs, etc.

--- a/website/source/docs/builders/virtualbox-ovf.html.markdown
+++ b/website/source/docs/builders/virtualbox-ovf.html.markdown
@ -226,7 +226,7 @@ directory of the SSH user.

 In order to perform extra customization of the virtual machine, a template can
 define extra calls to `VBoxManage` to perform.
-[VBoxManage](http://www.virtualbox.org/manual/ch08.html) is the command-line
+[VBoxManage](https://www.virtualbox.org/manual/ch08.html) is the command-line
 interface to VirtualBox where you can completely control VirtualBox. It can be
 used to do things such as set RAM, CPUs, etc.

--- a/website/source/docs/builders/virtualbox.html.markdown
+++ b/website/source/docs/builders/virtualbox.html.markdown
@ -9,7 +9,7 @@ page_title: VirtualBox Builder
 # VirtualBox Builder

 The VirtualBox Packer builder is able to create
-[VirtualBox](http://www.virtualbox.org) virtual machines and export them in the
+[VirtualBox](https://www.virtualbox.org) virtual machines and export them in the
 OVA or OVF format.

 Packer actually comes with multiple builders able to create VirtualBox machines,
--- a/website/source/docs/builders/vmware-iso.html.markdown
+++ b/website/source/docs/builders/vmware-iso.html.markdown
@ -15,12 +15,12 @@ Type: `vmware-iso`

 This VMware Packer builder is able to create VMware virtual machines from an ISO
 file as a source. It currently supports building virtual machines on hosts
-running [VMware Fusion](http://www.vmware.com/products/fusion/overview.html) for
+running [VMware Fusion](https://www.vmware.com/products/fusion/overview.html) for
 OS X, [VMware
-Workstation](http://www.vmware.com/products/workstation/overview.html) for Linux
-and Windows, and [VMware Player](http://www.vmware.com/products/player/) on
+Workstation](https://www.vmware.com/products/workstation/overview.html) for Linux
+and Windows, and [VMware Player](https://www.vmware.com/products/player/) on
 Linux. It can also build machines directly on [VMware vSphere
-Hypervisor](http://www.vmware.com/products/vsphere-hypervisor/) using SSH as
+Hypervisor](https://www.vmware.com/products/vsphere-hypervisor/) using SSH as
 opposed to the vSphere API.

 The builder builds a virtual machine by creating a new virtual machine from
@ -105,7 +105,7 @@ builder.
    default is "1", which corresponds to a growable virtual disk split in
    2GB files. This option is for advanced usage, modify only if you know what
    you're doing. For more information, please consult the [Virtual Disk Manager
-    User's Guide](http://www.vmware.com/pdf/VirtualDiskManager.pdf) for desktop
+    User's Guide](https://www.vmware.com/pdf/VirtualDiskManager.pdf) for desktop
    VMware clients. For ESXi, refer to the proper ESXi documentation.

 -   `floppy_files` (array of strings) - A list of files to place onto a floppy
--- a/website/source/docs/builders/vmware-vmx.html.markdown
+++ b/website/source/docs/builders/vmware-vmx.html.markdown
@ -15,10 +15,10 @@ Type: `vmware-vmx`
 This VMware Packer builder is able to create VMware virtual machines from an
 existing VMware virtual machine (a VMX file). It currently supports building
 virtual machines on hosts running [VMware Fusion
-Professional](http://www.vmware.com/products/fusion-professional/) for OS X,
-[VMware Workstation](http://www.vmware.com/products/workstation/overview.html)
+Professional](https://www.vmware.com/products/fusion-professional/) for OS X,
+[VMware Workstation](https://www.vmware.com/products/workstation/overview.html)
 for Linux and Windows, and [VMware
-Player](http://www.vmware.com/products/player/) on Linux.
+Player](https://www.vmware.com/products/player/) on Linux.

 The builder builds a virtual machine by cloning the VMX file using the clone
 capabilities introduced in VMware Fusion Professional 6, Workstation 10, and
--- a/website/source/docs/command-line/push.html.markdown
+++ b/website/source/docs/command-line/push.html.markdown
@ -81,7 +81,7 @@ download it during the packer run.

 If you want to build a private `.iso` file you can upload the `.iso` to a secure
 file hosting service like [Amazon
-S3](http://docs.aws.amazon.com/AmazonS3/latest/dev/ShareObjectPreSignedURL.html),
+S3](https://docs.aws.amazon.com/AmazonS3/latest/dev/ShareObjectPreSignedURL.html),
 [Google Cloud
 Storage](https://cloud.google.com/storage/docs/gsutil/commands/signurl), or
 [Azure File
--- a/website/source/docs/extend/builder.html.markdown
+++ b/website/source/docs/extend/builder.html.markdown
@ -157,7 +157,7 @@ it would be convenient to cache the file. This sort of caching is a core part of
 Packer that is exposed to builders.

 The cache interface is `packer.Cache`. It behaves much like a Go
-[RWMutex](http://golang.org/pkg/sync/#RWMutex). The builder requests a "lock" on
+[RWMutex](https://golang.org/pkg/sync/#RWMutex). The builder requests a "lock" on
 certain cache keys, and is given exclusive access to that key for the duration
 of the lock. This locking mechanism allows multiple builders to share cache data
 even though they're running in parallel.
--- a/website/source/docs/extend/developing-plugins.html.markdown
+++ b/website/source/docs/extend/developing-plugins.html.markdown
@ -14,7 +14,7 @@ reading this, it is assumed that you're comfortable with Packer and also know
 the [basics of how Plugins work](/docs/extend/plugins.html), from a user
 standpoint.

-Packer plugins must be written in [Go](http://golang.org/), so it is also
+Packer plugins must be written in [Go](https://golang.org/), so it is also
 assumed that you're familiar with the language. This page will not be a Go
 language tutorial. Thankfully, if you are familiar with Go, the Go toolchain
 makes it extremely easy to develop Packer plugins.
@ -36,7 +36,7 @@ uses, because they're completely isolated into the process space of the plugin
 itself.

 And, thanks to Go's
-[interfaces](http://golang.org/doc/effective_go.html#interfaces_and_types), it
+[interfaces](https://golang.org/doc/effective_go.html#interfaces_and_types), it
 doesn't even look like inter-process communication is occurring. You just use
 the interfaces like normal, but in fact they're being executed in a remote
 process. Pretty cool.
--- a/website/source/docs/installation.html.markdown
+++ b/website/source/docs/installation.html.markdown
@ -32,9 +32,9 @@ After unzipping the package, the directory should contain a set of binary
 programs, such as `packer`, `packer-build-amazon-ebs`, etc. The final step to
 installation is to make sure the directory you installed Packer to is on the
 PATH. See [this
-page](http://stackoverflow.com/questions/14637979/how-to-permanently-set-path-on-linux)
+page](https://stackoverflow.com/questions/14637979/how-to-permanently-set-path-on-linux)
 for instructions on setting the PATH on Linux and Mac. [This
-page](http://stackoverflow.com/questions/1618280/where-can-i-set-path-to-make-exe-on-windows)
+page](https://stackoverflow.com/questions/1618280/where-can-i-set-path-to-make-exe-on-windows)
 contains instructions for setting the PATH on Windows.

 ## Verifying the Installation
--- a/website/source/docs/other/debugging.html.markdown
+++ b/website/source/docs/other/debugging.html.markdown
@ -62,10 +62,10 @@ the log variable `PACKER_LOG_PATH` using powershell environment variables. For
 example:

    $env:PACKER_LOG=1
-    $env:PACKER_LOG_PATH="packerlog.txt" 
+    $env:PACKER_LOG_PATH="packerlog.txt"

 If you find a bug with Packer, please include the detailed log by using a
-service such as [gist](http://gist.github.com).
+service such as [gist](https://gist.github.com).

 ## Issues Installing Ubuntu Packages

--- a/website/source/docs/post-processors/vagrant-cloud.html.markdown
+++ b/website/source/docs/post-processors/vagrant-cloud.html.markdown
@ -23,7 +23,7 @@ to version and distribute boxes to an organization in a simple way.

 You'll need to be familiar with Vagrant Cloud, have an upgraded account to
 enable box hosting, and be distributing your box via the [shorthand
-name](http://docs.vagrantup.com/v2/cli/box.html) configuration.
+name](https://docs.vagrantup.com/v2/cli/box.html) configuration.

 ## Workflow

--- a/website/source/docs/post-processors/vagrant.html.markdown
+++ b/website/source/docs/post-processors/vagrant.html.markdown
@ -13,7 +13,7 @@ page_title: 'Vagrant Post-Processor'
 Type: `vagrant`

 The Packer Vagrant post-processor takes a build and converts the artifact into a
-valid [Vagrant](http://www.vagrantup.com) box, if it can. This lets you use
+valid [Vagrant](https://www.vagrantup.com) box, if it can. This lets you use
 Packer to automatically create arbitrarily complex Vagrant boxes, and is in fact
 how the official boxes distributed by Vagrant are created.

@ -22,7 +22,7 @@ If you've never used a post-processor before, please read the documentation on
 knowledge will be expected for the remainder of this document.

 Because Vagrant boxes are
-[provider-specific](http://docs.vagrantup.com/v2/boxes/format.html), the Vagrant
+[provider-specific](https://docs.vagrantup.com/v2/boxes/format.html), the Vagrant
 post-processor is hardcoded to understand how to convert the artifacts of
 certain builders into proper boxes for their respective providers.

--- a/website/source/docs/provisioners/ansible-local.html.markdown
+++ b/website/source/docs/provisioners/ansible-local.html.markdown
@ -15,7 +15,7 @@ Type: `ansible-local`
 The `ansible-local` Packer provisioner configures Ansible to run on the machine
 by Packer from local Playbook and Role files. Playbooks and Roles can be
 uploaded from your local machine to the remote machine. Ansible is run in [local
-mode](http://docs.ansible.com/playbooks_delegation.html#local-playbooks) via the
+mode](https://docs.ansible.com/ansible/playbooks_delegation.html#local-playbooks) via the
 `ansible-playbook` command.

 -&gt; **Note:** Ansible will *not* be installed automatically by this
--- a/website/source/docs/provisioners/puppet-masterless.html.markdown
+++ b/website/source/docs/provisioners/puppet-masterless.html.markdown
@ -66,7 +66,7 @@ Optional parameters:
    easier.

 -   `facter` (object of key/value strings) - Additional
-    [facts](http://puppetlabs.com/puppet/related-projects/facter) to make
+    [facts](https://puppetlabs.com/facter) to make
    available when Puppet is running.

 -   `hiera_config_path` (string) - The path to a local file with hiera
--- a/website/source/docs/provisioners/shell.html.markdown
+++ b/website/source/docs/provisioners/shell.html.markdown
@ -72,7 +72,7 @@ Optional parameters:
    `Vars`, which is the list of `environment_vars`, if configured.

 -   `inline_shebang` (string) - The
-    [shebang](http://en.wikipedia.org/wiki/Shebang_%28Unix%29) value to use when
+    [shebang](https://en.wikipedia.org/wiki/Shebang_%28Unix%29) value to use when
    running commands specified by `inline`. By default, this is `/bin/sh -e`. If
    you're not using `inline`, then this configuration has no effect.
    **Important:** If you customize this, be sure to include something like the
@ -196,8 +196,8 @@ git@github.com:exampleorg/myprivaterepo.git" \] }
 *My shell script doesn't work correctly on Ubuntu*

 -   On Ubuntu, the `/bin/sh` shell is
-    [dash](http://en.wikipedia.org/wiki/Debian_Almquist_shell). If your script
-    has [bash](http://en.wikipedia.org/wiki/Bash_(Unix_shell))-specific commands
+    [dash](https://en.wikipedia.org/wiki/Debian_Almquist_shell). If your script
+    has [bash](https://en.wikipedia.org/wiki/Bash_(Unix_shell))-specific commands
    in it, then put `#!/bin/bash` at the top of your script. Differences between
    dash and bash can be found on the
    [DashAsBinSh](https://wiki.ubuntu.com/DashAsBinSh) Ubuntu wiki page.
--- a/website/source/docs/templates/configuration-templates.html.markdown
+++ b/website/source/docs/templates/configuration-templates.html.markdown
@ -60,7 +60,7 @@ in Packer templates. These are listed below for reference.
 -   `build_name` - The name of the build being run.
 -   `build_type` - The type of the builder being used currently.
 -   `isotime [FORMAT]` - UTC time, which can be
-    [formatted](http://golang.org/pkg/time/#example_Time_Format). See more
+    [formatted](https://golang.org/pkg/time/#example_Time_Format). See more
    examples below.
 -   `lower` - Lowercases the string.
 -   `pwd` - The working directory while executing Packer.
--- a/website/source/intro/getting-started/build-image.html.markdown
+++ b/website/source/intro/getting-started/build-image.html.markdown
@ -14,13 +14,13 @@ prev_url: '/intro/getting-started/setup.html'
 # Build an Image

 With Packer installed, let's just dive right into it and build our first image.
-Our first image will be an [Amazon EC2 AMI](http://aws.amazon.com/ec2/) with
+Our first image will be an [Amazon EC2 AMI](https://aws.amazon.com/ec2/) with
 Redis pre-installed. This is just an example. Packer can create images for [many
 platforms](/intro/platforms.html) with anything pre-installed.

-If you don't have an AWS account, [create one now](http://aws.amazon.com/free/).
+If you don't have an AWS account, [create one now](https://aws.amazon.com/free/).
 For the example, we'll use a "t2.micro" instance to build our image, which
-qualifies under the AWS [free-tier](http://aws.amazon.com/free/), meaning it
+qualifies under the AWS [free-tier](https://aws.amazon.com/free/), meaning it
 will be free. If you already have an AWS account, you may be charged some amount
 of money, but it shouldn't be more than a few cents.

@ -30,7 +30,7 @@ few cents, but we're not responsible if it ends up being more.

 Packer can build images for [many platforms](/intro/platforms.html) other than
 AWS, but AWS requires no additional software installed on your computer and
-their [free-tier](http://aws.amazon.com/free/) makes it free to use for most
+their [free-tier](https://aws.amazon.com/free/) makes it free to use for most
 people. This is why we chose to use AWS for the example. If you're uncomfortable
 setting up an AWS account, feel free to follow along as the basic principles
 apply to the other platforms as well.
--- a/website/source/intro/getting-started/parallel-builds.html.markdown
+++ b/website/source/intro/getting-started/parallel-builds.html.markdown
@ -23,7 +23,7 @@ able to make an AMI and a VMware virtual machine in parallel provisioned with
 the *same scripts*, resulting in near-identical images. The AMI can be used for
 production, the VMware machine can be used for development. Or, another example,
 if you're using Packer to build [software
-appliances](http://en.wikipedia.org/wiki/Software_appliance), then you can build
+appliances](https://en.wikipedia.org/wiki/Software_appliance), then you can build
 the appliance for every supported platform all in parallel, all configured from
 a single template.

--- a/website/source/intro/getting-started/setup.html.markdown
+++ b/website/source/intro/getting-started/setup.html.markdown
@ -35,9 +35,9 @@ After unzipping the package, the directory should contain a set of binary
 programs, such as `packer`, `packer-build-amazon-ebs`, etc. The final step to
 installation is to make sure the directory you installed Packer to is on the
 PATH. See [this
-page](http://stackoverflow.com/questions/14637979/how-to-permanently-set-path-on-linux)
+page](https://stackoverflow.com/questions/14637979/how-to-permanently-set-path-on-linux)
 for instructions on setting the PATH on Linux and Mac. [This
-page](http://stackoverflow.com/questions/1618280/where-can-i-set-path-to-make-exe-on-windows)
+page](https://stackoverflow.com/questions/1618280/where-can-i-set-path-to-make-exe-on-windows)
 contains instructions for setting the PATH on Windows.

 ## Verifying the Installation
--- a/website/source/intro/getting-started/vagrant.html.markdown
+++ b/website/source/intro/getting-started/vagrant.html.markdown
@ -12,7 +12,7 @@ prev_url: '/intro/getting-started/parallel-builds.html'
 # Vagrant Boxes

 Packer also has the ability to take the results of a builder (such as an AMI or
-plain VMware image) and turn it into a [Vagrant](http://www.vagrantup.com) box.
+plain VMware image) and turn it into a [Vagrant](https://www.vagrantup.com) box.

 This is done using [post-processors](/docs/templates/post-processors.html).
 These take an artifact created by a previous builder or post-processor and
--- a/website/source/intro/index.html.markdown
+++ b/website/source/intro/index.html.markdown
@ -30,5 +30,5 @@ use tools like Chef or Puppet to install software onto the image.
 A *machine image* is a single static unit that contains a pre-configured
 operating system and installed software which is used to quickly create new
 running machines. Machine image formats change for each platform. Some examples
-include [AMIs](http://en.wikipedia.org/wiki/Amazon_Machine_Image) for EC2,
+include [AMIs](https://en.wikipedia.org/wiki/Amazon_Machine_Image) for EC2,
 VMDK/VMX files for VMware, OVF exports for VirtualBox, etc.
--- a/website/source/intro/platforms.html.markdown
+++ b/website/source/intro/platforms.html.markdown
@ -34,25 +34,25 @@ on supported configuration parameters and usage, please see the appropriate
 [documentation page within the documentation section](/docs).

 -   ***Amazon EC2 (AMI)***. Both EBS-backed and instance-store AMIs within
-    [EC2](http://aws.amazon.com/ec2/), optionally distributed to
+    [EC2](https://aws.amazon.com/ec2/), optionally distributed to
    multiple regions.

 -   ***DigitalOcean***. Snapshots for
-    [DigitalOcean](http://www.digitalocean.com/) that can be used to start a
+    [DigitalOcean](https://www.digitalocean.com/) that can be used to start a
    pre-configured DigitalOcean instance of any size.

-   ***Docker***. Snapshots for [Docker](http://www.docker.io/) that can be used
+-   ***Docker***. Snapshots for [Docker](https://www.docker.io/) that can be used
    to start a pre-configured Docker instance.

 -   ***Google Compute Engine***. Snapshots for [Google Compute
    Engine](https://cloud.google.com/products/compute-engine) that can be used
    to start a pre-configured Google Compute Engine instance.

-   ***OpenStack***. Images for [OpenStack](http://www.openstack.org/) that can
+-   ***OpenStack***. Images for [OpenStack](https://www.openstack.org/) that can
    be used to start pre-configured OpenStack servers.

 -   ***Parallels (PVM)***. Exported virtual machines for
-    [Parallels](http://www.parallels.com/downloads/desktop/), including virtual
+    [Parallels](https://www.parallels.com/downloads/desktop/), including virtual
    machine metadata such as RAM, CPUs, etc. These virtual machines are portable
    and can be started on any platform Parallels runs on.

@ -66,7 +66,7 @@ on supported configuration parameters and usage, please see the appropriate
    be started on any platform VirtualBox runs on.

 -   ***VMware (VMX)***. Exported virtual machines for
-    [VMware](http://www.vmware.com/) that can be run within any desktop products
+    [VMware](https://www.vmware.com/) that can be run within any desktop products
    such as Fusion, Player, or Workstation, as well as server products such
    as vSphere.

--- a/website/source/intro/use-cases.html.markdown
+++ b/website/source/intro/use-cases.html.markdown
@ -37,7 +37,7 @@ stability and testability to infrastructure changes.
 Packer helps [keep development, staging, and production as similar as
 possible](http://www.12factor.net/dev-prod-parity). Packer can be used to
 generate images for multiple platforms at the same time. So if you use AWS for
-production and VMware (perhaps with [Vagrant](http://www.vagrantup.com)) for
+production and VMware (perhaps with [Vagrant](https://www.vagrantup.com)) for
 development, you can generate both an AMI and a VMware machine using Packer at
 the same time from the same template.

@ -49,7 +49,7 @@ through to production.

 Since Packer creates consistent images for multiple platforms in parallel, it is
 perfect for creating
-[appliances](http://en.wikipedia.org/wiki/Software_appliance) and disposable
+[appliances](https://en.wikipedia.org/wiki/Software_appliance) and disposable
 product demos. As your software changes, you can automatically create appliances
 with the software pre-installed. Potential users can then get started with your
 software by deploying it to the environment of their choice.