Really excited to see what our customers and partners do with the new #AWS Cloud Control API, a consistent way to manage (CRUDL) resources based on the #CloudFormation Registry. aws.amazon.com/blogs/aws/anno…
A 🧵 for some more context :)
A 🧵 for some more context :)
When we launched the #CloudFormation Registry a couple of years ago, our vision was to reimagine how we solve service coverage in CloudFormation. We wanted to build it in a way that solves this use case for all AWS customers.
With Cloud Control API, everything that’s available in the Registry (including third party types!), are available with a consistent, simple interface. All resources get a uniform schema and interface, and builders can write once and leverage across all resources.
The nice thing about this approach is that as we continue to add new services and feature at AWS, Cloud Control API (and things leveraging it) stay up to date. You can discover all resources using the Registry, and then perform CRUDL operations using the new Cloud Control API!
Thank you to @hashicorp and @pulumi who worked with us. We’re also working with a number of developers and partners to help us shape the roadmap. If you’re interested, ping us!
We’re not done yet - we’re actively working to migrate resource types to the registry. We already have hundreds available, and every month you’ll continue to see progress. Give it a try and send us your feedback!
• • •
Missing some Tweet in this thread? You can try to
force a refresh
