Shulou(Shulou.com)06/02 Report--

Translator's preface

AWS has a wide range of users and a complex product line. The white paper "Architecting for the Cloud-AWS Best Practices" issued by AWS introduces the best practices of cloud architecture in common scenarios, which is of reference significance not only for AWS users, but also for cloud users. The new titanium cloud service engineer specially translated this white paper for cloud users.

The brain map compiled by the translator

Abstract

This white paper is intended for architects and developers building solutions on Amazon Web Services (AWS). This white paper provides architectural guidance and advice on technical design models and how to apply them to cloud computing environments. This white paper provides key concepts and differences when designing solutions on AWS. This white paper also discusses how to take advantage of attributes specific to the dynamic characteristics of cloud computing, such as resilience and infrastructure automation. These models can provide context for more detailed review of selection, operational state, and implementation state, as described in detail in "AWS Well-Architected Framework".

Introduction

Migrating applications to AWS provides organizations with secure and cost-effective infrastructure advantages, even without significant changes (called direct migration). However, in order to take full advantage of the flexibility and flexibility that cloud computing can bring, engineers must improve their architecture to take advantage of AWS capabilities.

For new applications, the cloud-based IT architecture model can help improve efficiency and scalability. These new architectures can support anything from real-time analysis of Internet-scale data to applications with thousands of connections to the Internet of things (IoT) or unpredictable traffic to mobile devices.

Whether you are rearchitecting current applications running in a local environment to run on AWS, or designing cloud native applications, you must consider the differences between traditional and cloud computing environments. This includes architecture selection, scalability, resource types, automation, and flexible components, services, and databases. If you are not familiar with AWS, we recommend that you check the information on the "About AWS" page to get a basic understanding of AWS services.

Differences between traditional and cloud computing environments

Cloud computing differs from traditional local environments in many ways, including flexible, global and scalable capacity, managed services, built-in security, cost optimization options, and various operational models.

3.1 IT assets as configurable resources

In traditional computing environments, you can provide capacity based on theoretical peak estimates. This can lead to periodic expensive idle resources or insufficient capacity. With cloud computing, you can access as much capacity as you need and dynamically expand to meet your actual needs, while paying for the resources you use.

On AWS, servers, databases, storage, and higher-level application components can be instantiated in seconds. You can think of these as temporary resources without the inflexibility and limitations of a fixed and limited IT infrastructure. This will reset the way you handle change management, testing, reliability, and capacity planning. This change in approach encourages the experience by introducing the ability to quickly fail and iterate quickly in the process.

3.2 Global, available and scalable capacity

Using AWS's global infrastructure, you can deploy your application to the AWS availability zone that best meets your requirements (for example, proximity to end users, compliance, data residence restrictions, and costs). For global applications, you can use the Amazon CloudFront content delivery Network (CDN) to reduce latency to end users worldwide. This also makes it easier to operate production applications and databases across multiple data centers, resulting in high availability and fault tolerance. AWS's global infrastructure and the ability to configure capacity as needed allows you to think differently about your infrastructure based on the needs of your application and the expansion of your range of services.

3.3 more advanced managed servic

In addition to Amazon Elastic Compute Cloud (Amazon EC2) computing resources, you can also access a variety of storage, database, analysis, applications and deployment services. Because these services are immediately available to developers, they reduce reliance on in-house expertise and enable organizations to deliver new solutions more quickly. Managed AWS services can reduce operational complexity and costs. They also have scalability and high availability, thus reducing implementation risk.

3.4 built-in security

In a traditional IT environment, infrastructure security reviews can be periodic and manual. In contrast, AWS Cloud provides governance capabilities that continuously monitor configuration changes to IT resources. AWS's security is the highest priority, which means you can benefit from the data center and network architecture built to meet the requirements of most security-sensitive organizations.

Because AWS resources can be programmed with tools and API, you can formalize security policies and embed them in your infrastructure design. With the ability to start a temporary environment, security testing can now be part of a continuous delivery pipeline. Finally, you can take advantage of a variety of cloud-native AWS security and encryption features that can help you achieve higher levels of data protection and compliance.

3.5 cost structure

The traditional cost management of an on-premises solution is usually not tightly coupled with the provision of services. When configuring a cloud computing environment, optimization costs are the architect's basic design tenant. When choosing a solution, you should focus not only on the functional architecture and feature set, but also on the cost profile of the selected solution.

AWS provides fine-grained billing that enables you to track costs associated with all aspects of the solution. There are a range of services that can help you manage your budget, remind you of the costs incurred, and help you optimize resource use and costs.

3.6 Operation and maintenance on AWS

When running a service on AWS, there are several common operation and maintenance models:

Migrated applications, maintaining existing traditional operational models, leveraging the ability to manage infrastructure as code through API, to achieve a reliable and repeatable build process, thereby improving reliability. The refactoring solution leverages a higher level of operational process automation as supporting services, such as AWS Auto Scaling and self-healing architecture. Solutions that are rebuilt and designed for cloud operations are typically fully automated through DevOps processes to enable delivery pipelines and management.

Supporting these changes will change not only the technologies used, but also the cultural changes in the way development and operations teams are managed.

AWS provides tools, processes and best practices to support the transformation of operations and maintenance practices to maximize the benefits of cloud computing.

Description:

This article is translated by Fu Yubin, an operation and maintenance engineer of New Titanium Cloud Service. new Titanium Cloud Services has eight certified AWS engineers and has rich experience in the use and maintenance of AWS, and has provided AWS cloud support for many users.

Original text link:

Https://d1.awsstatic.com/whitepapers/AWS_Cloud_Best_Practices.pdf

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.