Microsoft IIS App Server (v13.5 LTS)

Features

• Multi-cloud Support - Launch a server into one several supported cloud infrastructures. Check the ServerTemplate's Images tab to see which MultiCloud Images (MCIs) are included by default. However, additional MCIs can be added to the ServerTemplate, if desired.
• Support for retrieving application code from an SVN repository,from a supported remote object storage (ROS) location (e.g., Amazon S3 bucket, Rackspace Cloud Files container, Azure Blob container, etc.), or from a fully qualified URL that points to a publicly readable *.zip file.
• Built-in support for connecting to an HAProxy load balancer server, Amazon Elastic Load Balancer (ELB), or Rackspace Cloud Load Balancer (CLB).
• Pre-configured alerts for monitoring common system metrics.
• Utilizes RightScale tag-based routing for connecting to HAProxy load balancer servers.
• Support for Powershell 3.0.

Software Application Versions

• .Net 3.5 SP1
• .Net 4.0
• .Net 4.5
• IIS 7.5 (on Windows 2008R2 image)
• IIS 8.0 (on Windows 2012 image)

Retrieval of Application Code

Application code can be retrieved from one of the following locations:

• SVN Repository
• Remote Object Storage (ROS) location
  • Amazon S3 bucket
  • Rackspace Cloud Files container (US and UK)
  • Azure Blob Object Storage container
  • SoftLayer Object Storage container
  • OpenStack (Swift) Object Storage container
• URL to a publicly-readable .zip file (e.g. http://files.example.com/myapp.zip)

The IIS Download application code boot script retrieves your application code from one of the supported locations above, unpacks it (if necessary), and places it into the following directory by default: C:\inetpub\wwwroot\release\<GMT-timestamp>

Application Logs

The ServerTemplate contains a boot script (SYS Configure IIS logs rotation policy), which sets up a Windows scheduled task to upload an archive of any log entries older that one day to a specified container in one of the supported ROS services.

• Remote Object Storage (ROS) location
  • Amazon S3 bucket
  • Rackspace Cloud Files container (US and UK)
  • Azure Blob Object Storage container
  • SoftLayer Object Storage container
  • OpenStack (Swift) Object Storage container

The archives are taken once per day at a randomly generated time that is set at boot time. Currently, there is no way to preconfigure the time prior to launching the server. Archives are not auto-deleted after a certain amount of time. You must manually delete archive files that you no longer want to keep.

The archives are saved as .zip files using the following naming convention: <COMPUTER_NAME>-IISLOGS-YYYYMMDDHHMMSS.zip

Example: http://my-bucket.s3.amazonaws.com/RIGHTSC-FTBKOJU-IISLOGS-2013043016254548.zip

Windows Firewall and Security

The methods you will use to secure access to your IIS server depend on the cloud provider.

• For clouds that support security groups (e.g. Amazon EC2, CloudStack, and OpenStack) you must create a security group for the application servers to use that has TCP port 3389 open for Remote Desktop Connections (RDP), and any other ports required by the server (for example, port 80 for HTTP and/or 443 for HTTPS). 

          Note: All images > v13.5 have Windows Firewall enabled, but allow ports 80 and 443 by default.  

• The SYS open ports in Windows firewall boot script opens up ports specified by the FIREWALL_OPEN_PORTS_TCP input. By default it will allow connections from a load balancer to the application on TCP port 8000.
• By default, TCP Port 3389 is automatically opened to allow RDP access. The permission is defined in the image and is not set by a script in the ServerTemplate like ports 80 and 443.
• You could use the SYS open ports in Windows firewall RightScript as an operational script and the FIREWALL_OPEN_PORTS_TCP and FIREWALL_OPEN_PORTS_UDP inputs to open up additional TCP/UDP ports for ingress communication. TCP Port 8000 is assigned to the FIREWALL_OPEN_PORTS_TCP input value by default to allow ingress traffic from the load balancer to the IIS app server.
• Windows Firewall is turned on by default. However, you can use the SYS Disable Windows Firewall and SYS Enable Windows Firewall scripts to control this setting.
• SSL is supported if you want to use the application server as a standalone server without any load balancing tier. It is recommended that you use a credential for the CERT_PASSWORD input.

Database Connection

A connection string is used by the IIS application to connect to a SQL database. The IIS Add connection string boot script generates a database connection string in your IIS configuration settings (web.config file) with the values that your web application can use to connect to a remote SQL Server database.

If the database does not have a SQL Server user that can be used by the application to access the database, you should use the DB SQLS Create login operational script on the running database server to create the SQL user before you launch the application server.

Note: It's recommended that you use credentials to hide the username and password for the OPT_CONNECTION_STRING_DB_USER_ID and OPT_CONNECTION_STRING_DB_USER_PASSWORD inputs.

Load Balancing Support

The ServerTemplate contains scripts and inputs that support the following load balancing solutions.

• HAProxy
• Amazon Elastic Load Balancers (ELB)
• Rackspace Cloud Load Balancers (CLB)

By default, the ServerTemplate is designed to connect to an HAProxy load balancer launched with RightScale's Load Balancer with HAProxy ServerTemplate via the IIS Register with HAProxy (Chef-based) (v13.x) boot script, which uses machine tags to establish the appropriate connections between the HAProxy load balancer and application servers.

If you want to use an ELB or CLB instead of HAProxy, you should clone the template and customize the boot and decommission scripts by replacing the HAProxy connect/disconnect scripts with the appropriate ELB/CLB connect/disconnect scripts. See the Microsoft IIS App Server (v13.5_LTS) - Tutorial for detailed instructions on how to modify the ServerTemplate.

Custom IIS Monitoring

The SYS IIS monitoring install boot script configures the server for custom monitoring graphs that are specific to IIS applications. View graphs for the following metrics under the Monitoring tab and create custom alerts based on these metrics. Several alerts are preconfigured for the ServerTemplate including a few that are specific to IIS applications. However, you can also create your additional alerts based on any of the other monitored metrics. See Create a Custom Alert Specification.

Below is a list of the monitored metrics that are unique to the IIS ServerTemplate.

• ASP.NET Application Restarts
• ASP.NET Request Wait Time
• ASP.NET Requests Rejected
• ASP.NET Worker Processes Restarts
• ASP.NET Worker Processes Running
• IIS Anonymous Users per Second
• IIS Connection Attempts per Second
• IIS Current Connections
• IIS Get Requests per Second
• IIS Logon Attempts per Second
• IIS Non-Anonymous Users per Second
• IIS Not Found Errors per Second
• IIS Post Requests per Second
• IIS Total Bytes Received
• IIS Total Bytes Sent
• IIS Inetinfo Handle Count
• IIS Inetinfo Percent Processor Time