Make it clear to attach IAM policies to ECS task-role

[t-kikuc]

What this PR does / why we need it:

Make it clear which role to attach IAM policies to because ECS's task-role and task-execution-role are confusing.

[khanhtc1202]

👍

[Warashi]

How about removing this line?

pipecd/docs/content/en/docs-dev/installation/install-piped/required-permissions.md

Line 49 in 7ca5c05

"arn:aws:iam::<account-id>:role/<task-execution-role>",

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 22.42%. Comparing base (7ca5c05) to head (7664807).

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #5035   +/-   ##
=======================================
  Coverage   22.42%   22.42%           
=======================================
  Files         522      522           
  Lines       56915    56915           
=======================================
  Hits        12766    12766           
  Misses      43123    43123           
  Partials     1026     1026           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[t-kikuc]

@Warashi

How about removing this line?

pipecd/docs/content/en/docs-dev/installation/install-piped/required-permissions.md

Line 49 in 7ca5c05

"arn:aws:iam::<account-id>:role/<task-execution-role>",

It’s mandatory.
When a piped creates a new task, the piped needs to pass task-execution-role to the task.

[Warashi]

It’s mandatory.
When a piped creates a new task, the piped needs to pass task-execution-role to the task.

Sorry, I misread.

As I understood, the Resource field at this line does not mean the role to which we add permission but the role we use to run the tasks.
So we need this line.

[Warashi]

LGTM