Ah, this worked
{
"device_name" : "/dev/sda1",
"delete_on_termination" : true,
"volume_size" : 250,
"volume_type" : "gp2"
},
On Thursday, June 13, 2019 at 5:32:56 PM UTC-4, ZillaYT wrote:
>
> Like this (some info committed). I use AWS Ubuntu
Like this (some info committed). I use AWS Ubuntu AMI ami-024a64a6685d05041
as my base AMI
{
"variables" : {
"aws_access_key" : "{{ env `AWS_ACCESS_KEY_ID` }}",
"aws_secret_key" : "{{ env `AWS_SECRET_ACCESS_KEY` }}",
"ssh_private_key" : "{{ env `SSH_PRIVATE_KEY` }}",
"aws-ami-us
How do your template look like?
On Thu, Jun 13, 2019, 20:36 ZillaYT wrote:
> This setting doesn't work for me, I still get the default 8G AWS AMI
> partition.
>
> amazon-ebs: xvda202:008G 0 disk
>
> amazon-ebs: └─xvda1 202:108G 0 part /
>
> On Thursday, December 22, 2016 at
This setting doesn't work for me, I still get the default 8G AWS AMI
partition.
amazon-ebs: xvda202:008G 0 disk
amazon-ebs: └─xvda1 202:108G 0 part /
On Thursday, December 22, 2016 at 9:15:48 AM UTC-5, Pierre Freund wrote:
>
> Thanks very much.
>
> I tried lot of combinati
Thanks very much.
I tried lot of combinations, I thought I tried this one, but obviously not
:)
For debian 8 hvm, the right configuration is :
"launch_block_device_mappings": [
{
"device_name": "/dev/xvda",
"delete_on_terminatio
I do that with "launch_block_device_mappings". An example is below. The
"device_name" for the root device will depend a bit on the underlying AMI,
and whether it is PVM or HVM, but it should be the same as the Root Device
Name associated with the AMI itself.
"launch_block_device_map
