Step 1. Prepare an AWS Account - SharePoint Server on AWS

Step 1. Prepare an AWS Account

  1. If you don't already have an AWS account, create one at http://aws.amazon.com by following the on-screen instructions. Part of the sign-up process involves receiving a phone call and entering a PIN using the phone keypad.

  2. Use the Region selector in the navigation bar to choose the AWS Region where you want to deploy SharePoint on AWS.

    Amazon EC2 locations are composed of Regions and Availability Zones. For a current list of the Availability Zones and the services that are available in them, see the Region Table. Each Region includes at least two Availability Zones, which are isolated from each other with respect to power, network backbone, etc. Deploying your cloud applications across two Availability Zones helps you achieve high availability, even in the face of natural disasters that might impact a single Availability Zone.

    Note

    Consider choosing a Region closest to your data center or corporate network to reduce network latency between systems running on AWS and the systems and users on your corporate network.

  3. Create a key pair in your preferred Region. To do this, in the navigation pane of the Amazon EC2 console, choose Key Pairs, Create Key Pair, type a name, and then choose Create.

    
                        Screenshot showing the user interface that is described in step 3.

    Figure 5: Creating a key pair

    Amazon EC2 uses public-key cryptography to encrypt and decrypt login information. To be able to log into your instances, you must create a key pair. With Windows instances, we use the key pair to obtain the administrator password via the Amazon EC2 console, and then log in using Remote Desktop Protocol (RDP) as explained in the step-by-step instructions in the Amazon Elastic Compute Cloud User Guide.

  4. Verify that you have available Elastic IP addresses in your account. The AWS CloudFormation stack you will launch will automatically create Elastic IP addresses as needed for the SharePoint architecture. Each AWS account has a default quota of five addresses. To ensure beforehand that the AWS CloudFormation template will not fail because you’ve reached this quota, we recommend that you manually create two Elastic IP addresses in your AWS account and then delete them before you launch the Microsoft SharePoint AWS CloudFormation stack.

  5. If necessary, request a service quota increase for the instance types used for the deployment. You might need to request an increase if you already have an existing deployment that uses the same instance types as your SharePoint architecture or if you need additional Elastic IP addresses. To do this, on the Service Quotas console, for each instance type that you want a service quota increase, choose the instance type, choose Request quota increase, and then complete the fields in the quota increase form. It can take a few days for the new service quota to become effective.