I will be running multiple Hermes agents (profiles...
# infisical-help
m
I will be running multiple Hermes agents (profiles) and gateways. Are there any considerations when creating Agent Vault Services if I am using multiple Hermes agent profiles, or is it just when creating credentials that I need to append the _profile for each Hermes agent? Any assistance with using Agent Vault with multiple Hermes agents with their own API keys would be appreciated. Thanks in advance!
✅ 1
p
Hey hey! Since you have multiple gateways you'll be running, I would give each gateway an agent token to a vault. You can still use the same service in agent vault and grant each gateway the ability to proxy through that vault. You ALSO have the option to give each agent its own separate vault. So each agent will have one token scoped to one vault, that vault with agent / profile specific credentials. Let me know if this helps or if you have any other questions. I'd be happy to further assist!
If you haven't yet seen this video, I would check it out!

https://www.youtube.com/watch?v=6dERVjLk0-Q▾

m
Hello, this is the video I'm using to set up Agent Vault with Hermes. Its a great video! I will try your suggestions! Thank you!
Hello @Jake (Infisical) hope you had a great weekend! I'm at section 8 of the video/instructions where I have to configure the Hermes gateway.env file and systemd drop-in. I'll follow the instructions for the default gateway, but what changes are needed when you have multiple gateways for additional Hermes profiles? I don't believe I can use the same .env as the vault will be different for some of the gateway profiles. Appreciate clarifying steps 8-1, 8-2, and 8-3 for multiple Hermes gateways. Cheers!
j
Checking!
In the case that multiple gateways are running I would use separate .env files with separate respective agent tokens. i.e. gateway_hermes.env, gateway_coder.env, etc.
Each token in AV scoped to the respective vault for that agent
m
Ok I will try that. Thanks.
✅ 1
j
NP. Let me know!
m
Hello @Jake (Infisical) Hope you're having a great day! I will be trying the multiple gateways tomorrow and will let you know. When using Slack, there are two tokens - SLACK_BOT_TOKEN and SLACK_APP_TOKEN. Can both configured in the Agent Vault Service? I have successfully implemented the Slack BOT Token, but how would I configure the Slack APP token in the AV service so I don't store it in the Hermes .ENV file? Would I just add it as another substitution for the same Slack service, and how would it be configured? We are also looking at using the TencentDB Agent Memory provider proxy running on the Hermes server (for Hermes) but I see from first glance that it stores API Keys in .env and config.yaml files. If you get a moment, can Agent Vault also be used to protect the TencentDB API Keys, especially if running on the Hermes server? github.com/TencentCloud/TencentDB-Agent-Memory and regolo.ai/tencentdb-agent-memory-the-complete-guide-to-persistent-memory-for-hermes-and-openclaw-with-zero-data-retention#… Thanks in advance!
p
Hey @martin434 sorry for the late response here. Both of those can indeed be configured in the AV service. You will use passthrough with substitution as one of them will be in the body, correct!
Looking into this second part, standby!
Re the second part: Looks like in principle yes, Agent vault could broker those type of keys. The problem is that Agent Vault works as a proxy, and the TencentDB Agent Memory gateway/sidecar doesn't look like it will respect the HTTP_PROXY variable. I'll be curious to hear your experience with it!