1. Proposed title of this feature request: External Cluster ID generated by Installer as AWS Tag 
2. What is the nature and description of the request?

This is regarding the ability to add OCP Cluster’s External ID as AWS Tag for all the cluster’s AWS infrastructure resources.  Is there a way to add the External Cluster ID to a ROSA Cluster?

Perhaps, Installer provide an ability to allow clients like Hive pass an OCP Cluster ID instead of always generating and use that to tag cloud resources. That way, for customers, there is always one cluster ID across OCM, Infrastructure Tag, and OCP Cluster. (BTW, Hosted Clusters using HyperShift already has the ability to set Cluster ID)

Or perhaps Hive automatically tags using the External ID after the successful cluster creation. This will be Day-2 instead of Day-1 proposed in above option. This can be folded into https://issues.redhat.com/browse/XCMSTRAT-157 but based on the conversations so far this is blocked by general lack of OCP support for adding/editing AWS Tags.   

3. Why does the customer need this? (List the business requirements here)

1. IBM has an high priority ask for this. This is because the OCP cluster’s audit log for nodes contain cluster’s External ID, requiring a complex two-step method to link External ID with the actual nodes that only have Infra ID as Tags. Both Infra ID and Cluster External IDs are generated by the OCP Installer. 
2. Beyond IBM, I have other customers mention/ask ask this as well because in the cases of ROSA clusters, there are three cluster-related IDs: OCM ID, External ID, and Infra ID. This requires customers to find Infra ID for their Cluster’s ID and use that to tag cloud resources.

4. List any affected packages or components.

Installer, Hive, Cluster Operators