sbstjn/serverless-dynamodb-autoscaling

Create one scaling dedicated IAM role per project (not table)

Open

#31 opened on Oct 11, 2017

View on GitHub
 (10 comments) (2 reactions) (0 assignees)TypeScript (26 forks)github user discovery
help wanted

Repository metrics

Stars
 (148 stars)
PR merge metrics
 (PR metrics pending)

Description

Currently, project creates scaling role per table, which inconveniently increases resources count of CloudFormation stack, e.g. with larger number of tables it's more likely to reach 200 resources limit which is not shiftable.

As it's scalable targets that states which roles they're going to use, the ScalingRole can safely be configured as one global resource, it's also how it's exampled in AWS CloudFormation documentation

Contributor guide

Research direction
Review the current implementation in plugin.ts where the ScalingRole is created per table. Refactor to create one ScalingRole resource per project. Ensure that the role is attached to scalable targets appropriately.
Tech stack
typescript
Domain
backendcloud
Issue type
Refactor
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-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitTypeScriptServerless FrameworkAWS IAM
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60