HCP Vault - can't run operator init

HashiCorp Cloud Platform (HCP) HCP Vault
1

I’m trying to do the bare minimum here. I’ve initialized a developer cluster in HCP Vault. I used the simple template, with nothing initialized. During the setup process, I wasn’t given keys or anything.

I’m trying to run vault operator init to get my unseal keys so I can generate a root key, but I get:


Namespace: admin/
URL: PUT https://vault-test-public-vault-.....z1.hashicorp.cloud:8200/v1/sys/init
Code: 404. Errors:

* unsupported path

It seems like all operator calls fail, and none have access to v1/sys/init. I can’t figure out what’s going on.

2

Hi @nravic

The unseal process with HCP Vault is managed and auto-unsealed. The root namespace for HCP is reserved for platform operations and you start in a namespace called admin. You can generate your admin token from the HCP Portal.

This quick start series should be a good jumping off point:

If you haven’t worked with namespaces before, this may also be a useful read:

3

Ah I didn’t realize an admin token was the same as the root token! Thank you, this was helpful.

4

It’s not 100% 1-to-1, but that admin token gives you access to start. There are a few endpoints you can’t access (Constraints and limitations | HashiCorp Cloud Platform | HashiCorp Developer) even with the admin token. Let us know if you have any other questions.