While trying to get packer to:
1. Assume a role
2. use `auto` price for spot instances
2. Assign an instance profile to the provisioned instance, I hit this error:
```
The provided credentials do not have permission to create the service-linked role for EC2 Spot Instances.
```
Adding the `iam:CreateServiceLinkedRole` entitlement to the role that packer assumes was all I needed to do.
Add newbie friendly reminder that just running a 'vagrant up' in the Packer Vagrant builder output directory does not run the newly built and provisioned .box file.
* document builder id of artifact for each builder's output on website
* document postprocessor artifact ids on website
* Fix links to new communicator page
Co-authored-by: Wilken Rivera <[email protected]>
This adds the new `required_plugins` block to be nested under the packer block.
Example:
```hcl
packer {
required_plugins {
aws = {
version = ">= 2.7.0"
source = "azr/aws"
}
azure = ">= 2.7.0"
}
}
```
For example on darwin_amd64 Packer will install those under :
* "${PACKER_HOME_DIR}/plugin/github.com/azr/amazon/packer-plugin-amazon_2.7.0_x5.0_darwin_amd64"
* "${PACKER_HOME_DIR}/plugin/github.com/hashicorp/azure/packer-plugin-azure_2.7.0_x5.0_darwin_amd64_x5"
+ docs
+ tests
kiddom-kq
Megan Marsh
mr-evilbit
Tim Dawson
Adrien Delorme
Sylvia Moss
Wilken Rivera
Jessi
Adrien Delorme
Kara de la Marck
Pero P
Roman Mingazeev
Felix Hillingshaeuser
Shigetaka Shirouchi
adeniyistephen
Jeff Escalante