Other cloud service models include platform-as-a-service (PaaS), which typically are more fully managed services that deploy customers’ applications, or software-as-a-service (SaaS), which are cloud-based applications.
The core features of AWS are infrastructure-as-a-service (IaaS) - that is, virtual machines and supporting infrastructure. Many companies use a hybrid of private and public clouds. Private clouds are within a single (usually large) organization. In general, “ cloud computing” can refer to one of three types of cloud: “public,” “private,” and “hybrid.” AWS is a public cloud provider, since anyone can use it. AWS is the dominant public cloud computing provider. 🚧 Areas where correction or improvement are needed (possibly with link to an issue - do help!). 📗 📘 📙 Colors indicate basics, tips, and gotchas, respectively. 🕍 A mild warning attached to “full solution” or opinionated frameworks that may take significant time to understand and/or might not fit your needs exactly the opposite of a point solution (the cathedral is a nod to Raymond’s metaphor). 💸 Cost issues, discussion, and gotchas. ⛓ Lock-in: Products or decisions that are likely to tie you to AWS in a new or significant way - that is, later moving to a non-AWS alternative would be costly in terms of engineering effort. 🐥 Relatively new (and perhaps immature) services or features. 🔸 “Regular” gotcha, limitation, or quirk (used where consequences are things not working, breaking, or not scaling gracefully). ❗ “Serious” gotcha (used where risks or time or resource costs are significant: critical security risks, mistakes with significant financial cost, or poor architectural choices that are fundamentally difficult to correct). 📒 Marks standard/official AWS pages and docs. It is written by and for engineers who use AWS. This guide is not sponsored by AWS or AWS-affiliated vendors. (We believe this is both possible with a guide of this format, unlike in some other venues.) Suggestions, notes, and opinions based on real experience can be extremely valuable. Thoughtful opinion with rationale is welcome. Thoughtful: The goal is to be helpful rather than present dry facts. Current: We can keep updating it, and anyone can contribute improvements. Practical: Basic facts, concrete details, advice, gotchas, and other “folk knowledge”. It is for both beginners and the experienced. It is not a tutorial, but rather a collection of information you can read and return to. Currently, this guide covers selected “core” services, such as EC2, S3, Load Balancers, EBS, and IAM, and partial details and tips around other services. Like any open source effort, we combine efforts but also review to ensure high quality. This guide is open to contributions, so unlike a blog, it can keep improving. Please help by joining the Slack channel (we like to talk about AWS in general, even if you only have questions - discussion helps the community and guides improvements) and contributing to the guide. This is an early in-progress draft! It’s our first attempt at assembling this information, so is far from comprehensive still, and likely to have omissions or errors. #SYMANTEC ENCRYPTION DESKTOP AMAZON LICENSE#
It arose from discussion and editing over beers by several engineers who have used AWS extensively.īefore using the guide, please read the license and disclaimer. It aims to be a useful, living reference that consolidates links, tips, gotchas, and best practices. This guide is by and for engineers who use AWS. The information in blogs or Stack Overflow is also not consistently up to date. AWS’s own documentation is a great but sprawling resource few have time to read fully, and it doesn’t include anything but official facts, so omits experiences of engineers. Nonetheless, trustworthy and practical information and recommendations aren’t easy to come by. Most people learn AWS by reading a blog or a “ getting started guide” and referring to the standard AWS references. Table: Storage Durability, Availability, and Price: A quantitative comparisonĪ lot of information on AWS is already written.Table: AWS Product Maturity and Releases: AWS product releases.
Table: Service Matrix: How AWS services compare to alternatives.Figure: AWS Data Transfer Costs: Visual overview of data transfer costs.Figure: Tools and Services Market Landscape: A selection of third-party companies/products.VPCs, Network Security, and Security Groups Credits ∙ Contributing guidelines Table of Contents
0 kommentar(er)
