aws/aws-cdk

(ecs-patterns): QueueProcessingFargateService - Allow task role to be specified

Open

#16,297 opened on Aug 31, 2021

View on GitHub
 (3 comments) (0 reactions) (0 assignees)TypeScript (3,530 forks)batch import
@aws-cdk/aws-ecs-patternseffort/smallfeature-requestgood first issuep2

Repository metrics

Stars
 (10,710 stars)
PR merge metrics
 (Avg merge 14d 11h) (68 merged PRs in 30d)

Description

Allow the Role used by the Task created by the service to be specified in configuration

Use Case

Allow for customization of the Role such as setting the role name.

Proposed Solution

I'm torn here. What is really needed is come consistency between the ECS patterns when it comes to configuration. ApplicationLoadBalancedFargateService provides an imageOptions configuration property that contains an optional Role property. QueueProcessingFargateService only has an image property, so it would appear that taskRole would need to be defined on the configuration root.

  • :wave: I may be able to implement this feature request
  • :warning: This feature might incur a breaking change

This is a :rocket: Feature Request

Contributor guide

Research direction
Investigate the ApplicationLoadBalancedFargateService pattern to understand how it handles role customization and apply a similar approach to QueueProcessingFargateService.
Tech stack
typescript
Domain
cloud
Issue type
Feature
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.
Half day
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
GitAWS CDK
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40