53 Commits (b4e70cc0ec0b24b040fe0dfbf68c560dc6c0f736)

Author	SHA1	Message	Date
phils	700e747cb9	Fix IAM permissions for spot based on changes in 7682	7 years ago
Adrien Delorme	4f46bd74ab	Merge pull request #7313 from kristi/patch-1 ... add DescribeInstanceStatus to minimum permissions	7 years ago
Kristi	7e7e486901	add DescribeInstanceStatus to minimum permissions ... Packer needs DescribeInstanceStatus or else it ends up waiting forever for the instance to become ready.	7 years ago
Megan Marsh	af7131b169	tests, logic cleanup, docs for vagrant builder	7 years ago
Megan Marsh	ad21367b21	vagrant builder	7 years ago
Matthew Hooker	88d27f37a7	make fmt-docs	7 years ago
Kevin Hicks	03f8680c3c	Remove json specifier from doc code block	7 years ago
Megan Marsh	14166fdd99	update amazon import docs to include the env vars for setting aws waiter delays and timeouts	8 years ago
Fotios Lindiakos	896ceee902	Update list of required IAM permissions ... The `ec2:DescribeSpotPriceHistory` is required when the `spot_price` parameter is set to `auto`.	8 years ago
EximChua	286a5aa8c7	Update info on format of the credentials file ... Update info on format of the credentials file.	8 years ago
stack72	1bc471073f	docs/aws: Update documentation for AWS Spot Instances ... The docs didn't specify that `ec2:DescribeSpotInstanceRequests` was required. This causes an error as follows: ``` Error waiting for spot request (sir-yg6866gj) to become ready: UnauthorizedOperation: You are not authorized to perform this operation. ``` This is because the permission to describe instance state is not available	8 years ago
alexgottschalkmedal	38e419dd8c	Update amazon.html.md ... Fix typo - CreateKeypair should be CreateKeyPair	8 years ago
Matthew Hooker	b16f2ec64b	builder/amazon: Use sdk default cred providers ... I think we were overcomplicating things. The SDK provides the correct credential chain by default, so let's use that. This patch does a quick check for static credentials and uses those if found, then defaults to the default credential provider chain. This patch also removes the metadata timeout argument. Current versions of the SDK have short timeouts by default, so I don't believe this is needed.	8 years ago
Megan Marsh	d07a2dda7d	fix grammar in docs	8 years ago
SwampDragons	23567aad6f	Merge pull request #5197 from BWITS/feature/policy_for_spot_instance ... Add policies to use spot instance to create the AMI	8 years ago
Matthew Hooker	5b64f71702	Merge pull request #5764 from hashicorp/fix5760 ... "borrow" access config code from terraform.	8 years ago
Matthew Hooker	a9b48309c9	update amazon authentication docs ... Correct docs to reflect new behavior. This is largely borrowed from terraform.	8 years ago
Matthew Hooker	f5ea1e8312	Use WaitUntilInstanceReady waiter	8 years ago
Matthew Hooker	cba1a0598f	document additional aws permission	8 years ago
Bill Wang	28a986691d	Add policies to use spot instance to create the AMI	9 years ago
Matthew Hooker	bcc0d24bf4	run docs through pandoc	9 years ago
Matthew Hooker	176715b7f0	document profile option.	9 years ago
Matthew Hooker	160d31a568	update documentation on automatic lookup of credentials. ... Reverts work in #4612	9 years ago
Rickard von Essen	5bc8edc3b2	Updated AWS docs for using default chain	9 years ago
Rickard von Essen	f4f0560101	Updated docs about AWS credentials handeling	9 years ago
Matthew Hooker	d30605fdfb	use json markdown syntax	9 years ago
Seth Vargo	6b80c21043	Revamp pages and docs to fit HashiCorp brand	9 years ago
Kerim Satirli	37feec41d9	fixes broken link to EBS surrogate page	9 years ago
Matthew Hooker	131e1e3857	clarify that it's profile name	9 years ago
Matthew Hooker	6b95de73c4	document how aws-sdk uses the shared credentials file ... from https://docs.aws.amazon.com/sdk-for-go/api/aws/credentials/\#SharedCredentialsProvider	9 years ago
James Nugent	635aeb765b	amazon/ebssurrogate: Add New Builder ... This commit adds a new type of builder which builds an AMI based on a snapshot of an EBS volume which is provisioned on a "surrogate" instance. This can be used to build operating system images from scratch, but unlike the `chroot` builder does not require running from an AWS EC2 instance.	9 years ago
Matthew Hooker	b04a878ea8	small spelling fix	9 years ago
Rickard von Essen	d1b9a91e3d	Change all builder docs to the expected file names	9 years ago
Rickard von Essen	4ce3b8712a	Replace unencrypted EBS snapshots with encrypted ... To ensure that groups and users attributes are added to the encrypted snapshots.	9 years ago
Ari Aviran	46f217f255	amazon - Snapshot permissions correctly applied ... Fixes #3344	9 years ago
Rickard von Essen	d8ef6d1977	Fixed formatting of source_ami_filter example	9 years ago
Matthew Hooker	7443e21992	fix broken link in docs	9 years ago
Matthew Hooker	1cf9dbf27d	fix json	9 years ago
Matthew Hooker	3d69af1247	sort/uniq IAM policies	9 years ago
Matthew Hooker	ac8e70ade0	Revert "Remove duplicate permission" ... This reverts commit 78067ff949.	9 years ago
Matthew Hooker	8eab0ee5b2	Merge pull request #4109 from mitchellh/b-docs ... builder/amazon: Fix doc of EBS Volume builder name	9 years ago
James Nugent	33c423529d	builder/amazon: Fix doc of EBS Volume builder name ... Various things still referred to `ebsinit` or `ebs-volume` - the imported name was `amazon-ebsvolume`.	9 years ago
Amo Chumber	78067ff949	Remove duplicate permission ... In the suggested policy `ec2:CopyImage` was listed twice. I've also sorted alphabetically to make it easier for somebody who might be recreating the policy in the AWS gui to follow along more easily.	9 years ago
James Nugent	b1ff8c3bfc	builder/amazon: Add `ebs-volume` builder ... This commit adds a builder that works like EBS builders, except does not create an AMI, and instead is intended to create EBS volumes in an initialized state. For example, the following template can be used to create and export a set of 3 EBS Volumes in a ZFS zpool named `data` for importing by instances running production systems: ``` { "variables": { "aws_access_key_id": "{{ env `AWS_ACCESS_KEY_ID` }}", "aws_secret_access_key": "{{ env `AWS_SECRET_ACCESS_KEY` }}", "region": "{{ env `AWS_REGION` }}", "source_ami": "{{ env `PACKER_SOURCE_AMI` }}", "vpc_id": "{{ env `PACKER_VPC_ID` }}", "subnet_id": "{{ env `PACKER_SUBNET_ID` }}" }, "builders": [{ "type": "amazon-ebs-volume", "access_key": "{{ user `aws_access_key_id` }}", "secret_key": "{{ user `aws_secret_access_key` }}", "region": "{{user `region`}}", "spot_price_auto_product": "Linux/UNIX (Amazon VPC)", "ssh_pty": true, "instance_type": "t2.medium", "vpc_id": "{{user `vpc_id` }}", "subnet_id": "{{user `subnet_id` }}", "associate_public_ip_address": true, "source_ami": "{{user `source_ami` }}", "ssh_username": "ubuntu", "ssh_timeout": "5m", "ebs_volumes": [ { "device_name": "/dev/xvdf", "delete_on_termination": false, "volume_size": 10, "volume_type": "gp2", "tags": { "Name": "TeamCity-Data1", "zpool": "data", "Component": "TeamCity" } }, { "device_name": "/dev/xvdg", "delete_on_termination": false, "volume_size": 10, "volume_type": "gp2", "tags": { "Name": "TeamCity-Data2", "zpool": "data", "Component": "TeamCity" } }, { "device_name": "/dev/xvdh", "delete_on_termination": false, "volume_size": 10, "volume_type": "gp2", "tags": { "Name": "TeamCity-Data3", "zpool": "data", "Component": "TeamCity" } } ] }], "provisioners": [ { "type": "shell", "start_retry_timeout": "10m", "inline": [ "DEBIAN_FRONTEND=noninteractive sudo apt-get update", "DEBIAN_FRONTEND=noninteractive sudo apt-get install -y zfs", "lsblk", "sudo parted /dev/xvdf --script mklabel GPT", "sudo parted /dev/xvdg --script mklabel GPT", "sudo parted /dev/xvdh --script mklabel GPT", "sudo zpool create -m none data raidz xvdf xvdg xvdh", "sudo zpool status", "sudo zpool export data", "sudo zpool status" ] } ] } ``` StepModifyInstance and StepStopInstance are now shared between EBS and EBS-Volume builders - move them into the AWS common directory and rename them to indicate that they only apply to EBS-backed builders.	9 years ago
Jinesh Choksi	0f4d2341cb	Packer v0.11.0 requires "ec2:DescribeSecurityGroups" permissions to work ... Without the "ec2:DescribeSecurityGroups" permission, you would get the following error: 2016/10/25 16:03:28 ui: ==> aws: Creating temporary security group for this instance... 2016/10/25 16:03:28 packer.exe: 2016/10/25 16:03:28 Temporary group name: packer 580f7440-2135-068c-99b7-35595a7522d1 2016/10/25 16:03:28 ui: ==> aws: Authorizing access to port 22 the temporary security group... 2016/10/25 16:03:28 packer.exe: 2016/10/25 16:03:28 [DEBUG] Describing tempSecurityGroup to ensure it is available: sg-38e0355e 2016/10/25 16:03:29 packer.exe: 2016/10/25 16:03:29 [DEBUG] Error in querying security group UnauthorizedOperation: You are not authorized to perform this operation. 2016/10/25 16:03:29 packer.exe: status code: 403, request id: bc664eff-cc01-42c1-8408-23493c11d92d	9 years ago
Matthew Hooker	24c4ba3bb5	add the error you might see	10 years ago
Matthew Hooker	7a1b84cec1	add some debugging info for if your clock is skewed	10 years ago
Huy Nguyen	5e1aa22dc7	IAM permission needed to deregister failed images (#3796)	10 years ago
www.elconas.de	e6c590ace4	Fix IAM Policy to avoid 'Error enabling Enhanced Networking on xxxxxxx: UnauthorizedOperation: You are not authorized to perform this operation' (#3696)	10 years ago
mieciu	23296988b8	Update example AWS policy document	10 years ago