Skip to content

Commit e0d375b

Browse files
authored
docs(pipelines): describe how to work around policy size errors (#20569)
Fixes #20565. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
1 parent 0368374 commit e0d375b

File tree

1 file changed

+16
-0
lines changed

1 file changed

+16
-0
lines changed

packages/@aws-cdk/pipelines/README.md

+16
Original file line numberDiff line numberDiff line change
@@ -1379,6 +1379,22 @@ After turning on `privilegedMode: true`, you will need to do a one-time manual c
13791379
pipeline to get it going again (as with a broken 'synth' the pipeline will not be able to self
13801380
update to the right state).
13811381

1382+
### IAM policies: Cannot exceed quota for PoliciesPerRole / Maximum policy size exceeded
1383+
1384+
This happens as a result of having a lot of targets in the Pipeline: the IAM policies that
1385+
get generated enumerate all required roles and grow too large.
1386+
1387+
Make sure you are on version `2.26.0` or higher, and that your `cdk.json` contains the
1388+
following:
1389+
1390+
```json
1391+
{
1392+
"context": {
1393+
"@aws-cdk/aws-iam:minimizePolicies": true
1394+
}
1395+
}
1396+
```
1397+
13821398
### S3 error: Access Denied
13831399

13841400
An "S3 Access Denied" error can have two causes:

0 commit comments

Comments
 (0)