Today, let’s take a colloquial look at automatically granting ingress access to your Elastic Beanstalk apps that need to use RDS resources. When we first started, we brought up our RDS instance and our Elastic Beanstalk instance. The two weren’t connected. Of course, as soon as the instance tried to connect to the SQL Server, it couldn’t. Why? Because the RDS security group blocks all access by default, only allowing in what you specify.…

So, you’re running an ASP.NET app in IIS on Elastic Beanstalk and trying to figure out how to keep the app from shutting down due to idleness. Read on, my friend. The answer to your problem lies below. As you’re no doubt aware, low-traffic ASP.NET web apps can time out on IIS due to idleness. This is the server’s way of helping you conserve resources and make sure the machine is available to serve higher demand applications.…

I recently tried deploying a new ASP.NET 4.5 MVC 3 application to our production web server. Everything worked fine on test and on my local machine, so I was not expecting trouble on production. But after I deployed it to production, every URL below the top-level immediately returned a 404 HTTP error. Other applications worked fine, but the new one gave me lots of trouble. This took a bit of work to figure out, but here’s the answer.…