32 ms·
> Features are available almost instantly If SAM relies on Cloud Formation, there must have been some serious changes at AWS. CF was/is notoriously lagging beh
by tilolebo 6y ago
> Features are available almost instantly
If SAM relies on Cloud Formation, there must have been some serious changes at AWS. CF was/is notoriously lagging behind AWS console and API in terms of feature coverage.
The Terraform AWS provider has always been much faster to reflect the AWS API changes.
- nowahe 6y agoNot especially true for all AWS Services, there has been some services that were only available on CF (Workspaces comes to mind). But in this case it wasn't Hashicorp fault, as what was available in CF wasn't in the AWS official API. It took something like a year for AWS to release the API
- irjustin 6y agoIn agreement with you, SAM's support in CF and CDK is solid. AWS really put all their ducks behind SAM. The place that suffers is ElasticBeanstalk. I used to be on EB but couldn't take it anymore. I kept having to run mini-templates from inside the beanstalk machines to get access to specific items that weren't exposed to CF directly. Once I moved to ECS/Fargate, it's worlds better support. ECS still has some parts that are laggy in the CDK (and you can still do it via JSON obj) but not in CF. It's been pretty good here in Fargate land.
- idunno246 6y agoIf I recall correctly, a couple years ago aws switched from one central team owning all of the cfn implementations to pushing it onto the service owner, so it’s no longer bottlenecked on a single teams queue. Given that the serverless teams are all invested in sam, it follows they’d make sure the things are implemented