Fail2Ban VS terraform-provider-google

now some things you need to think about: - cloud init - this will need to be secure so lock it down hard anything not needed an alternative OS to look at if you have the ability's is https://www.alpinelinux.org/ also as these devices are not that powerfull every extra agent / abstaction layer you add impacts performance need to look at low over head security https://www.crowdsec.net/ and https://github.com/fail2ban/fail2ban (if you call fail2ban security) - using certificates to authenticate ssh login

See https://github.com/fail2ban/fail2ban for beginner's guide, basically you set it up to monitor logfiles and it would act accordingly (plenty of built-in config to handle various daemons so you don't have to write yourself).

- Nginx & crowdsec/fail2ban if you are exposing your parts (services) to the public ( https://hub.docker.com/r/baudneo/nginx-proxy-manager, https://www.crowdsec.net, https://www.fail2ban.org )

— In /etc/fail2ban/action.d/cloudflare.conf I copied the file from https://github.com/fail2ban/fail2ban/blob/master/config/action.d/cloudflare.confand added my ‘cftoken’ and ‘cfuser’ on the bottom

https://github.com/fail2ban/fail2ban is a mature, easy to set up way to have some dynamic firewall rules that respond to attacks. There are more sophisticated options, but they are probably not worth the return on time investment for you.

You can create your own regexes for custom services: https://github.com/fail2ban/fail2ban/wiki/Developing-Regex-in-Fail2ban

Others seem to be (or were) experiencing this too: https://github.com/fail2ban/fail2ban/issues/3100

> DNS without CGO works perfectly

It does not. I know this because it impacts my daily work and the work of others. Honestly if you could make my day and go figure out exactly what's going wrong with the pure go DNS implementation it would make my life alot simpler and I wouldn't have to maintain shell scripts that update etc/hosts to hard code in ipv4 addresses for the APIs I access with terraform.

https://github.com/hashicorp/terraform-provider-google/issue...

GCP Terraform Provider

I think the equivalent for AWS is https://registry.terraform.io/providers/hashicorp/aws/latest/docs and for GCP https://registry.terraform.io/providers/hashicorp/google/latest/docs

There's an open issue in the gcp provider for exactly this. I'd recommend thumbs-upping it if you haven't already, as well as subscribing to notifications so you can see when there are updates.

only some people inside google could answer that but here's an issue already? https://github.com/hashicorp/terraform-provider-google/issues/11648

Not sure if you've solved for this or not, but it didn't work for me running terraform as a service account, it appears that it doesn't handle HTTP headers correctly: https://github.com/hashicorp/terraform-provider-google/issues/6738 but it does work with impersonation of that account, which is what I did. Note that your org can only have 1 access policy, and in my case I had to make google_access_context_manager_access_level anyways.

All I can find is an old thread saying cannot do. https://github.com/hashicorp/terraform-provider-google/issues/6413 Has there been any update to this, or does anyone know of a work around?

If you followed that request, you get to this PR which added the feature and updated this documentation