Skip to content

Conversation

@alhusseinsamy
Copy link
Contributor

No description provided.

Copy link
Member

@karimatwa karimatwa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Motivation section to be added:
Adding 40 EIPs creates very long EC2 policy statements, exceeding the quota limit for policy sizes.
Error: creating IAM Policy (control-plane-ec2-policy): operation error IAM: CreatePolicy, https response error StatusCode: 409, RequestID: bb394652-2232-4c2b-978b-5b51f1d368ff, LimitExceeded: Cannot exceed quota for PolicySize: 6144

-> The implemented solution could potentially work on the short term if the EIP policy statements are below the quota size limit. Long term solution entails creating a unique policy per EIP.

@alhusseinsamy
Copy link
Contributor Author

Motivation section to be added: Adding 40 EIPs creates very long EC2 policy statements, exceeding the quota limit for policy sizes. Error: creating IAM Policy (control-plane-ec2-policy): operation error IAM: CreatePolicy, https response error StatusCode: 409, RequestID: bb394652-2232-4c2b-978b-5b51f1d368ff, LimitExceeded: Cannot exceed quota for PolicySize: 6144

-> The implemented solution could potentially work on the short term if the EIP policy statements are below the quota size limit. Long term solution entails creating a unique policy per EIP.

I modified the scripts in order to create one policy per chunk of 10 statements. I believe this can be a reasonable solution as the number of elastic IPs will typically be in the order of 10s.

@alhusseinsamy alhusseinsamy merged commit cc44155 into main Nov 5, 2025
1 check passed
@alhusseinsamy alhusseinsamy deleted the chore/tf-aws-separate-elastic-ips-in-iam-policy branch November 5, 2025 09:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants