包阅导读总结
1. 关键词：AWS、服务停用、社区担忧、沟通不足、策略变化
2. 总结：AWS 在短时间内停用了多项服务，包括 CodeCommit 等，引发社区担忧。虽提供了替代方案文档，但起初沟通不清晰，致用户不确定。AWS 副总裁确认停用部分服务，各方对此看法不一。
3. 主要内容：
– AWS 短时间内首次停用多项管理服务，如 CodeCommit、Cloud9、Forecast 等。
– 社区因缺乏清晰沟通产生担忧，AWS 开始发布技术文章介绍替代方案，但未先明确服务已停用。
– 这些服务的停用未在公告页面和推送中显示，与其他提供商做法不同。
– AWS 副总裁 Jeff Barr 确认部分服务停用新访问，现有功能不变，支持迁移到其他方案。
– 各方对 AWS 此举看法不同，有人认为是策略变化，有人认为不是。相关文章补充了服务迁移的说明。
思维导图：
文章来源：infoq.com
作者：Renato Losio
发布时间：2024/8/2 0:00
语言：英文
总字数：538字
预计阅读时间：3分钟
评分：86分
标签：AWS,云服务,服务停止,社区担忧,技术迁移
以下为原文内容
本内容来源于用户推荐转载，旨在分享知识与观点，如有侵权请联系删除 联系邮箱 media@ilingban.com
For the first time in its history, AWS has discontinued several managed services within a matter of days. Among the affected services are the source control AWS CodeCommit, the cloud-based IDE AWS Cloud9, and the time-series forecasting service Amazon Forecast. The wave of deprecations has led to concerns within the community due to the lack of clear communication.
After deprecating the ledger database Amazon QLDB, as separately reported on InfoQ, AWS began posting articles to document how to replace CodeCommit with other Git providers, CloudSearch with OpenSearch, and Cloud9 with AWS IDE Toolkits. While the technical articles provided useful information, they did not initially clarify whether the existing services had been discontinued, leaving the community in a state of uncertainty.
None of the retirements— S3 Select, CloudSearch, Cloud9, SimpleDB, Forecast, Data Pipeline, and CodeCommit— appeared on the announcement page and feeds, a practice that other providers usually follow. While existing customers might have received emails clarifying the status of the affected services, others were left wondering if the services were still supported or if AWS was changing its philosophy. To clarify the status of the affected services—a small percentage of the over 200 available—Jeff Barr, vice president and chief evangelist at AWS, confirmed:
After giving it a lot of thought, we made the decision to discontinue new access to a small number of services, including AWS CodeCommit. While we are no longer onboarding new customers to these services, there are no plans to change the features or experience you get today, including keeping them secure and reliable. We also support migrations to other AWS or third-party solutions better aligned with your evolving needs. Keep the feedback coming. We’re always listening.
Matthew Juliana, senior manager at Rackspace Technology, highlights how Barr’s message significantly differs from the “retiring services isn’t something we do at AWS” statement that Werner Vogels, CTO at Amazon, wrote just over a year ago. SimpleDB, a service superseded by DynamoDB over a decade ago, has often been used as an example of AWS not killing services like other providers do. In the article “The end of the Everything Cloud”, Forrest Brazeal comments:
This is not an indication that AWS is turning into GCP, who has inherited from broader Google a deserved reputation for pulling the rug out from under users by killing services with wide adoption (…) These services have been in maintenance-only mode for some time.
Andrew Brown, CEO of ExamPro, writes:
Whether this is a marketing blunder or not to me the idea of AWS cleaning up their catalog and killing off zombie AWS Services and Products is a good idea.
After suggesting that AWS should provide a deprecation page, Scott Piper, cloud security consultant, now maintains a list on GitHub of the services that have been deprecated. Piperwrites:
I’d also like to hear the strategy moving forward around this in terms of whether this is a one-time event, or if we should expect more batches of deprecations (…) how should one be evaluating services now that a change in strategy has happened at AWS?
Since the original posts, various deprecation notes have been added to the articles documenting the migrations from the affected services, clarifying the status of each one.
