1. Nerdio Help Center
  2. Community
  3. NMM Product and Feature Suggestions

Cost Estimator - S2S VPN Tunnel Count and Bandwidth

Avatar
John Tokash

I recently had a prospect looking for AVD and a requirement for S2S VPN Tunnelling to numerous sites (8).   I just realized that the cost estimator does not accommodate for more than 1 VPN S2S Tunnel in its estimating, yet there is a cost per S2S tunnel.  It is marginal, but this should be included.

Alongside that, I had the same prospect considering building a new application in the cloud with IaaS servers.   They have a need for significant bandwidth consumption both inbound and outbound.   There is no way for me to specify additional bandwidth consumption.

It would be ideal if NMM Cost Estimator could offer the following fields to be calculated in:

A general purpose consumption cost add-on (a place to add the 'cost' of Azure resources not offered for inclusion in NMM)

A method to specify a planned number of S2S VPN Tunnels when a VPN Gateway is specified

A method to clearly add additional bandwidth costs (e.g. specify a total amount of planned outbound egress, to which zones, which leads the estimator to produce the right value)

 

3

Comments (2 comments)

Sort by
Avatar
DStephenson
(Edited )

Great call-out, John!
Those features could be useful.

I know we generally don't have many customers with multiple S2S VPNs into Azure once they move to AVD, but if it's a multi-phased migration where we're moving DCs to Azure first, prior to AVD, I can see the use case you're describing.

As a stopgap, until Nerdio can add these features, there is the ability to "write in" products.
Not ideal, but it might help in the meantime. 🙂

 

0
Avatar
John Tokash

This is excellent.

In my case, I didn't catch until my internal costing reporting and analysis surfaced a customer running more expensive than estimated (not by a ton, but it was high enough to get noticed).   In this particular case, the customer moved their IaaS to Azure, and we then linked each satellite office with an independant S2S VPN tunnel on a single gateway.    I don't think that is all that uncommon, but in this case we jumped from the usual 1 or 2 tunnels (where the cost is negligible) to 8 tunnels, where the cost is a bit more noticeable. 

 

That said though - this solution to bring additional 'costs' in is a great workaround, got it!

1

Please sign in to leave a comment.