Specifying Custom Disk Sizes with EC2 Instances


How do you specify custom disk sizes for EC2 instances?

I saw this patch, which seems to work around the issue:


I’m not sure if there’s a better way to do this or if this has already been addressed elsewhere.

Expected outcome:

You can enter a custom disk size for an EC2 instance.

Foreman and Proxy versions:


Foreman and Proxy plugin versions:

foreman-tasks 0.14.1
foreman_ansible 2.2.9
foreman_cockpit 2.0.3
foreman_hooks 0.3.14
foreman_memcache 0.1.1
foreman_remote_execution 1.6.4

Other relevant data:
[e.g. logs from Foreman and/or the Proxy, modified templates, commands issued, etc]
(for logs, surround with three back-ticks to get proper formatting, e.g.)


This feature is missing, you can’t do it. Feel free to add the feature if you like, other than that it’s on our lengthy TODO.

1 Like

Thanks @lzap for confirming! When I have some time this weekend, I’ll take a stab at this.
Are these docs still the best to use? I saw something about forklift somewhere. Should I be using that as well?

I think if you want only to work on EC2 Compute Resource then just follow our git checkout guide: Foreman :: Contribute

All you need to do is git clone, npm install, bundler install, rails server and you can start hacking. Obviously, this feature needs new field on Rails form as well as in our API, but it’s doable - let us know if you need assistance. Help is welcome, thanks!

1 Like