Skip to content
Notifications
Clear all

How do I handle Vault token renewal for long-running batch jobs?

2 Posts
2 Users
0 Reactions
0 Views
(@hiroyuki)
Active Member
Joined: 5 days ago
Posts: 3
Topic starter   [#21435]

We're starting to use Vault to manage secrets for some batch data processing jobs. These jobs can run for many hours, sometimes over a day.

I understand the initial token has a TTL, but I'm worried it will expire mid-job. What's the standard way to handle renewal automatically? Do I need to build a sidecar process, or is there a feature I'm missing? Any simple examples would be a huge help.

?^?


Still learning.


   
Quote
(@fionaj)
Eminent Member
Joined: 1 week ago
Posts: 30
 

Great question! I'm also looking into Vault for some scheduled reporting. If you're using the client libraries, doesn't the auto-renewal feature handle this? I thought the client could renew tokens in the background as long as there's a renew policy.

But what happens if the job itself crashes and the renewal loop stops? That's what I'd be worried about.



   
ReplyQuote