aws-fargate

Before opening, please confirm:

• I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
• I have searched for duplicate or closed issues.
• I have read the guide for [submitting bug reports](https://github.com/aws-amplify/amplify-cli/blob/master/CONTR

The --prod flag has been deprecated, so we should not show that field in the output of the env show command, or in our docs:

https://aws.github.io/copilot-cli/docs/concepts/environments/
https://aws.github.io/copilot-cli/docs/commands/env-show/

Description

If using an existing VPC rather than let this module create it, it now generates this error:

│ Error: "" is not a valid CIDR block: invalid CIDR address: 
│ 
│   with module.atlantis.module.efs_sg[0].module.sg.aws_security_group_rule.ingress_rules[0],
│   on .terraform/modules/atlantis.efs_sg/main.tf line 70, in resource "aws_security_group_rule" "ingress_rules":
│   70

At the moment the number of tasks able to be launched for a given scenario is 10 do to restriction with ECS. A workaround that creates multiple ECS instances for a given scenario based on the number of tasks requested should be added.

Errors are retried immediately and forever. Would be good to enter a truncated exponential backoff loop or similar. A full jitter algorithm is available and in use by the AWS client. We should make sure failed messages are retried after an interval derived from that.

https://github.com/Blissfully/sqs-lambda-bridge/blob/eba837a7b080092ed44706aa53125c33aa8da1be/src/aws.js#L4-L15