Skip to content

iambic setup does not pre-flight whether there were conflicting IambicSpokeRole during AWS setup #505

@smoy

Description

@smoy

Describe the bug
iambic setup can fail to complete for AWS setup if there are conflicting IambicHubRole or IambicSpokeRole because AWS IAM Role name within an account must be unique.

The conflict typically comes from a previous failed iambic setup. Because there are not iambic uninstall, the operator has to manually clean up any conflicting AWS IAM Role.

To Reproduce

  1. Create a AWS IAM Role name IambicSpokeRole or IambicHubRole in the mgmt account.
  2. Run iambic setup
  3. It will fail to create Stack either on mgmt account or any of the org member account.
  4. See error

Expected behavior

  1. iambic setup either preflight if there are any conflicting IAM role before attempting to create the stack.
  2. iambic cleanup that can remove any conflicting resources for the AWS setup.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • OS: [e.g. iOS]
  • Browser [e.g. chrome, safari]
  • Version [e.g. 22]

Additional context
Add any other context about the problem here.

Community Engagement
Your vote counts! Please support this bug report by adding a 👍 reaction to the original issue, which will aid the community and maintainers in addressing this problem.

Please refrain from adding "+1" or "me too" comments, as these create unnecessary noise for issue followers and do not help in prioritizing the issue. If you wish to contribute to solving this issue or have submitted a pull request, please leave a comment.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions