Paul SANTUS
Paul SANTUS
> In my case I had to switch from `terraform-aws-modules/vpc/aws` to `registry.terraform.io/terraform-aws-modules/vpc/aws`. > > * terraform 1.2.4 > * Intellij 2022.1.2 That tip was life-saving for me, thanks @lozuwa
@antonbabenko @bryantbiggs : would you consider reviewing my PR, if I submit one on this?
Being able to automatically have `--use-device-code` for `configure sso` and `sso login` would greatly benefit those working on remote shell sessions;
These are used only if create_iam_role and create_task_exec_iam_role are respectively set to false. Otherwise the module creates the role and won't take your arn into consideration.
Using root is not such a big issue if you stick to read-only file system
Could you do that on a new account? Now new accounts have default quotas lower than so called default quotas.
@AWS-Joe-A: adding a list of all the quotas request we need to make to get this deployment to work would be a satisfactory solution to this issue.
Issue was in one nested stack. I deployed in eu-west-1. I'll try again and will let you know
Hi @AWS-Joe-A I appreciate your commitment and efforts to replicate. I just deployed in my account again and got 2 errors in the Services stack ``` {"state":"TIMEOUT","reason":"Waiter has timed out"}...