Handling automated Vault Deployment errors

I’ve been working a couple of days on learning how to deploy a node of Vault with three Consul node as back-end on AWS.

I followed all the instructions as directed and when I attempted to test my Vault through the UI I came up with the surprise that the deployment didn’t work.

So what I did next, is I connected to the VM hosting vault and asked the system for Vault status and this is what I got:

system vault status

Output:

"storage migration check error: error="Unexpected response code: 500"

I performed the deployment once more and attempted received the following error:

"storage migration check error: error="Unexpected response code: 403"

With this I learned the error was related to Consul.

I learned that to review whats going on with a Consul node I can do it with the following commands:

consul monitor

To learn the status of my consul nodes and its details:

consul operator raft list-peers

This one will display the current nodes and its status as member or leader.

I haven’t figured out the source of the issue yet, but I came closer to understand the system’s status.