We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I think the backup role: EBSBackupLambdaRole created here: https://github.com/Accenture/adop-aws/blob/master/layer5-ebs-backups/ebs-backup-lambda-function.yaml#L28
Probably doesn't need full lambda access. Especially for people using lambda for more than backups.
https://docs.aws.amazon.com/lambda/latest/dg/access-control-identity-based.html
The text was updated successfully, but these errors were encountered:
Added policy for EBSBackupLambdaRole
ff26ed6
Removed the lambda full access managed role , created role name ebs-backup-lambda-role and attached the polucy to "fix Accenture#5"
No branches or pull requests
I think the backup role: EBSBackupLambdaRole created here:
https://github.com/Accenture/adop-aws/blob/master/layer5-ebs-backups/ebs-backup-lambda-function.yaml#L28
Probably doesn't need full lambda access. Especially for people using lambda for more than backups.
https://docs.aws.amazon.com/lambda/latest/dg/access-control-identity-based.html
The text was updated successfully, but these errors were encountered: