Hello,

Thanks for writing.

I do not think that integrating cloud-init is a viable option because it is designed for simple systems that just need to get an IP address and some basic configuration. The firewall scenario has a lot more complex configuration and that cannot be (I think) represented by cloud-init.

We have a custom set of scripts to import basic network configuration from AWS:

https://aws.amazon.com/marketplace/pp/B07HYRD4FX

There is a script that detects at boot time if the system is running on AWS:

https://git.ipfire.org/?p=ipfire-2.x.git;a=blob;f=src/initscripts/system/aws...

Then, a configuration script is called that connects to the meta-data service and imports what we need (networking, SSH, etc.):

https://git.ipfire.org/?p=ipfire-2.x.git;a=blob;f=src/initscripts/helper/aws...

This can in theory be used with other platforms, yes. I guess there is some sort of a common standard on the meta-data.

-Michael

On 9 Jan 2019, at 10:00, Nux! nux@li.nux.ro wrote:

Hello,

We are thinking to use Ipfire on a on-premise cloud plaform, these are well supported on Linux by the cloud-init package which can work with all sorts of metadata providers. I understand from twitter that there is something similar in Ipfire which works on AWS. Can anyone shed some more light on this component and perhaps how it could be used with other platforms?

Regards, Lucian

-- Sent from the Delta quadrant using Borg technology!

Nux! www.nux.ro