User Story

When I try to build a ROSA (classic and HCP) or OSD cluster, anywhere that I'm provided an error caused by lack of AWS service quota, the error should include the AWS quota code that I can use to search for and fix the quota issue. Without the code it is difficult to know which one I need to adjust.
As an example, currently, I get an error indicating that I lack the vCPU quota, but there is no such named quota in AWS service quotas.... it is actually the on-demand general instance types, measured in vCPU cores, that requires adjusting, but having the quota code to search for it would be so much better.

Acceptance Criteria

• Customers can receive more useful quota information related to AWS service quotas that might get in the way of creating clusters.

Default Done Criteria

• All existing/affected SOPs have been updated.
• New SOPs have been written.
• Internal training has been developed and delivered.
• The feature has both unit and end to end tests passing in all test
  pipelines and through upgrades.
• If the feature requires QE involvement, QE has signed off.
• The feature exposes metrics necessary to manage it (VALET/RED).
• The feature has had a security review.* Contract impact assessment.
• Service Definition is updated if needed.* Documentation is complete.
• Product Manager signed off on staging/beta implementation.

Dates

Integration Testing:
Beta:
GA:

Current Status

GREEN | YELLOW | RED
GREEN = On track, minimal risk to target date.
YELLOW = Moderate risk to target date.
RED = High risk to target date, or blocked and need to highlight potential
risk to stakeholders.

References

Links to Gdocs, github, and any other relevant information about this epic.