Amazon has launched managed database and application services that you can use to deploy and manage SQL Server databases and ASP.NET applications on AWS Elastic Beanstalk.
Amazon RDS for SQL Server is the service that you can use to set up, operate and manage relational databases in SQL Server on AWS. Until now, only MySQL and Oracle were supported. There’s a free usage tier that includes 750 hours per month of Amazon RDS micro instances with SQL Server Express Edition, 20GB of database storage and 10 million I/O requests per month for a full year, after which you can run SQL Server on Amazon RDS using the “License Included” or the “Bring Your Own License” service models, with prices starting at $0.035/hour. You can use SQL Server 2008 R2 Express, Web, Standard and Enterprise Edition, and Amazon plans to add support for SQL Server 2012 later this year.
ASP.NET support for Elastic Beanstalk means you can now deploy and manage ASP.NET applications in the AWS cloud. This adds to the existing support for Java and PHP. As with the support for the other languages, you simply upload your ASP.NET application, and Elastic Beanstalk automatically handles the deployment details of capacity provisioning, load balancing, auto-scaling, and application health monitoring. Elastic Beanstalk makes use of the IIS 7.5 software stack, so your existing applications can be deployed with minimal changes to the underlying code. There is no additional charge for Elastic Beanstalk, and you pay only for the AWS resources needed to run your applications.
There’s an AWS Toolkit for Visual Studio that you can use to create applications, and you can try out a hands-on demo showing how to deploy an ASP.NET application on Beanstalk with Amazon RDS for SQL Server in the developer guide.
MIT Professional Education is launching a new online Data Science course next week. This adds to the existing range of options available to those in the data science field who want a credential that c [ ... ]
The first Fortran Reference Manual was released on October 15, 1956, six months before the first working compilers were distributed to IBM customers. While Fortran may have challengers as the fir [ ... ]