# Failling to create ec2 root volume with indicated size on spinning up instnce

**URL:** <https://forum.ansible.com/t/failling-to-create-ec2-root-volume-with-indicated-size-on-spinning-up-instnce/19188>\
**Category:** Ansible Project\
**Tags:** ubuntu\
**Created:** [September 4, 2015, 4:47pm UTC](https://forum.ansible.com/t/failling-to-create-ec2-root-volume-with-indicated-size-on-spinning-up-instnce/19188 "2015-09-04T16:47:26Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Joseph\_DJOMEDA](https://avatars.discourse-cdn.com/v4/letter/j/13edae/32.png) [@Joseph\_DJOMEDA](https://forum.ansible.com/u/Joseph_DJOMEDA)\
**Post date:** [September 4, 2015, 4:47pm UTC](https://forum.ansible.com/t/failling-to-create-ec2-root-volume-with-indicated-size-on-spinning-up-instnce/19188/1 "2015-09-04T16:47:26Z")

</div>

Hello All,

I have been struggling with the past 3 hours trying to figure out why my ubuntu ec2 instances are not been created with the specified volume size.

I have been following the documentation [http://d](http://docs.ansible.com/ansible/ec2_module.html)[ocs.ansible.com/ansible/ec2\_module.html](http://ocs.ansible.com/ansible/ec2_module.html) .

The only difference in there is that it looks to reattach an existing snapshot of a EBS block.

My example is here on pastie [http://pastie.org/10396629](http://pastie.org/10396629)

I have tried using device\_name like sda or xvda1 but no change.

Is it possible to actually specify the size of the ec2 instance root volume with ansible ec2 module?

Can anyone help?

Best Regards,

---

<div class="post-metadata">

**Author:** ![Joseph\_DJOMEDA](https://avatars.discourse-cdn.com/v4/letter/j/13edae/32.png) [@Joseph\_DJOMEDA](https://forum.ansible.com/u/Joseph_DJOMEDA)\
**Post date:** [September 6, 2015, 10:58am UTC](https://forum.ansible.com/t/failling-to-create-ec2-root-volume-with-indicated-size-on-spinning-up-instnce/19188/2 "2015-09-06T10:58:20Z")

</div>

Hello

Anybody ?

Thanks

---

<div class="post-metadata">

**Author:** ![Joseph\_DJOMEDA](https://avatars.discourse-cdn.com/v4/letter/j/13edae/32.png) [@Joseph\_DJOMEDA](https://forum.ansible.com/u/Joseph_DJOMEDA)\
**Post date:** [September 8, 2015, 8:57am UTC](https://forum.ansible.com/t/failling-to-create-ec2-root-volume-with-indicated-size-on-spinning-up-instnce/19188/3 "2015-09-08T08:57:06Z")

</div>

Hello All,

I am totally desperate right now. Any help would be greatly appreciated. it Looks like this is something I am doing in a wrong way.

Best Regards,

---

<div class="post-metadata">

**Author:** ![Brian\_Coca](https://avatars.discourse-cdn.com/v4/letter/b/6de8d8/32.png) [@Brian\_Coca](https://forum.ansible.com/u/Brian_Coca)\
**Post date:** [September 8, 2015, 12:55pm UTC](https://forum.ansible.com/t/failling-to-create-ec2-root-volume-with-indicated-size-on-spinning-up-instnce/19188/4 "2015-09-08T12:55:32Z")

</div>

This does not seem to be possible right now, you can specify the size  
of additional volumes but not resize the default root volume from ec2  
instance creation.  
A workaround is to create an ami with a root volume with the required size.

---

<div class="post-metadata">

**Author:** ![Joseph\_DJOMEDA](https://avatars.discourse-cdn.com/v4/letter/j/13edae/32.png) [@Joseph\_DJOMEDA](https://forum.ansible.com/u/Joseph_DJOMEDA)\
**Post date:** [September 8, 2015, 2:48pm UTC](https://forum.ansible.com/t/failling-to-create-ec2-root-volume-with-indicated-size-on-spinning-up-instnce/19188/5 "2015-09-08T14:48:18Z")

</div>

Thank you Brian for the Clarification

Best Regards,