EXPANDR-3582 Resolving AWS-IAM bug

[capanw]

Contributing to Cortex XSOAR Content

Make sure to register your contribution by filling the contribution registration form

The Pull Request will be reviewed only after the contribution registration form is filled.

Status

• In Progress
• Ready
• In Hold - (Reason for hold)

Related Issues

fixes: link to the issue

Description

Removing IAM related tasks from the AWS enrichment and remediation as we don't want to list out all the users present in the AWS account.

Screenshots

Paste here any images that will help the reviewer

Minimum version of Cortex XSOAR

• 6.0.0
• 6.1.0
• 6.2.0
• 6.5.0

Does it break backward compatibility?

• Yes
  • Further details:
• No

Must have

• Tests
• Documentation

[content-bot]

Thank you for your contribution. Your generosity and caring are unrivaled! Make sure to register your contribution by filling the Contribution Registration form, so our content wizard @samuelFain will know the proposed changes are ready to be reviewed.

[capanw]

For reference: Old GCP PR: #22877. The reason why we are removing the IAM AWS tasks is, they are not able to enrich the security group owners. Only the AWS account ID is being returned associated with the security group. Any security group regardless of who created it, will always have the same aws account ID and this doesn't really help to enrich the exact owner of security group.

[samuelFain]

Hi @capanw, your PR will be reviewed shortly.
In the meanwhile, feel free to contact me for any questions/clarifications.
Thank you!

[content-bot]

For the Reviewer: Successfully created a pipeline in Gitlab with url: https://code.pan.run/xsoar/content/-/pipelines/5166160

[samuelFain]

Hi @capanw, since your PR mostly contain changes to playbooks, it will be also reviewed by a member of our security team.
Also, I noticed your forked repo is named chait-content instead of the recommended content, this is causing problems with the build process (you can see it for yourself here).
Could you please manually rename the repo using the following manual?
https://docs.github.com/en/repositories/creating-and-managing-repositories/renaming-a-repository

[efelmandar]

I reviewed the changes and PR is approved @samuelFain

waiting for shmuel

[capanw]

Hello @samuelFain, Thanks for pointing it out. I updated the name of my forked repo.