New crate installation - version 3.0.2

CrateDB
1

Hi,

Been running cratedb inhouse with no problems. We are trying to setup crate on AWS and for whatever reason I cannot make it bound to ANY ip other than 127.0.0.1.

I’ve tried all possible variations with:
network.host: (local, site, global, 0.0.0.0)
network.bind_host: (local, site, global, 0.0.0.0)
network.publish_host: (local, site, global, 0.0.0.0)

Nothing works. Crate starts and it’s always the same thing:
publish_address {127.0.0.1:5432}, bound_addresses {[::1]:5432}, {127.0.0.1:5432}
publish_address {127.0.0.1:4200}, bound_addresses {[::1]:4200}, {127.0.0.1:4200}
publish_address {127.0.0.1:4300}, bound_addresses {[::1]:4300}, {127.0.0.1:4300}

Any ideas?

2

WELP, apparently it was not reading our /etc/crate/crate.yml file … so now it’s good.

But the nodes are not joining - new ticket …

3

Isn’t https://crate.io/docs/crate/guide/en/latest/deployment/cloud/aws/ec2-setup.html helping here?