Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EnterpriseLogAccessIamRole can not be altered, eventually throwing limit exceeded errors. #620

Open
4 tasks done
Will-Bagley opened this issue Sep 17, 2021 · 2 comments
Open
4 tasks done
Labels
bug Something isn't working

Comments

@Will-Bagley
Copy link

Are you certain it's a bug?

  • Yes, it looks like a bug

Is the issue caused by a plugin?

  • It is not a plugin issue

Are you using the latest version?

  • Yes, I'm using the latest version

Is there an existing issue for this?

  • I have searched existing issues, it hasn't been reported yet

Issue description

I'm running into a problem while trying to deploy my current project where the "EnterpriseLogAccessIamRole" policy is exceeding the maximum limit of 10240 bytes. Given the size of the project, there are simply too many functions to fit within a single policy.
I tried to use this plugin: https://github.com/AntonBazhal/serverless-plugin-custom-roles but it doesn't appear to deal with my particular issue.

I reached out to serverless support and was told that there is indeed no way of altering the output of the EnterpriseLogAccessIamRole policy and that this was a current limitation of serverless. I have been made aware of a workaround (splitting the service into multiple smaller parts), but was urged to log this as an issue in hopes of a less drastic solution being considered.

Service configuration (serverless.yml) content

N/A

Command name and used flags

N/A

Command output

N/A

Environment information

Framework Core: 2.59.0 (local)
Plugin: 5.4.4
SDK: 4.3.0
Components: 3.17.0
@medikoo medikoo transferred this issue from serverless/serverless Sep 17, 2021
@medikoo medikoo added the bug Something isn't working label Sep 17, 2021
@medikoo
Copy link
Contributor

medikoo commented Sep 17, 2021

I assume that problematic part of the configured policy is here:

Resource: entries(ctx.sls.service.provider.compiledCloudFormationTemplate.Resources)
.filter(([, { Type }]) => Type === 'AWS::Logs::LogGroup')
.map(([logicalId]) => ({
'Fn::GetAtt': [logicalId, 'Arn'],

A quick fix that comes to my mind is to allow to override this policy, and then user may come up with some general catch-all rule that will cover all log groups in a given service

@amel-harrath
Copy link

any updates regarding this issue? I'm facing the exact same problem and splitting the service is not an option.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants