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.
If you are fine with running lots of apps on one beefy machine, the project I am building https://github.com/openrundev/openrun provides a similar abstraction as App Runner and Cloud Run (automatically deploy web apps from source). It supports scaling down to zero, but does not yet scale an app beyond one container.
Starting a new service was a path towards promotion at AWS, so they ended up launching 100s of services to the point where there were 10 different ways to do everything. I’m glad they’re culling them.
Amazon Glacier on the list is a pretty big surprise to me.
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
[deleted]
Read the header here for an explanation, it's not going away.
Same capability is now just a storage class in S3.
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?
Some of them also ended up getting consolidated into other larger services
Amazon S3 Object Lambda seems like a massive category to deprecate
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.
At least it’s not S3 triggers for lambdas, just about gave me a heart attack.
oh maybe thats what were using. Made it months ago and im not 100% sure. Lambda on putObject
That sounds like it might be a lambda trigger to me. The feature being deprecated is lambdas that operate at the s3 API level.
Yeah it's an Event Notification that triggers lambda that acts on the bucket, i had to give it permissions to the bucket so i guess it's outside it :). We'll see!
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?
It's the standalone Glacier service which I wasn't even aware existed - nothing changes for the s3 glacier storage class.
Amazon following the lead of Google Cloud of shutting down AWS services is not a good sign.
Where will the money and resources to develop AWS AI come from? Not from Incident Manager, that is for certain.
This is why you should never use niche aws services.
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.
If you are fine with running lots of apps on one beefy machine, the project I am building https://github.com/openrundev/openrun provides a similar abstraction as App Runner and Cloud Run (automatically deploy web apps from source). It supports scaling down to zero, but does not yet scale an app beyond one container.
Starting a new service was a path towards promotion at AWS, so they ended up launching 100s of services to the point where there were 10 different ways to do everything. I’m glad they’re culling them.
Amazon Glacier on the list is a pretty big surprise to me.
It was consolidated into S3 as a storage class: https://docs.aws.amazon.com/amazonglacier/latest/dev/introdu...
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
Read the header here for an explanation, it's not going away.
https://docs.aws.amazon.com/amazonglacier/latest/dev/introdu...
Same capability is now just a storage class in S3.
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?
Some of them also ended up getting consolidated into other larger services
Amazon S3 Object Lambda seems like a massive category to deprecate
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.
At least it’s not S3 triggers for lambdas, just about gave me a heart attack.
oh maybe thats what were using. Made it months ago and im not 100% sure. Lambda on putObject
That sounds like it might be a lambda trigger to me. The feature being deprecated is lambdas that operate at the s3 API level.
Yeah it's an Event Notification that triggers lambda that acts on the bucket, i had to give it permissions to the bucket so i guess it's outside it :). We'll see!
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?
It's the standalone Glacier service which I wasn't even aware existed - nothing changes for the s3 glacier storage class.
Amazon following the lead of Google Cloud of shutting down AWS services is not a good sign.
Where will the money and resources to develop AWS AI come from? Not from Incident Manager, that is for certain.
This is why you should never use niche aws services.