AWS CloudFormation Resource Import now supports CloudFormation Registry types
Resource Import now supports CloudFormation Registry types, so you can import resource types in the Registry, including non-AWS and private ones. Resource Import allows you to bring existing infrastructure and application resources into CloudFormation, regardless of how they were created or managed previously.
Resource Import now supports CloudFormation Registry types, so you can import resource types in the Registry, including non-AWS and private ones. Resource Import allows you to bring existing infrastructure and application resources into CloudFormation, regardless of how they were created or managed previously.
The CloudFormation Registry makes it easy to model and automate the management of AWS and third-party resources with the benefits of infrastructure-as-code. With this release, you can import resource types registered with the Registry into CloudFormation and leverage automation. This includes resource types by third-parties as well as private types. This release also adds support for 45 new Registry types in addition to the 50 originally supported types, including AWS Config Conformance Packs, Amazon CloudWatch Alarms, and Amazon ECS Clusters. Going forward, all new public Registry types will be automatically supported by Resource Import. This allows you to import public Registry resource provider types into CloudFormation as soon as they are available.
To get started, read our documentation where you will find tutorials and details on importing resources and refactoring stacks. For an up to date list of resource types supported by Resource Import, refer to the resource types section of the documentation.
For Resource Import region availability, refer to the AWS Region Table.