Track 5 Session 4_ intel 透過AWS Outposts就地佈署 on-premises 雲端環境.pptx
•Als PPTX, PDF herunterladen•
1 gefällt mir•1,132 views
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (20)
Ähnlich wie Track 5 Session 4_ intel 透過AWS Outposts就地佈署 on-premises 雲端環境.pptx
Ähnlich wie Track 5 Session 4_ intel 透過AWS Outposts就地佈署 on-premises 雲端環境.pptx (20)
Mehr von Amazon Web Services
Mehr von Amazon Web Services (20)
Track 5 Session 4_ intel 透過AWS Outposts就地佈署 on-premises 雲端環境.pptx
- 1. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved. 透過AWS Outposts 就地佈署 (on-premises)雲端環境 Bruce Wang Partner Solutions Architect Amazon Web Services T r a c k 5 | S e s s i o n 4
- 2. © 2020, Amazon Web Services, Inc. or its Affiliates. Cloud adoption continues to grow… but not fast enough 73%Organizations are already using the cloud 17%Organizations plan to start using the cloud in the next 12 months https://www.idg.com/tools-for-marketers/2018-cloud-computing-survey/
- 3. © 2020, Amazon Web Services, Inc. or its Affiliates. Applications that are sensitive to latency and variability in latency Need for near real time responses to end user applications Need to control on-site equipment Need to communicate with other on-premises systems Applications that process data locally Need to ensure integrity of ingested signal (e.g., at live events before broadcasting) Need to reliably process messages from industrial equipment to monitor production Need for managing local data stores Applications that need to remain on premises
- 4. © 2020, Amazon Web Services, Inc. or its Affiliates. Customers want the same experience across on-premises and the cloud Same operational consistency Same tools for automation, deployments, and security controls Same services and APIs Same pace of innovation as in the cloud Same reliable, secure, and high performance infrastructure
- 5. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved.
- 6. © 2020, Amazon Web Services, Inc. or its Affiliates. Same AWS-designed infrastructure as in AWS data centers (built on AWS Nitro System) Fully managed, monitored, and operated by AWS as if in AWS Regions Single pane of management in the cloud providing the same APIs and tools as in AWS Regions AWS Outposts: Bringing AWS on-premises
- 7. © 2020, Amazon Web Services, Inc. or its Affiliates. • Industry standard 42U rack • Fully assembled, ready to be rolled into final position • Installed by AWS, simply plugged into power and network • Centralized redundant power conversion unit and DC distribution system for higher reliability, energy efficiency, easier serviceability • Redundant active components including top of rack switches and hot spare hosts AWS Outposts rack
- 8. © 2020, Amazon Web Services, Inc. or its Affiliates. VMware APIs and services to leverage existing skills, automation, and governance policies For customers running VMware SDDC on-premises Same AWS APIs, services, and features as in the AWS cloud EC2 and EBS with support for services including RDS, ECS, EKS, EMR, ALB, others Native AWS VMware Cloud on AWS Available in two variants
- 9. © 2020, Amazon Web Services, Inc. or its Affiliates. Supported countries Canada USA Japan Singapore Australia Republic of Korea All EU Countries Switzerland & Norway Bahrain Hong Kong United Arab EmiratesKingdom of Saudi Arabia UK & Ireland Indonesia New (6/24) Taiwan
- 10. © 2020, Amazon Web Services, Inc. or its Affiliates. Supported regions us-east-2 us-east-1 us-west-1 us-west-2 ca-central-1 eu-west-1 eu-west-2 ap-northeast-1 ap-southeast-1 ap-southeast-2 ap-northeast-2 eu-west-3 me-south-1 eu-north-1 eu-central-1 ap-east-1 us-gov-west-1 us-gov-east-1 eu-south-1
- 11. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved.
- 12. © 2020, Amazon Web Services, Inc. or its Affiliates. Build on the same EC2 Instances & EBS Volumes For general purpose applications For compute intensive applications (media transcoding, gaming servers, machine learning inference) For memory intensive applications (databases, in-memory caches, real time data analytics) For machine learning inference and graphics workstations For I/O intensive applications (NoSQL databases, in-memory or transactional databases, distributed file systems) Local Instance Storage and EBS gp2 volumes for temporary and persistent storage M5 C5 R5 I3G4
- 13. © 2020, Amazon Web Services, Inc. or its Affiliates. Amazon EC2 Instances On Premises Powered by Intel Technologies Intel Xeon Scalable processors workload performance enhancements 2.5 GHz Intel Xeon Scalable Processors (Skylake) G4 2nd Generation Intel Xeon Scalable processors (Cascade Lake)
- 14. © 2020, Amazon Web Services, Inc. or its Affiliates. • Amazon S3 for Outposts (Coming Soon) • Can use any service in the AWS Region Amazon EKS Amazon EC2 Amazon ECS Amazon RDS (Preview) Amazon EBS Amazon EMR Services optimized to run locally
- 15. © 2020, Amazon Web Services, Inc. or its Affiliates. EC2 Auto Scaling Groups AWS CloudFormation CloudWatch CloudTrail Elastic BeanStalk Cloud9 and more… With the same AWS APIs & tools as in the AWS Region
- 16. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved.
- 17. © 2020, Amazon Web Services, Inc. or its Affiliates. Seamlessly extend your regional VPC AWS Region Availability Zone Subnet VPC Availability Zone Subnet
- 18. © 2020, Amazon Web Services, Inc. or its Affiliates. Instances in the Outpost can securely talk to other instances in the VPC via private IP addresses Seamlessly extend your regional VPC AWS Region Availability Zone Subnet VPC Availability Zone Subnet AWS Outposts Subnet
- 19. © 2020, Amazon Web Services, Inc. or its Affiliates. Seamlessly extend your regional VPC AWS Region Availability Zone Subnet VPC Availability Zone Subnet AWS Outposts Subnet Amazon S3 Use Interface Endpoints (powered by Private Link) to access all regional AWS services such as DynamoDB and S3 in your private VPC environment
- 20. © 2020, Amazon Web Services, Inc. or its Affiliates. VIF1 VIF2 • Connect to local network equipment via ports provided in the Outpost’s top of rack (TOR) switches • Configure Virtual Interfaces (VIFs) mapping to your VLANs using Link Aggregation Control Protocol (LACP) • Configure the new local gateway (LGW) on the Outpost to route traffic to and from your local network using these VIFs Router or Switch TOR LACP Router or Switch TOR LACP AWS Outpost Customer Network Connect to your local network LGW
- 21. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved.
- 22. © 2020, Amazon Web Services, Inc. or its Affiliates. Outposts security • Built-in Tamper Detection • Enclosed rack with a lockable door • Data on Outpost is encrypted • Removable and destroyable hardware security key on each server • Encrypted network connection to the AWS Region • Physical security of the Outpost location is the customers responsibility
- 23. © 2020, Amazon Web Services, Inc. or its Affiliates. AWS Outposts: security and compliance AWS Outposts have an updated shared responsibility model AWS is responsible for protecting Outposts’ infrastructure similar to securing infrastructure in the cloud today Customers are responsible for securing their applications running on Outposts as they do in AWS Region Customers are also responsible for the physical security of their Outpost racks AWS services launched locally on Outposts will go through a separate evaluation for certifications and existing certifications WILL NOT apply Compared to certification for other AWS services, with AWS Outposts the customer owns the responsibility for physical security and access controls around the Outpost for compliance certification
- 24. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved.
- 25. © 2020, Amazon Web Services, Inc. or its Affiliates. • Philips is a Dutch-based company that focuses on the areas of healthcare and consumer lifestyle solutions and services • Serving both professional and consumer markets throughout the world in the areas of health systems and personal health • Delivering solutions in diagnostic imaging, image-guided therapy, patient monitoring and health informatics, as well as in consumer health and home care. Philps
- 26. Customer Applications Web Applications Customer Applications Enterprise Applications Customer Devices HealthSuite Authorize Identity and Access Management HealthSuite Host 3rd party services Logging & Auditing Notification Service Service Discovery Databases & Service Brokers HealthSuite Analyze Big Data Ingestion Data Processing Framework HealthSuite Connect Device Management IoT Data Integrations HealthSuite Share IO Bridge HealthSuite Store Clinical Data Repository Telemetry Data Repository Object Storage Repository HealthSuite Share Mobile Applications Consumer Devices Professional Devices De- Identification Consumer and Clinical Solutions HealthSuite Digital Platform Amazon Kinesis Amazon EC2 Amazon SNS API Gateway Amazon CloudWatch AWS IoT Core AWS IoT Device Management Amazon DynamoDB Amazon RDS Amazon S3 AWS Lambda RegionsAvailability Zones HealthSuite Hosting Clinical Viewer DICOM Viewer DICOM Store Insights & Data Lake IHE Customer application layer HealthSuite platform services (PaaS) Underlying infrastructure (IaaS) HealthSuite digital platform
- 27. © 2020, Amazon Web Services, Inc. or its Affiliates. Applications that are sensitive to latency and variability in latency • Need for near real-time responses to providers accessing data • Need to communicate with other on-premises systems • Need for managing local data stores (e.g., PACS system processing high-resolution patient images) • Need to pre-process some data locally before streaming to the cloud (e.g., genomic sequencing data) Applications that process data locally Applications that need to remain on premises
- 28. © 2020, Amazon Web Services, Inc. or its Affiliates. VPC AWS Cloud AWS Outposts AWS Region Hospital Network Hospital campus Amazon ECS Amazon EC2 Amazon RDS <10 ms latency Data sent for long-term storage & backup Outpostslocalgateway BGPmapping Medical images & metadata Local users access the Philips solution Amazon S3 and S3 Glacier storage Monitoring & deployment tools
- 29. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved.
- 30. © 2020, Amazon Web Services, Inc. or its Affiliates. 1. Order Select your compute and storage capacity 2. Install AWS delivers and installs the Outpost 3. Launch Use standard AWS APIs or Management Console to launch and run AWS resources locally 3 steps to get started with AWS Outposts
- 31. © 2020, Amazon Web Services, Inc. or its Affiliates. Step 1: select your compute and storage capacity • Fully assembled, configured, and pre-validated SKUs with mix of EC2 instances, EBS volumes, and built in networking • Simply select a SKU and submit your order • Smallest configuration starting at 4x m5.12xl + 2.7 TiB gp2 volumes, scale to hundreds of racks in an Outpost • View your order status on the AWS Management Console
- 32. © 2020, Amazon Web Services, Inc. or its Affiliates. • AWS delivers to your site in few weeks based on your preferred delivery window • AWS installs and configures the Outpost to connect to the AWS Region and with your local network • Multiple racks at a site can be configured as a single pool of capacity Step 2: AWS delivers and installs the Outpost
- 33. © 2020, Amazon Web Services, Inc. or its Affiliates. Step 3: launch and run AWS resources locally Demo
- 34. Thank you! © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved. Bruce Wang ykwang@amazon.com
Hinweis der Redaktion
- The 2018 IDG Cloud Computing study was conducted to measure cloud computing trends among technology decision-makers, which includes their usage and plans across various cloud service and deployment models, investments, business drivers and impact on business strategy and plans. It was found that Seventy-three percent of organizations have at least one application, or a portion of their computing infrastructure already in the cloud And, 17% of organizations plan to do so within the next 12 months. So, what is causing the delay in adopting the cloud?
- There were two main reasons there was this hesitation or constrain. First, Low Latency Requirements: Some of your business critical applications are sensitive to latency and variability in latency. You need applications to run on premises to respond to events with extremely small millisecond latencies in order to ensure smooth and predictable operations, to provide superior experience to end users, and to maintain competitive advantage. you have adopted the Amazon cloud for centralized operations but find you need to run compute, graphics, or storage intensive workloads on premises to execute localized workflows with precision and quality. These may be workloads running on factory floors for automated operations in manufacturing, real time patient diagnosis or medical imaging, and content and media streaming. Second, Local Data Processing & Data Integrity needs: there has been an exponential increase in the data that is being generated by users and end devices and data integrity is a key concern in locations that are bandwidth constrained. You have data intensive workloads that collect and process hundreds of TBs of data a day. Transmission of this large volume of data to the cloud is wasteful and expensive. Transmitting message or data streams over long distance internet connections can also lead to packet loss resulting in data integrity problems. It would be good to process the data locally to respond to events in real time and to have better control on analyzing, backing up, and restoring the data. At the same time, you would also like to leverage cloud services such as AI/ML frameworks or analytics as they do in the cloud for data visualization and insights; use services such as RDS to store data locally and seamlessly transfer it to the cloud later. Applications that process this data to drive better data visualization or business insights need to run on premises close to the data sources or end devices.
- So if we should summarize , you want Same reliable, secure and high performance infrastructure Same operational consistency Same services, APIs, tools for automation, deployment pipelines, security controls which can provide you the same pace of innovation as in the cloud.
- So, what is AWS Outposts? Outposts enable you to develop once, and deploy in the AWS cloud or on-premises without having to rewrite your applications. With Outposts, you have the same hardware and software infrastructure and a consistent set of services and tools across your AWS cloud and on-premises environments to build and run modern, cloud-native applications anywhere AWS Outposts are fully managed and supported by AWS, and AWS automatically manages and updates AWS Outposts as part of its ongoing operations in the public AWS region. You do not have to worry about updating or patching infrastructure AWS Outposts allow you to choose the AWS native variant of AWS Outposts or the VMware Cloud on AWS Outposts variant as your management plane for your APIs, management console, automation, governance policies, and security controls for all your applications across the AWS cloud and on-premises locations. You use the same AWS Console to view and manage their resources, whether those resources and services are in the AWS Cloud or on premises. You can use the same AWS CLI and SDKs as you use today to run and deploy applications, using the API endpoints as you use today to run applications in the AWS Cloud. That said, it is also important to understand that AWS Outposts is not a replacement for building and running applications in the AWS Cloud. If an application can run in the AWS Cloud, it should. The scalability, operational efficiency, and cost optimizations gained by running applications in the AWS Cloud will always be second to none. AWS Outposts allows you to extend the AWS Cloud to your on premises for applications that need to run on premises, as well providing a jumping point for migrating enterprise applications on premises to AWS that have longer and more involved migration timelines and dependencies.
- So, what does the Outpost look like? It comes in a 42U rack form, fully assembled, ready to be rolled into position. AWS associated will show up at your data center at a coordinated with with the rack. They’ll roll it in, plug the power and network. It comes with centralized redundant power conversion unit with DC power distribution. It has redundant active components such as switches and spare capacity.
- AWS Outposts will be available in two options: The AWS native variant of Outposts allows you to use the same APIs and control plane you use in the AWS cloud to build and run your applications, but do it on-premises. You will be able to run Amazon EC2 instances and EBS volumes on Outposts. And, at launch or soon thereafter, services such as RDS, ECS, EKS, SageMaker, and EMR will also be available locally on the AWS native variant of Outposts. Other services, such as S3, DynamoDB, and Lambda will be available as Private Link endpoints in the customer’s own VPC. The VMware variant allows you to run VMware Cloud on AWS locally on Outposts to use the same VMware control plane and APIs you use to run your on-premises infrastructure. This variant delivers the entire VMware Software-Defined Datacenter - compute, storage, and networking infrastructure - to run on-premises using AWS Outposts and allows you to take advantage of the ease of management and integration with AWS services.
- Outpost is currently available to be installed in the US, in all EU countries, including Switzerland and Norway, Japan, the republic of Korea and Australia. We will be adding more countries starting this quarter, so stay tuned.
- Similarly, we have a list of supported regions to which you can connect Outposts to. Additional regions will be supported later this quarter. Note that, you can pick any region to connect to depending on your requirements. For example, if the Outposts is installed in Dublin but all your resources are part of eu-central-1, you can establish your connection to eu-central for shared resource access.
- AWS Outposts catalog includes options supporting the latest generation Intel powered EC2 instance types with or without local instance storage. General purpose (M5/M5d) instances provide a balance of compute, memory, and network resources and can be used for general-purpose workloads, web and application servers, backend servers for enterprise applications, gaming servers, and caching fleets. Compute optimized (C5/C5d) instances are optimized for compute-intensive workloads and deliver cost-effective high performance at a low price per compute ratio. Memory optimized (R5/R5d) instances are designed to deliver fast performance for workloads that process large data sets in memory. Graphics optimized (G4dn) are designed to help accelerate machine learning inference and graphics-intensive workloads. They can be used for machine learning inference for applications like adding metadata to an image, object detection, recommender systems, automated speech recognition, and language translation. They also provide a very cost-effective platform for building and running graphics-intensive applications, such as remote graphics workstations, video transcoding, photo-realistic design, and game streaming in the cloud. I/O optimized (I3en) provides dense Non-Volatile Memory Express (NVMe) SSD instance storage optimized for low latency, high random I/O performance, high sequential disk throughput, and offers the lowest price per GB of SSD instance storage on Amazon EC2. It is well suited for NoSQL databases (Cassandra, MongoDB, Redis), in-memory databases (SAP HANA, Aerospike), scale-out transactional databases, distributed file systems, data warehousing, Elasticsearch, analytics workloads. In addition, Outposts offers local instance storage, and Elastic Block Store (EBS) gp2 volumes for persistent block storage. Just as in the AWS Region, you can use EBS gp2 volumes for boot or data volumes, and attach or detach EBS volumes to EC2 instances on your Outpost. It provides snapshot and restore capabilities and lets you increase volume size without any performance impact. All EBS volumes and snapshots on Outposts are fully encrypted by default. Any EBS snapshots will be stored using Amazon S3 in the Region associated with your Outpost. EBS is offered in tiers of 2.7 TB, 11 TB, 33 TB, and 55 TB and above.
- All Amazon tools will just work as well. API calls will automatically be logged via CloudTrail, existing Cloud Formation templates will also work. AWS tools such as AWS CloudFormation, Amazon CloudWatch, AWS CloudTrail, and others can be used to run and manage applications running on premises just the same as they are used for cloud workloads today. They will have same security controls such as IAM permissions, VPC security groups, and access control lists. You can access AWS tools running in the region such as AWS CloudFormation, Amazon CloudWatch, AWS CloudTrail, Elastic BeanStalk, Cloud 9, and others to run and manage applications on Outposts the same way as you do in the cloud today.
- You can seamlessly extend your VPC on premises by creating a subnet and associating it with an Outpost just as you associate subnets with an AZ in the cloud. <Click> As the control plane is in the public region, you can access a wide range of AWS services locally on your Outpost or in region through public endpoints or privately through VPN. <Click> Instances in the Outpost can securely talk to other instances in your VPC through private IP addresses. Use Interface Endpoints (powered by Private Link) to access all regional AWS services such as DynamoDB and S3 in your private VPC environment or use their regional public endpoints as shown here
- You can seamlessly extend your VPC on premises by creating a subnet and associating it with an Outpost just as you associate subnets with an AZ in the cloud. <Click> As the control plane is in the public region, you can access a wide range of AWS services locally on your Outpost or in region through public endpoints or privately through VPN. <Click> Instances in the Outpost can securely talk to other instances in your VPC through private IP addresses. Use Interface Endpoints (powered by Private Link) to access all regional AWS services such as DynamoDB and S3 in your private VPC environment or use their regional public endpoints as shown here
- You can seamlessly extend your VPC on premises by creating a subnet and associating it with an Outpost just as you associate subnets with an AZ in the cloud. <Click> As the control plane is in the public region, you can access a wide range of AWS services locally on your Outpost or in region through public endpoints or privately through VPN. <Click> Instances in the Outpost can securely talk to other instances in your VPC through private IP addresses. Use Interface Endpoints (powered by Private Link) to access all regional AWS services such as DynamoDB and S3 in your private VPC environment or use their regional public endpoints as shown here
- You can Connect to your local network equipment via ports provided in the Outpost’s top of rack (TOR) switches You can Configure Virtual Interfaces (VIFs) mapping to your VLANs using Link Aggregation Control Protocol (LACP) You can Configure the new local gateway (LGW) on the Outpost to route traffic to and from your local network using these VIFs
- AWSserver-5059.jpg
- Three steps to getting started with the Outposts. You order, we install and ready to launch!
- First, you go to the console and browse through the catalog to find the configuration that meets your needs. You can Filter by instance types, EBS storage, services supported, and site constraints (eg, power draw or networking uplink) You’ll then create a logical Outpost with site and network information Once done, you can place an order right from the console.
- Once you place an order, our associates will get in touch with you to confirm the information. Within few weeks, AWS associates will deliver to your site AWS associates will install and configure the Outpost to connect to the AWS Region and with your local network We can also install Multiple racks at a site provided you have the power, space, cooling and network connectivity to support it.