Cloudformation-coverage-roadmap: Import Operation Resource Type Coverage

[lukbes]

Tracking expansion of resource type coverage for import operations:

create-change-set --resources-to-import

Resources types that currently Support Import Operations

[PatMyron]

https://github.com/aws-cloudformation/aws-cloudformation-coverage-roadmap/issues/303

---

Stateful resource types should be prioritized for import operations:
AWS::Backup::BackupVault
AWS::DocDB::DBCluster
AWS::DocDB::DBInstance
AWS::EFS::FileSystem
AWS::EMR::Cluster
AWS::ElastiCache::CacheCluster
AWS::ElastiCache::ReplicationGroup
AWS::Elasticsearch::Domain
AWS::FSx::FileSystem
AWS::Neptune::DBCluster
AWS::Neptune::DBInstance
AWS::QLDB::Ledger
AWS::Redshift::Cluster
AWS::SDB::Domain
etc.

[reiddhughes]

Import is such a hugely amazing feature for evolving Stacks: definitely want to see more of it.
We would really love to see AWS::EKS::Cluster specifically.

[PatMyron]

Resource Import now supports CloudFormation Registry types

[benbridts]

@PatMyron which process is being used to determine which resources should be migrated, and in which order? Closing the other issues keeps the discussion in one place, but how are customers supposed to indicate which resources they need import on most?

(the stateful comment above is a good first indicator, but there might be more customers impacted by eg. EFS than by ElastiCache - and even stateless resources might have a performance impact on an application when migrating)

[seittema]

Any indication when AWS::Elasticsearch::Domain will support Import Operations? We have been wanting to get our ES cluster under CFT support for a year now, but appears it's still not supported.