[HN Gopher] AWS Service Availability Updates
       ___________________________________________________________________
        
       AWS Service Availability Updates
        
       Author : dabinat
       Score  : 44 points
       Date   : 2025-10-13 19:52 UTC (3 hours ago)
        
 (HTM) web link (aws.amazon.com)
 (TXT) w3m dump (aws.amazon.com)
        
       | bigwheels wrote:
       | Is the implication these services are used so little it isn't
       | worth AWS continuing to invest in developing or maintaining
       | beyond bare-minimum KTLO ops?
        
       | ayende wrote:
       | Amazon Glacier on the list is a pretty big surprise to me.
        
         | bpicolo wrote:
         | It was consolidated into S3 as a storage class:
         | https://docs.aws.amazon.com/amazonglacier/latest/dev/introdu...
        
         | count wrote:
         | Same capability is now just a storage class in S3.
        
         | Niksko wrote:
         | If you click the Glacier link, it seems like it's some sort of
         | standalone service and API that's very old. The page says to
         | use S3's Glacier storage tier instead, so no change for the
         | majority of folks that are likely using it this way
        
         | whydid wrote:
         | Read the header here for an explanation, it's not going away.
         | 
         | https://docs.aws.amazon.com/amazonglacier/latest/dev/introdu...
        
       | umurkontaci wrote:
       | Amazon following the lead of Google Cloud of shutting down AWS
       | services is not a good sign.
        
         | rilindo wrote:
         | Where will the money and resources to develop AWS AI come from?
         | Not from Incident Manager, that is for certain.
        
       | joelthelion wrote:
       | This is why you should never use niche aws services.
        
       | havefunbesafe wrote:
       | Amazon S3 Object Lambda seems like a massive category to
       | deprecate
        
         | honopu wrote:
         | Yeah I agree. We're currently using it to dump images as
         | originals into a bucket at a path.. then the aws lambda
         | function attached generates all the thumbnails.
        
         | easton wrote:
         | At least it's not S3 triggers for lambdas, just about gave me a
         | heart attack.
        
           | honopu wrote:
           | oh maybe thats what were using. Made it months ago and im not
           | 100% sure. Lambda on putObject
        
             | JohnMakin wrote:
             | That sounds like it might be a lambda trigger to me. The
             | feature being deprecated is lambdas that operate at the s3
             | API level.
        
       | koolba wrote:
       | Wow. I can't believe Glacier is on that list.
       | 
       | 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?
        
         | jeffnappi wrote:
         | It's the standalone Glacier service which I wasn't even aware
         | existed - nothing changes for the s3 glacier storage class.
        
       | freshnode wrote:
       | They should get real and include App Runner on this list.
       | 
       | 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.
        
       ___________________________________________________________________
       (page generated 2025-10-13 23:01 UTC)