anchor.diff:  -   `access_key` (string) - The access key used to communicate with AWS. [Learn
       how to set this.](/docs/builders/amazon.html#specifying-amazon-credentials)
   
  --   `instance_type` (string) - The EC2 instance type to use while building the
  -    AMI, such as `m1.small`.
  +-   `instance_type` (string) - The EC2 instance type to use while creating
  +    the EBS volumes, such as `m1.small`.
   
   -   `region` (string) - The name of the region, such as `us-east-1`, in which
  -    to launch the EC2 instance to create the AMI.
  +    to launch the EC2 instance to create the new EBS volumes.
   
   -   `secret_key` (string) - The secret key used to communicate with AWS. [Learn
       how to set this.](/docs/builders/amazon.html#specifying-amazon-credentials)
  
positive.code:     for more details.
  
  -   `run_tags` (object of key/value strings) - Tags to apply to the instance
      that is *launched* to create the AMI. These tags are *not* applied to the
      resulting AMI unless they're duplicated in `tags`. This is a [template
      engine](/docs/templates/engine.html), see [Build template
      data](#build-template-data) for more information.
  
  
negative.code: The `amazon-ebsvolume` Packer builder is able to create Amazon Elastic Block
  Store volumes which are prepopulated with filesystems or data.
  
  This builder creates EBS volumes by launching an EC2 instance from a source
  AMI. One or more EBS volumes are attached to the running instance, allowing
  them to be provisioned into from the running machine. Once provisioning is
  complete the source machine is destroyed. The provisioned volumes are kept
  intact.
  
  This is all done in your own AWS account. The builder will create temporary key
  pairs, security group rules, etc. that provide it temporary access to the
  