leveraging amazon web services to host msdn licenses

Leveraging AWS To Host MSDN Licenses

Wayne Saxe – Solutions Architect

Agenda

Why AWS for Windows?

MSDN Licensing on AWS – What Do I Need to Know

What is a Dedicated Instance and How do I Use it?

Using my MSDN License on AWS

Deploying Windows Workloads to AWSSoftware Development on AWS

Why AWS For Windows?

Why AWS for Windows?

Secure Reliable High-Performance Familiar

Cost-Effective Extensive Flexible

MSDN Licensing on AWS

– What Do I Need to

Know?

MSDN Licensing

The Microsoft Volume Licensing Product Use Rights (July 2014) states, “You may install and use permitted copies of the software on Servers and other devices that are under the day-to-day management and control of third parties, provided all such Servers and other devices are and remain fully dedicated to your use.”*

*You are responsible for complying with Microsoft licensing. Please consult your specific license agreement

What is a Dedicated

Instance, and How Do I

Use It?

Dedicated Instances

Amazon EC2 Dedicated Instances help you use your MSDN subscription licenses on AWS for development and test without paying additional Microsoft licensing fees*. Dedicated Instances are Amazon EC2 instances that run on hardware that is dedicated to you—a single customer. Your Dedicated Instances are physically isolated at the host hardware level. They are available as On-Demand and Reserved Instances.

*You are responsible for complying with Microsoft Licensing. Please consult your specific license agreement.

Dedicated Instances: Types

Windows Windows + SQL Standard Windows + SQL Web Windows + SQL Enterprise

General Purpose (M3+M4)

Compute Optimized (C3+C4)

GPU Instances (G2)

Memory Optimized (R3)

Storage Optimized (I2+D2)

Windows

General Purpose (M3+M4)

Compute Optimized (C3+C4)

GPU Instances (G2)


Storage Optimized (I2)

Windows + SQL STD/WEB


Windows + SQL STD/WEB

See http://aws.amazon.com/ec2/purchasing-options/dedicated-instances/ for previous generation instance options

http://aws.amazon.com/ec2/purchasing-options/dedicated-instances/

Dedicated Instances: On-Demand Pricing

See http://aws.amazon.com/ec2/purchasing-options/dedicated-instances/ for up-to date prices and further details

On-demand pricing means no long term commitments: Dev/Test has never been easier!

Price = Hourly per instance fee + a dedicated per region fee ($2/hour)


Dedicated Instances: On-Demand Pricing – Think Parallel

Hour 1 Hour 2 Hour 3 Hour 4

1 server working on a job

sequentially for 4 hours

Dedicated Instances: On-Demand Pricing – Think Parallel

Hour 1 Hour 2 Hour 3 Hour 4

4 servers working on a job in parallel for 4 hours

Same cost (i.e., 4 instance hours), but parallel is 4x faster

Dedicated Instances: Reserved Pricing

See http://aws.amazon.com/ec2/purchasing-options/dedicated-instances/ for up-to date prices and details

Capacity Reservation – Great for Steady State Operations: Have confidence in your ability to launch the number of instances you have reserved when you need them.Significant price discount: up to 75% compared to on-demand


Using My MSDN Licenses

on AWS?

Using MSDN Licenses On AWS

The Value MSDN Gives You

AWS and MSDN Play Very Well Together!

Remember On-Demand vs. Reserved?Mix and Match to Fit your Need

Deploying Windows

Workloads to AWS

Deploying Windows Workloads to AWS

Microsoft Customer Case Studies

Customers are running all kinds of windows workloads on AWS

SharePoint intranet ,extranet and public website farms

Microsoft Dynamics CRM applications

Microsoft Exchange servers and mailboxes

Microsoft SQL Server database for ERP’s like SAP

Applications using .NET framework & IIS Application servers

http://aws.amazon.com/windows/case-studies/

http://aws.amazon.com/windows/case-studies/


Windows Based Machine Images on AWSMicrosoft and Amazon have jointly developed a set of Amazon Machine Images (AMIs) for some of the more popular Microsoft solutions.

Available in all regions that AWS supports to provide a consistent global experience.

7 Windows OS versions, in up to 19 languages

11 SQL Server versions/editions


SharePoint Sample Architecture

10.0.2.0/24

Availability Zone

Availability Zone

Public Subnet

NAT

10.0.0.0/24

DCDB

PrimaryAPPWEB

Domain Controller

AppServer

Web Front-End

RDGW

Public Subnet

NAT

10.0.0.0/24 10.0.2.0/24

DCDB

SecondaryAPPWEB

Domain Controller

AppServer

Web Front-End

RDGW

Users

AvailabilityGroup

SQLServer

SQLServer

Private Subnet

Private Subnet


Active Directory: Deploy from AWS

Amazon EC2 AWS Directory Services

Fully Managed by YouIsolated, Stretched or Federated

Managed By AWSSimple AD and AD Connector


Highly Available SQL Server: MSDN

Availability Zone 1

Private Subnet

Primary Replica

Availability Zone 2

Private Subnet

SecondaryReplica

Synchronous-commit Synchronous-commit

Primary: 10.0.2.100

WSFC: 10.0.2.101

AG Listener: 10.0.2.102

Primary: 10.0.3.100

WSFC: 10.0.3.101

AG Listener: 10.0.3.102

AG Listener:ag.awslabs.net

Automatic Failover


WFSC Cluster: The Quorum

Availability Zone 1

Private Subnet

Primary Replica

Availability Zone 2

Private Subnet

SecondaryReplica

Synchronous-commit Synchronous-commit

Automatic Failover

WitnessServer


WFSC Cluster: The Quorum Placement

Availability Zone 1

Primary Replica

Availability Zone 2

SecondaryReplica

Automatic Failover

WitnessServer

Availability Zone 3


SharePoint Site Migration

Create SharePoint

Farm• Create the New Target Farm to Spec

Copy Database to the Target

Farm

• Place Source Farm and Database in Read-Only Mode

• Backup Content and Service Application Database

• Restore the Databases to the Target Farm

Upgrade Service

Applications

• Configure Service Applications for the Target Farm

• Create New Web Applications matching the Source Farm

Upgrade Content

Databases

• Upgrade and Mount the New Content Databases

Upgrade Site Collections

• Site Owners Responsibility

Software Development on

AWS

Software Development on AWS

Manage EC2Manage VPCManage S3 buckets/filesCreate DDB databases, add, edit, scan, delete recordsDeploy with Elastic Beanstalk or CloudFormationManage SNS eventsManage SQS queuesManage IAM users, groups, and policiesManage RDS databasesManage CloudFront distributions

The AWS Toolkit for Visual Studio Does A Lot!


Needed to deploy and to simplify API calls

API’s require Access Key and Secret Key

5 choices where you can put keys:

In source code – NO

In app.config – NO

In credentials file – YES

In SDK store – YES

Use IAM role (only for API calls made from EC2) – YES

Name it the default profile, or put profile name in app.config

Put “AWSRegion” in app.config

Credential Yourself


All AWS API Calls Are REST based, So you could:

Create canonical request

Create a hash of request, append to the request

Create a string to sign from

Derive a signing key with recursive keyed hash operation

Create the request signature

Add signature to the header

But This is a lot of effort…


Instead, The AWS SDK can Come to the Rescue

Handles all of the REST call details

Handles access key management (store in config files or use EC2 Roles)

Exposes the Services as an Object Oriented API


The AWS API Does a LOT

• AutoScaling

• CloudFormation

• CloudFront

• CloudSearch

• CloudTrail

• CloudWatch

• CodeDeploy

• Cognito

• Config

• DataPipeline

• DirectConnect

• DynamoDB

• EC2

• ElasticCache

• ElasticBeanstalk

• ElasticLoadBalancing

• ElasticMapReduce

• ElasticTranscoder

• Glacier

• IAM

• ImportExport

• KeyManagement

• Kinesis

• Lambda

• OpsWorks

• RDS

• Redshift

• Route53

• S3

• STS

• SES

• SNS

• SWF

• SQS

• StorageGateway

Thank you

leveraging amazon web services to host msdn licenses

Technology