Amazon unsettles developers: secret end for AWS CodeCommit and Cloud9
Stop for CodeCommit, Cloud9 and other Amazon Web Services. The operator blocks them for new users and discontinues further development.
(Image: iX mit Dall-E 3)
- Robert Lippert
Amazon has unsettled parts of its web services community with a fleeting announcement published on X (formerly Twitter). According to Jeff Barr, Chief Evangelist at Amazon, the company has decided to stop accepting new users for some of the services it offers with immediate effect.
This affects the services S3 Select, CloudSearch, Cloud9, SimpleDB, Forecast, Data Pipeline and CodeCommit. However, according to Barr, the company wants to support the migration to similar AWS or third-party solutions.
The announcement unsettled parts of the developer community, as there was no official statement from Amazon apart from Jeff Bar's tweet. The fact that only hints were given and users had to gather the information from news sites caused particular dissatisfaction.
Feature freeze for CodeCommit, user freeze for Cloud9
For CodeCommit, a source code repository service managed by Amazon, Amazon provides instructions for migrating to other Git providers, which have now been supplemented with further official information. According to this, CodeCommit has decided on a complete feature freeze and will only deliver security and availability updates until further notice. There is also a migration path for Cloud9, including information on the feature freeze and user freeze. This heralds the end of Amazon's cloud IDE, with which the company had found a way to tie users to an AWS account following the acquisition of Cloud9 in 2017.
In this context, observers are also keeping an eye on SimpleDB, a non-relational database service from Amazon, which is also mentioned by Barr. SimpleDB is one of the oldest AWS services, and there is a possibility that applications with little support are still using the service without keeping an eye on the components.
There is also the possibility that there are still templates for the multi-account management environment AWS Control Tower that have not yet been adapted to the new conditions and with which users can no longer set up AWS environments. It is advisable to thoroughly check the AWS setups again.
The community is helping itself
It remains to be seen what will happen now that the services mentioned have been stopped. Where Amazon itself does not provide migration paths or official information, the AWS community is helping itself in some cases, such as with the aws_breaking_changes repository, which contains information on other affected services.
(are)
