AWS re:Invent 2016: Design, Deploy, and Optimize Microsoft SharePoint on AWS (WIN304)

Download AWS re:Invent 2016: Design, Deploy, and Optimize Microsoft SharePoint on AWS (WIN304)

Post on 16-Apr-2017

426 views

Category:

Technology

3 download

Embed Size (px)

TRANSCRIPT

<ul><li><p> 2016, Amazon Web Services, Inc. or its Affiliates. All rights reserved.</p><p>Design, Deploy, and Optimize Microsoft SharePoint on AWS</p><p>Lou De La Torre, Solutions Architect</p><p>Zlatan Dzinic, Senior Consultant</p><p>November 30, 2016</p><p>WIN304</p></li><li><p>What Well Cover: Everything SharePoint on AWS</p><p>The Fundamentals</p><p>Architectural Scenarios</p><p>Best Practices</p><p>&gt; EC2 Networking</p><p>Active Directory</p><p>Remote Access</p><p>Purchasing Options</p><p>The Fundamentals</p><p>Architectural Scenarios</p><p>Best Practices</p><p>&gt;</p><p>Marketplace Builds</p><p>Hybrid: AWS as a DR Site</p><p>Multi-AZ SharePoint</p><p>SharePoint 2016</p><p>Quick Start</p><p>The Fundamentals</p><p>Architectural Scenarios</p><p>Best Practices &gt;</p><p>Amazon EC2 Best Practices</p><p>SQL Best Practices</p><p>Migration Best Practices</p><p>Going Beyond IaaS</p></li><li><p>Fundamentals: Single VPC Patterns</p><p>Public and Privately Routed VPCThis design pattern is used for workloads that need to accommodate a combination of public and private routing needs, such as all-in Internet-facing, multi-tier web applications supported by databases or other privately routed backend systems.</p><p>Internal-Only VPCThis design pattern is used to create a network environment that is only accessible from an existing, internal network, such as internally facing or back-office systems.</p><p>On-Premises and Internet-Accessible VPCThis design pattern is used to create a network environment that has the ability to communicate with both on-premises (privately routed) and external (publicly routed) resources</p><p>Internet-Accessible VPCThis design pattern is primarily used for test, R&amp;D, sales demo, production, and other environments that require a network environment that is completely isolated from a customers internal network.</p><p>For more info on configuring VPCs, see AWS Answers for Networking.</p><p>https://aws.amazon.com/answers/networking/</p></li><li><p>Internet GatewayHighly available VPC component that allows communication between instances in your VPC and the Interneta</p><p>NAT GatewayEnable instances in a private subnet to connect to the Internet or other AWS services, but prevent the Internet from initiating a connection with those instancesa</p><p>Virtual Private Network (VPN)a</p><p>Virtual Private Gateway (VPG)a</p><p>AWS Direct Connecta</p><p>For more info on configuring external access, see Amazon VPC for On-Premises Network Engineers, Part One.</p><p>Fundamentals: External Connectivity</p><p>https://aws.amazon.com/blogs/apn/amazon-vpc-for-on-premises-network-engineers-part-one/</p></li><li><p>Fundamentals: Active Directory Patterns</p><p>Directory TrustsExtending On-Premises Directory Over Secure Connections to AWS Using Either Active Directory or AWS Directory Service for Microsoft AD.</p><p>Federated TrustsBuilding Federated Trusts From On-Premise to AWS Using Active Directory Federation Services or Other SAML Compliant Software and Services.</p><p>Availability Zone</p><p>On-Premises Data Center</p><p>VPN Direct Connect</p><p>DomainController</p><p>Domain Controlleron AmazonEC2</p><p>Either/Or</p><p>AWS Directory </p><p>Service</p><p>On-Premises Data Center</p><p>Internet</p><p>WAP / ADFS</p><p>Secure</p><p>Domain Controlleron AmazonEC2</p><p>DomainController</p><p>WAP/ADFSon Amazon EC2</p></li><li><p>See the Remote Desktop Gateway on the AWS Cloud: Quick Start for additional info</p><p>The Fundamentals: Remote Access</p><p>http://docs.aws.amazon.com/quickstart/latest/rd-gateway/welcome.html</p></li><li><p>The Fundamentals: Purchasing Options</p><p>For more info on licensing Windows on AWS, see Microsoft Licensing on AWS.</p><p>Options for using Microsoft software licenses on the AWS Cloud</p><p>Buy LicensesFrom AWS</p><p>Bring LicensesTo AWS</p><p>2,300+ products available for 1-click deployment across 35 distinct product categories, including several SharePoint 2013 &amp; 2016 builds ranging from single-server to multiple-server builds.</p><p>If youve already purchased Microsoft software, bring your own licenses (BYOL) to the AWS Cloud and extend the lifecycle of your software without additional hardware costs.</p><p>Using license-included instances allows you access to fully compliant Microsoft software licenses bundled with Amazon EC2 and ability to pay for them as you go with no upfront costs or long-term investments.</p><p>https://aws.amazon.com/windows/resources/licensing/</p></li><li><p>What Well Cover: Everything SharePoint on AWS</p><p>The Fundamentals</p><p>Architectural Scenarios</p><p>Best Practices</p><p>&gt;</p><p>Marketplace Builds</p><p>Hybrid: AWS As a DR Site</p><p>Multi-AZ SharePoint</p><p>SharePoint 2016</p><p>Quick Start</p></li><li><p>Browse, Test, and Buy Enterprise Softwarea</p><p>Simplified Procurement Processa</p><p>Consume as Needed Without Overprovisioning</p><p>Architecture: Marketplace</p><p>One AWS Billa</p><p>Consume Hourly, Monthly, Annuallya</p><p>Customers run over 143M hours of software per month</p></li><li><p>Architecture: Marketplace</p><p>SharePoint Enterprise 2016 for AWS "All In One" for SME or Line of Business implementation. Best for Test or Development teams working on short-term development projects, to share and collaborate on new ideas and engage in social conversations.</p><p>SharePoint Enterprise 2016 All In One</p><p>Availability Zone</p><p>Subnet</p><p>Windows Server 2012R2</p><p>Active Directory Domain Services</p><p>SQL Server 2014 Enterprise</p><p>SharePoint Server 2016</p><p>Internet Gateway</p></li><li><p>Architecture: Marketplace</p><p>Availability Zone</p><p>Subnet</p><p>Windows Server 2012R2</p><p>Active Directory Domain Services</p><p>Internet Gateway</p><p>Subnet</p><p>Windows Server 2012R2</p><p>SQL Server 2014 Enterprise</p><p>Subnet</p><p>Windows Server 2012R2</p><p>SharePoint Server 2016</p><p>SharePoint Enterprise 2016 Business</p><p>SharePoint Enterprise 2016 is well suited for enterprises looking for a collaboration tool in multiple geo-locations, including support for external users.</p></li><li><p>Architecture: AWS As a DR Site</p><p>Higher RTO Lower RTO</p><p>Backup &amp; Restore Pilot Light</p><p>Spectrum of Disaster Recovery Options</p><p>Back up to S3 with AWS Storage Gatewaya</p><p>Replace On-Premises Tape Systema</p><p>Leverage Amazon Glacier for Data Archiving</p><p>SQL Server Log Shipping over VPN or Direct Connecta</p><p>EC2 Instances in Stopped State a</p><p>Cool DR Site with Lower Costs</p><p>Warm Site</p><p>SQL Server Asynchronous Always-On Availability Group over Direct Connecta</p><p>EC2 Instances in Running State a</p></li><li><p>Architecture: AWS As a DR Site</p><p>Minimal Amount of Running Infrastructure on AWS Keeps Costs Low</p><p>Backup &amp; Restore</p><p>Typically Longer RTO</p><p>For more info on configuring backup and recovery, see Enterprise Backup and Recovery On-Premises to AWS.</p><p>For more info on configuring AWS Storage Gateway, see AWS Storage Gateway Documentation.</p><p>Availability Zone</p><p>Direct Connect, VPN or HTTPS</p><p>On-Premises Data Center</p><p>HTTPSAWS Storage Gateway VM</p><p>Storage: Direct Attached or SAN</p><p>APP Server</p><p>WFE Server SharePoint EC2 Instances in Stopped State</p><p>SQL Server EC2 Instance in Stopped State</p><p>AWS DR SharePoint Farm</p><p>APP Server</p><p>WFE Server</p><p>On-PremisesSharePoint Farm</p><p>App Server</p><p>Backup ServerSupporting iSCSI, CIFS, SMB</p><p>SQLServer</p><p>SQL Server</p><p>EBS Volume</p><p>Storage Gateway Service</p><p>S3 Bucket </p><p>WFE Server</p><p>WFE Server</p><p>https://d0.awsstatic.com/whitepapers/best-practices-for-backup-and-recovery-on-prem-to-aws.pdfhttp://docs.aws.amazon.com/storagegateway/latest/userguide/WhatIsStorageGateway.html</p></li><li><p>Architecture: AWS As a DR Site</p><p>Small Amount of Running EC2 Infrastructure on AWS</p><p>Pilot Light</p><p>SQL Log Shipping Increases Automation of Database Layer Backup and Restore Operations</p><p>For more info on configuring log shipping between on premises and AWS, see Deploying Microsoft SQL Server on Amazon Web Services.</p><p>For more info on configuring a pilot light DR environment on AWS, see Using Amazon Web Services for Disaster Recovery.</p><p>Availability Zone</p><p>TransactionLog Shipping</p><p>Direct Connect or</p><p>VPN</p><p>TransactionLog Replay</p><p>APP ServerAPP Server</p><p>WFE ServerWFE Server SharePoint EC2 Instances in a stopped state</p><p>AWS DR SharePoint Farm</p><p>SQL Server</p><p>On-Premises Data Center</p><p>On-PremisesSharePoint Farm</p><p>WFE Server</p><p>WFE Server</p><p>App Server</p><p>App Server</p><p>SQL Server</p><p>https://d0.awsstatic.com/whitepapers/RDS/Deploying_SQLServer_on_AWS.pdfhttp://d36cz9buwru1tt.cloudfront.net/AWS_Disaster_Recovery.pdf</p></li><li><p>Architecture: AWS As a DR Site</p><p>Lower RTOs Require More Running EC2 Infrastructure on AWS</p><p>AlwaysOn Availability Group(s) Further Increase Automation of Database Synchronization/Restore</p><p>Warm Site</p><p>For more info on configuring always-on availability groups between on premises and AWS, see Deploying Microsoft SQL Server on Amazon Web Services.</p><p>Availability Zone</p><p>APP ServerAPP Server</p><p>WFE ServerWFE Server SharePoint EC2 Instances in a running state</p><p>AWS DR SharePoint Farm</p><p>SQLServer</p><p>On-Premises Data Center</p><p>On-PremisesSharePoint Farm</p><p>WFE Server</p><p>WFE Server</p><p>App Server</p><p>App Server</p><p>SQL Server</p><p>SQL Server</p><p>Asynchronous Commit</p><p>SQL Server Always On Availability Group</p><p>Sync</p><p>Direct Connect or</p><p>VPN</p><p>https://d0.awsstatic.com/whitepapers/RDS/Deploying_SQLServer_on_AWS.pdf</p></li><li><p>Architecture: Multi-AZ SharePoint</p><p>Single Production Farm</p><p>Database Backups Shipped Offsite and/or Replicated to Alternate Data Center</p><p>Typical SharePoint DR Plan Involves a Full Farm Rebuild Followed by a Restore of Content Database Backups</p><p>Typical On-Premises SharePoint Setup</p><p>Data Center #1</p><p>Storage Volumes or Database Backups Synchronized/Replicated to Alternate Datacenter</p><p>Production SharePoint Farm</p><p>Data Center #2</p><p>Database Backups Located on Tape Media Transported to Offsite Facility</p></li><li><p>Architecture: Multi-AZ SharePoint</p><p>AWS Multi-AZ Design Pattern</p><p>AWS is built around Regions and Availability Zones (AZs)</p><p>Region is a physical location in the world where we have multiple Availability Zones</p><p>Availability Zones consist of one or more discrete fault tolerant data centers, each with redundant power, networking and connectivity</p><p>Availability Zones are connected to each other with private fiber-optic low-latency links</p><p>You can achieve High Availability by deploying your application that spans across multiple Availability Zones</p><p>Data Center Redundancy Achieved with Little or No Effort!</p><p>Availability Zone #1</p><p>Web Server</p><p>DB Server</p><p>Web Server</p><p>DB Server</p><p>Single Application Boundary Spanning Multiple AZs</p><p>Synchronous Replication / Automatic Failover</p><p>Availability Zone #2Low Latency</p></li><li><p>Architecture: Multi-AZ SharePoint</p><p>VPC, Two AZs, Single Public and Multiple Private Subnetsa</p><p>Include Remote Access, NAT Gateways and Active Directorya</p><p>Stretched SharePoint Farm Spanning Multiple AZs Providing Data Center Redundancy a</p><p>Multi-AZ Reduces Risk Profile and Simplifies DR Planning</p><p>AWS Multi-AZ SharePoint 2013</p><p>Availability Zone #1</p><p>Web Tier (Subnet) App Tier (Subnet) Directory Tier (Subnet)</p><p>Web Tier (Subnet) App Tier (Subnet) Data Tier (Subnet) Directory Tier (Subnet)</p><p>Availability Zone #2</p><p>VPC NAT Gateway</p><p>Public Tier (Subnet) Data Tier (Subnet)</p><p>Windows Server RD Gateway</p><p>VPC NAT Gateway</p><p>Public Tier (Subnet)</p><p>Windows Server RD Gateway</p><p>DomainController</p><p>DomainController</p><p>Availability Zone #1</p><p>Directory Tier (Subnet)</p><p>Web Tier (Subnet) App Tier (Subnet) Data Tier (Subnet) Directory Tier (Subnet)</p><p>Availability Zone #2</p><p>AWS ELB</p><p>VPC NAT Gateway</p><p>Public Tier (Subnet) Data Tier (Subnet)</p><p>Windows Server RD Gateway</p><p>VPC NAT Gateway</p><p>Public Tier (Subnet)</p><p>Windows Server RD Gateway</p><p>SQL Server</p><p>SQL Server</p><p>S SharePointWFE SSharePointAPP</p><p>Web Tier (Subnet) App Tier (Subnet)</p><p>DomainController</p><p>DomainControllerS</p><p>SharePointAPPS</p><p>SharePointWFE</p><p>Always OnAvailability Group </p><p>(Synchronous)</p></li><li><p>Fully Supported to Run a SharePoint DR Farm/Two-Region DR Pattern on AWS for SharePoint</p><p>AWS Supports Traditional Two-Data Center Patterns</p><p>Architecture:Multi-AZ SharePoint</p><p>Availability Zone #1</p><p>Directory Tier (Subnet)</p><p>Web Tier (Subnet) App Tier (Subnet) Directory Tier (Subnet)</p><p>Availability Zone #2</p><p>AWS ELB</p><p>VPC NAT Gateway</p><p>Windows Server RD Gateway</p><p>VPC NAT Gateway</p><p>Public Tier (Subnet)</p><p>Windows Server RD Gateway</p><p>SQL Server DomainController</p><p>DomainController</p><p>Region US East</p><p>Region US West</p><p>Web Tier (Subnet) App Tier (Subnet) Data Tier (Subnet) Directory Tier (Subnet)</p><p>Availability Zone #1</p><p>VPC NAT Gateway</p><p>Public Tier (Subnet)</p><p>Windows Server RD Gateway</p><p>DomainController</p><p>Always OnAvailability Group (Asynchronous)</p><p>SQL Server</p><p>Data Tier (Subnet)</p><p>VPN</p><p>DR Farm</p><p>S SharePointAPPSSharePointWFE</p><p>Public Tier (Subnet) Web Tier (Subnet) App Tier (Subnet)</p><p>S SharePointAPPSSharePointWFE</p><p>S SharePointAPPSSharePointWFE</p><p>Data Tier (Subnet)</p><p>SQL Server</p><p>Always OnAvailability Group </p><p>(Synchronous)</p><p>Production Farm</p><p>Availability Zone #1</p></li><li><p>Architecture: SharePoint 2016</p><p>Minimum Size SharePoint 2016 MinRole Farma</p><p>Does Not Provide HA</p><p>MinRole SharePoint</p><p>Availability Zone #1</p><p>Directory Tier (Subnet)</p><p>Web Tier (Subnet) App Tier (Subnet) Data Tier (Subnet) Directory Tier (Subnet)</p><p>Availability Zone #2</p><p>AWS ELB</p><p>VPC NAT Gateway</p><p>Public Tier (Subnet) Data Tier (Subnet)</p><p>Windows Server RD Gateway</p><p>VPC NAT Gateway</p><p>Public Tier (Subnet)</p><p>Windows Server RD Gateway</p><p>SQL Server</p><p>S SharePointFront-end SSharePointSearch</p><p>Web Tier (Subnet) App Tier (Subnet)</p><p>DomainControllerS</p><p>SharePointApplication</p><p>SSharePointDistributedCache</p></li><li><p>Architecture: SharePoint 2016</p><p>HA SharePoint 2016 MinRole Farma</p><p>Supports No Downtime Patching</p><p>MinRole SharePoint</p><p>Availability Zone #1</p><p>Directory Tier (Subnet)</p><p>Web Tier (Subnet) App Tier (Subnet) Data Tier (Subnet) Directory Tier (Subnet)</p><p>Availability Zone #2</p><p>AWS ELB</p><p>VPC NAT Gateway</p><p>Public Tier (Subnet) Data Tier (Subnet)</p><p>Windows Server RD Gateway</p><p>VPC NAT Gateway</p><p>Public Tier (Subnet)</p><p>Windows Server RD Gateway</p><p>SQL Server</p><p>SQL Server</p><p>Web Tier (Subnet) App Tier (Subnet)</p><p>DomainController</p><p>DomainController</p><p>S SharePointApplication</p><p>Always OnAvailability Group </p><p>(Synchronous)</p><p>S SharePointFront-end</p><p>SSharePointDistributedCache</p><p>S SharePointSearchS</p><p>SharePointDistributedCache</p><p>SSharePointDistributedCache</p><p>S SharePointApplication</p><p>S SharePointSearch</p><p>S SharePointFront-end</p></li><li><p>Architecture: SharePoint 2016</p><p>HA SharePoint 2016 MinRole Farma</p><p>Supports No Downtime Patching</p><p>Add Office Online Server and Workflow Manager</p><p>MinRole SharePoint</p><p>Availability Zone #1</p><p>Directory Tier (Subnet)</p><p>Web Tier (Subnet) App Tier (Subnet) Data Tier (Subnet) Directory Tier (Subnet)</p><p>Availability Zone #2</p><p>AWS ELB</p><p>VPC NAT Gateway</p><p>Public Tier (Subnet) Data Tier (Subnet)</p><p>Windows Server RD Gateway</p><p>VPC NAT Gateway</p><p>Public Tier (Subnet)</p><p>Windows Server RD Gateway</p><p>SQL Server</p><p>SQL Server</p><p>Web Tier (Subnet) App Tier (Subnet)</p><p>DomainController</p><p>DomainController</p><p>S SharePointApplication</p><p>Always OnAvailability Group </p><p>(Synchronous)</p><p>S SharePointFront-end</p><p>SSharePointDistributedCache</p><p>S SharePointSearchS</p><p>SharePointDistributedCache</p><p>SSharePointDistributedCache</p><p>S SharePointApplication</p><p>S SharePointSearch</p><p>S SharePointFront-end</p><p>OfficeOnline Server</p><p>OfficeOnline Server</p><p>Workflow Manager</p><p>Workflow Manager</p><p>Workflow Manager</p></li><li><p>Architecture: SharePoint 2016</p><p>MinRole Enhancementsa</p><p>Supports Shared Rolesa</p><p>Minimum Number of Farm Servers for HA = 4</p><p>SharePoint 2016 Feature Pack1</p><p>Availability Zone #1</p><p>Directory Tier (Subnet)</p><p>Web Tier (Subnet) App Tier (Subnet) Data Tier (Subnet) Directory Tier (Subnet)</p><p>Availability Zone #2</p><p>AWS ELB</p><p>VPC NAT Gateway</p><p>Public Tier (Subnet) Data Tier (Subnet)</p><p>Windows Server RD Gateway</p><p>VPC NAT Gateway</p><p>Public Tier (Subnet)</p><p>Windows Server RD Gateway</p><p>SQL Server</p><p>SQL Server</p><p>Web Tier (Subnet) App Tier (Subnet)</p><p>DomainController</p><p>DomainController</p><p>Always OnAvailability Group </p><p>(Synchronous)</p><p>S</p><p>SharePointFront-end with Distributed Cache</p><p>SSharePointApplication with Search</p><p>S</p><p>SharePointFront-end with Distributed Cache</p><p>SSharePointApplication with Search</p></li><li><p>Architecture: SharePoint Quick Start</p><p>AWS CloudFormation Automated Build</p><p>Extensible JSON AWS CloudFormation </p><p>Templates Available on GitHub</p><p>Creates Stacks of AWS Resources</p><p>Bring Your Own License for SharePoint</p><p>DevOps for SharePoint</p></li><li><p>Architecture:...</p></li></ul>