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.
This is a 🚀 Feature Request
Allow the
Roleused by theTaskcreated by the service to be specified in configurationUse Case
Allow for customization of the
Rolesuch 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
taskRolewould need to be defined on the configuration root.This is a 🚀 Feature Request