I am running a FreeBSD EC2 instance with a single jail.
In a regular homebrew setup, I would create a jail in "shared IP" (iocage) mode, and configure my router to forward various ports to the jail. In EC2, I am not sure whether to share the public IP or assign a new one.
I created a new Network Interface and Elastic IP, but could not get the jail to ping or telnet anything, not even the host. Which makes me suspect that the jail's internal config is wrong. The host could however ping the jail (which still does not mean that the Elastic IP is the right approach...)
Any ideas? (I posted the above in the AWS forums.)
In addition, I wonder if the jail approach is necessary in EC2? The instance's sole purpose is a webserver for Wordpress.
In my present setup (which I am attempting to migrate to AWS), the host is useful for running various cron jobs which implement my backup solution.
Any suggestions on both issues is greatly appreciated.
In a regular homebrew setup, I would create a jail in "shared IP" (iocage) mode, and configure my router to forward various ports to the jail. In EC2, I am not sure whether to share the public IP or assign a new one.
I created a new Network Interface and Elastic IP, but could not get the jail to ping or telnet anything, not even the host. Which makes me suspect that the jail's internal config is wrong. The host could however ping the jail (which still does not mean that the Elastic IP is the right approach...)
Any ideas? (I posted the above in the AWS forums.)
In addition, I wonder if the jail approach is necessary in EC2? The instance's sole purpose is a webserver for Wordpress.
In my present setup (which I am attempting to migrate to AWS), the host is useful for running various cron jobs which implement my backup solution.
Any suggestions on both issues is greatly appreciated.