Hi,
First, sorry for the delay.
If I got your point, looks like I need to setup a initial configuration
to get SSH enable, so I follow some templates now and I'll test but I got
stuck because of Memory issue in my laptop, I don't have enough memory to
setup the VM, so I'm waiting for the
The packer program use your credentials to make API directly. Nor
credentials is passed to the EC2 instance launched. The canonical way of
giving it AWS API access is by using iam_instance_profile.
See https://packer.io/docs/builders/amazon-ebs.html#iam_instance_profile
On Wed, Oct 9, 2019,
I believe that's accurate.
On Wed, Oct 9, 2019 at 8:47 AM Mauricio Tavares wrote:
> I was reading https://www.packer.io/docs/builders/qemu.html and it does
> not mention a way to connect to a host running kvm to build thingies. Does
> that mean it only works if packer is local to the kvm
The documentation is a bit vague about how credential passing works. I've
given the packer server all of the credentials it needs for the amazon ebs
builder including iam:passrole for * resources in its instance profile, and
I removed all other references to IAM from the json template. I
Yes, it was.
On Wednesday, October 9, 2019 at 7:31:32 AM UTC-3, Mauricio Tavares wrote:
>
> Has ssh_name been deprecated for ssh_username?
>
--
Your privacy is important to us. That is why we have taken appropriate
measures to ensure the data you provide to us is kept secure. To learn more
Has ssh_name been deprecated for ssh_username?
--
This mailing list is governed under the HashiCorp Community Guidelines -
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of
those guidelines may result in your removal from this mailing list.
GitHub Issues:
