https://docs.aws.amazon.com/amazonglacier/latest/dev/introdu...
----
Hello,
After careful consideration, we have decided to stop accepting new customers for Amazon Glacier (original standalone vault-based service) starting on December 15, 2025. There will be no change to the S3 Glacier storage classes as part of this plan.
Amazon Glacier is a standalone service with its own APIs, that stores data in vaults and is distinct from Amazon S3 and the S3 Glacier storage classes [1]. Your Amazon Glacier data will remain secure and accessible indefinitely. Amazon Glacier will remain fully operational for existing customers but will no longer be offered to new customers (or new accounts for existing customers) via APIs, SDKs, or the AWS Management Console. We will not build any new features or capabilities for this service.
You can continue using Amazon Glacier normally, and there is no requirement to migrate your data to the S3 Glacier storage classes.
Key Points: * No impact to your existing Amazon Glacier data or operations: Your data remains secure and accessible, and you can continue to add data to your Glacier Vaults. * No need to move data to S3 Glacier storage classes: your data can stay in Amazon Glacier in perpetuity for your long-term archival storage needs. * Optional enhancement path: if you want additional capabilities, S3 Glacier storage classes are available.
For customers seeking enhanced archival capabilities or lower costs, we recommend the S3 Glacier storage classes [1] because they deliver the highest performance, most retrieval flexibility, and lowest cost archive storage in the cloud. S3 Glacier storage classes provide a superior customer experience with S3 bucket-based APIs, full AWS Region availability, lower costs, and AWS service integration. You can choose from three optimized storage classes: S3 Glacier Instant Retrieval for immediate access, S3 Glacier Flexible Retrieval for backup and disaster recovery, and S3 Glacier Deep Archive for long-term compliance archives.
If you choose to migrate (optional), you can use our self-service AWS Guidance tool [2] to transfer data from Amazon Glacier vaults to the S3 Glacier storage classes.
If you have any questions about this change, please read our FAQs [3]. If you experience any issues, please reach out to us via AWS Support for help [4].
[1] https://aws.amazon.com/s3/storage-classes/glacier/ [2] https://aws.amazon.com/about-aws/whats-new/2021/04/new-aws-s... implementation-amazon-s3-glacier-re-freezer/ [3] https://aws.amazon.com/s3/faqs/#Storage_Classes [4] https://aws.amazon.com/support
Niche ? From who's perspective? Anyway if AWS are offering a service, why would you ever need to consider 'is this too niche for lts?'
https://docs.aws.amazon.com/AmazonS3/latest/userguide/amazon...
I wonder why they're going that direction too, if anything those lambdas must be making money for them.
Does not be accessible to new customers mean a new test account that rolls into the same parent org would no longer have access either?
I believe that they did alter the pricing at some point. Regardless, the move to just a storage class on S3 made everything much simpler.
So much promise as a Heroku alternative with all the AWS integrations but it's basically dead now. Not a peep from them on their public roadmap over at github.
We're having to go back to Fargate with all the operational overhead that entails.
If you ever get this working for Kubernetes, I'd love to add it to https://canine.sh for a one click deploy, been looking for something like this.
But there are others where a “service” is really a _feature_ of another existing product offering. But for handwave reasons it can be extremely difficult to implement that way, and a new API and service name etc make the development tractable. To throw a stone Cloudwatch org is an interesting example of this, where its both too broad and too narrow, leading to an umbrella of undersized feature/services.
We love you, but focus on the core infrastructure bits and stop chasing everything that moves! Your customers build better apps and services that you do… just build great building blocks and folks will be very happy.
I knew the service was rough, but had the right building blocks plus Cfn/CDK support and has been working well.
My lack of trust in AWS is increasing, feels like a google move.
bigwheels•3mo ago
yunwal•3mo ago