serverless/examples

Lock Down Permissions

Open

#49 opened on Jan 5, 2017

View on GitHub
 (5 comments) (0 reactions) (0 assignees)JavaScript (11,176 stars) (4,496 forks)batch import
help wanted

Description

Currently, some of the examples have very open permissions.

Example: https://github.com/serverless/examples/blob/master/aws-node-fetch-file-and-store-in-s3/serverless.yml#L13-L17

For the sake of those less-than-knowledgeable with AWS permissioning, we should probably lock these instances down a bit more.

Contributor guide

Tech stack
awsnodejs
Domain
security
Issue type
security
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
basic AWS IAM knowledgeserverless framework
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Examine the referenced file aws node fetch file and store in s3/serverless.yml lines 13-17 to understand the current permissive IAM policy. Research AWS IAM policy syntax and the principle of least privilege. Propose a more restrictive policy that only grants the necessary actions (e.g., s3:PutObject) on the specific bucket. Review comments in the issue for any previous suggestions or concerns.