Update aws-privilege-escalation.json

[SeaBlooms]

Added additional single service rules from Hacking the Cloud.

QA Checklist

Alerts Rule Packs

• IF THIS CONTENT NEEDS TO BE RELEASED - is the package version in the package.json bumped?
• Does a related alert already exist, and should it be tweaked or added to instead?
• Test each query to make sure it works
• Look for hardcoded variables/parameter values in the query
• Consider Severity for Alerts
• Spellcheck
• Use all caps for J1QL keywords and relationship classes
• Upload the alerts rule pack JSON into JupiterOne to validate

[mikiodehartj1]

We should add in the description why* each may be an issue.

L. 256 is a great example: "Users with the lambda:UpdateFunctionConfiguration permission can modify an existing Lambda function's configuration to add a new Lambda layer, allowing the user to override an existing library and allow them to execute malicious code under the privilege of the role associated with the Lambda function."

This explains the importance of each rule.

Otherwise looks good.