Learn More





Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...DNN on Amazon EC2 instanceDNN on Amazon EC2 instance
New Post
8/5/2014 3:27 PM

With Amazon pushing the cloud so heavily, I am looking at what it would cost to put a LIVE DNN site with the SQL Server on the EC2 web server.  Has anyone done this before?  I have personally done it and got it all working just fine, but did not go to PROD with was not that difficult, since it is essentially just a col-located box.  I also have to say that it was a helluva lot easier than getting it to run on GoDaddy for example.  My question really revolves around the pricing.  Amazon's pricing model is pretty convoluted and I suspect that might be purposeful, because once you are on there, it can be hard to unwind.  Anyway, to the point, I wanted to do a comparison between SQL Server licensing required for a web server we have in house versus just pushing it out to an EC2 instance, however, I am not 100% sure I have turned over all the rocks on the AWS pricing model.  has anyone else done this comparison and what were your conclusions?  Did you see licensing benefit to pushing your DNN server to an Amazon EC2 instance? 


 BTW-I realize Azure is likely much less expensive, but since I cannot run a FOR XML on the WHERE clause in Azure it makes it a bit problematic as well as some internal pushback on using ANYTHING Microsoft.



New Post
8/6/2014 10:22 AM

What level of SQL Server licensing are you looking to replicate on AWS?  Pricing varies depending on whether you are running SQL Express, SQL Web or SQL Standard.  You can use the RDS pricing page to get a good comparison.

Joe Brinkman
DNN Corp.
New Post
8/6/2014 11:22 AM
SQL Express seems too light and I was not 100% sure DNN could run against it. The RDS instance can be difficult to get data in and out of, so I was trying to do a straight comparison between SQL Standard on an EC2 instance versus a home grown server with SQL Standard on it. Both Amazon's and Microsoft's pricing models are a bit difficult to interpret with confidence. There are lots of caveats and very little straightforward pricing. On the AWS side, there are the data charges and the potential need for more IP addresses and other hidden gotchas that just seem to show up on the monthly bill unexpectedly even though you used there price calculation engines on their web sites. on the Microsoft side, I have not been able to get a good handle on how M$ will charge licensing on a VM running against a Quad core CPU. Straight core pricing would mean that it is close to $8k a year, but I am told that Microsoft will give us a break if we are running on a VM, but exactly what that virtual machine pricing looks like seems to be up to M$ interpretation. Given all this complexity, I was wondering if someone had navigated this billing licensing swamp and managed to not get eaten by alligators.
New Post
8/6/2014 12:48 PM
As I'm sure you know, the sheer variety of needs for web based installations makes quoting any price/setup a futile effort. I've been running on AWS for years without a hitch. Unless you have a specific need for SQL Standard, I'd go with SQL Web for cost reasons. Of course, AWS has a BYOL option too that you could investigate if you already have a license.

The next question is whether you need to run your SQL on a separate box or boxes or whether you can run it on the same box as your web server. That would depend largely on your use case and would determine if you would be better off with RDS.

One thing I would highly recommend is getting a Reserved Instance, but do the calculations as there are certain pricing sweet spots - depending on instance type and resource utilization (light vs medium vs heavy). M3 instance types tend to be a good-for-most-situations instance. C3 is a good option if you will be doing more processing on the server. Of course those are web servers and not DB servers.

Most of the extra charges on AWS I've found to be pretty minor. Storage is cheap. Bandwidth you'd have to pay for regardless of where you hosted (either the price is built-in to your fee or you pay separately). However, a lot of internal traffic within the same Availability Zones is free so you can minimize costs there as well.

Everything depends on the specifics of your situation but if I were to hazard a guess, I'd offer that a well-managed AWS setup is probably cheaper overall than rolling your own in-house - especially if you think about on-going maintenance, upgrades, staffing, etc.


Create simple forms or build complete module solutions XMod Pro is the best-selling forms and views module of all time.
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...DNN on Amazon EC2 instanceDNN on Amazon EC2 instance

These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
Try Evoq
For Free
Start Free Trial
a Demo
See Evoq Live
Need More Information?