Thank you for your reply. I did phrase my question wrongly, apologies. I have hard not to setup cluster or Load Balancer, I haver hard times to configure and understand what are potential drawbacks and errors might appear.
Here are couple sources I went through:
- So, I have Lambda application, that does not run either Vault or Consul client (and it cant), so Consul DNS Interface is not an option.
- Lambda talks to AWS ALB that is attached to Vault Cluster. Since July 2018, ALB supports redirects, but I could not find what rules are proper to setup, or default will work.
- I want to use forwarding instead of redirect, but documentation says that if forwarding will fail, it will fallback to redirect I still find confusing under what circumstances it will fallback.
- As per configuration here, to enable forwarding all I need is to setup one listener for vault, and rest be propagated and forwarding is enabled per default.
I understand that AWS ALB is something not Vault related, but nowadays in serverless apps is something good to know if anyone encountered and how configured it, also what most worries is under what circumstances Vault can stop forwarding and start redirecting.