Description Hi Vapi team, I’m deploying the latest on-prem stack in the AWS il-central-1 region. EKS itself launches fine, but every managed NodeGroup that uses your

enclave-launch-template-*

templates fails with:

CreateNodegroup: InvalidRequestException: 
Specifying enclave support for an instance is not supported in this region.

Because il-central-1 (and a few other newer regions) still doesn’t allow Nitro Enclave–enabled instances in managed NodeGroups, the bootstrap halts and the whole backend stack rolls back. Request * Could you add a flag or template parameter that turns off

EnclaveOptions { Enabled: true }

in the generated launch templates? * Or ship an alternate launch template without enclave support that we can reference when deploying in these regions. This would let us complete the install today without switching to another AWS region. Thanks a lot!

Thanks for reaching out about our on-prem solution. Here’s where things stand: * Current focus: Our engineering team is fully dedicated to rolling out VAPI enhancements and new workflow features. * On-prem support: At the moment, solution-engineering resources for on-prem deployments are limited. The only available path today is via our enclave-based option. * Why this decision: We’ve prioritized core product improvements and upcoming features over expanding on-prem capabilities right now. I apologize for any inconvenience this causes. We’ll revisit broader on-prem support as our roadmap evolves—your feedback on specific requirements is invaluable in shaping that effort.

Will you provide a solution-engineering support for my usecase if I become an Enterprise-grade customer?

We don't offer that right now. We're planning to work on a new on-prem deployment by the end of the year, which should allow us to do it then.

did you use the AWS cloud formation template and get the dashboard to succesfully load?