Vault's resident RAM requirements are pretty minimal, so I would
imagine if not much else is running 384MB or 512MB should be fine. An
(idle) unsealed Vault server running in dev mode is consuming about
18MB on my system.
Like many servers, it depends on your usage. The more requests you
need to handle at once, the more memory you'll need (but it won't
scale up drastically). Storage requirements depend on which storage
backend you are planning to use and how you're going to use Vault; I
can say that the requirements when using the "generic" backend should
be drastically lower in the soon-to-be-released 0.3 due to leases
being removed from this backend.
Using Vault on a separate machine is a totally reasonable scenario --
you can lock that machine down however you like regardless of how the
rest of your infrastructure is configured.
--Jeff
> --
> This mailing list is governed under the HashiCorp Community Guidelines -
>
https://www.hashicorp.com/community-guidelines.html. Behavior in violation
> of those guidelines may result in your removal from this mailing list.
>
> GitHub Issues:
https://github.com/hashicorp/vault/issues
> IRC: #vault-tool on Freenode
> ---
> You received this message because you are subscribed to the Google Groups
> "Vault" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to
vault-tool+...@googlegroups.com.
> To view this discussion on the web visit
>
https://groups.google.com/d/msgid/vault-tool/6f314b29-b247-4862-be16-2d8e68598262%40googlegroups.com.
> For more options, visit
https://groups.google.com/d/optout.