If we attempt to apply a plan for shared workspace with IAM groups to an AWS account that already has a deployed template, we'll encounter an error stating that the group with that name already exists.
Typically, this isn't an issue since we use one project for each AWS account. However, there can be exceptions. For instance, if we deploy various staging projects on the company's AWS account, they may conflict.
Why
If we attempt to apply a plan for shared workspace with IAM groups to an AWS account that already has a deployed template, we'll encounter an error stating that the group with that name already exists.
Typically, this isn't an issue since we use one project for each AWS account. However, there can be exceptions. For instance, if we deploy various staging projects on the company's AWS account, they may conflict.
Acceptance Criteria