Saurabh M.

@bernardobridge Thank you. I tried and still getting the same error where I opted in to change folder hierarchy so that the scenario I am trying to run isn't at...

@bernardobridge - Same error. My ideal use case is to separate multiple scenarios pointing to same config as config doesn't change. I am actually testing [Separating scenarios into separate files](https://github.com/artilleryio/artillery/tree/main/examples/multiple-scenario-specs)...

@jasonmimick-aws My stack is also stuck in progress endlessly. Is there a different image and port number we can use for initial deployment?

@rverton Container / Task is still taking unusually longer with below changes due to which stack continues to be In progress status. Is that how you are using a dummy...

Still no progress. Stack is stuck in progress and task stopped eventually const baseImage = 'public.ecr.aws/nginx/nginx-unprivileged' const container = taskDef.addContainer('nodejs-docker-example', { image: ecs.ContainerImage.fromRegistry(baseImage), memoryLimitMiB: 256, cpu: 256, logging }); container.addPortMappings({...

@rverton I believe you mean if subnet where cluster is created have access to Internet (IGW). I will check the routing and will verify. Could be related to [Auto-assign public...