#terraform-aws-modules - June 2020

Hi all. Wondering if it’s “just me” or if others are seeing any changes in AWS beanstalk workings over the last week? We were running older version of cloudposse beanstalk environment (0.13.0) and all of a sudden started seeing the following errors (no changes on our end):

Failed Environment update activity. Reason: Configuration validation exception: Invalid option value: ‘0.0’ (Namespace: ‘aws:autoscaling:updatepolicy:rollingupdate’, OptionName: ‘MinInstancesInService’): You can’t enable rolling updates for a single-instance environment.

I’ve since upgraded our environment and app cloudposse modules to 0.22.0 as I saw a number of changes around the configuration thinking that may be it. But seeing the same thing now, at least this time at deploy time:

Error: ConfigurationValidationException: Configuration validation exception: Invalid option value: ‘0.0’ (Namespace: ‘aws:autoscaling:updatepolicy:rollingupdate’, OptionName: ‘MinInstancesInService’): You can’t enable rolling updates for a single-instance environment.

status code: 400, request id: c0ee72fe-414f-4d4e-b3e3-d40e5f7867a3

I see that the error is clear enough, but quite baffled why it just started all of a sudden. I’ve opened a ticket with AWS on Friday, still no response there - but maybe someone here has an idea?

Regarding https://github.com/cloudposse/terraform-aws-ecs-alb-service-task

i just had a quick question about that. why is icmp ingress enabled on the security group resource ?

I’ve added some important features into https://github.com/cloudposse/terraform-aws-codebuild .
Can some please review the changes in https://github.com/cloudposse/terraform-aws-codebuild/pull/53 so that these important features are merged asap.

Added support for :
• private repository auth
• git_submodules_config
• vpc_config
• logs_config
• git_clone_depth
• source_version
• Solved : #54
• Added force_detach_policies = true into resource “aws_iam_role” “default”
• Solved: #48
• solve issue #48 mandatory namespace and stage
• added secret manager access
• Solved: #56 Support of Other AWS CodeBuild Containers
• Example: Bitbucket

Review please for repo cloudposse/terraform-aws-ecs-alb-service-task

• https://github.com/cloudposse/terraform-aws-ecs-alb-service-task/pull/55
• https://github.com/cloudposse/terraform-aws-ecs-alb-service-task/pull/56

Review please https://github.com/cloudposse/terraform-aws-ecs-container-definition/pull/76

While using this terraform git https://github.com/cloudposse/terraform-aws-eks-node-group/blob/master/README.md
Can we have existing iam roles to be attached in node groups?
Because autoscaling describe policies are not attached in the newly created iam role.
These policies are need to be attached in node iam role to have autoscaling to work.

hi does any one have msk module that I can use .. I did not see one in the cloudpose repo .. any help would be greatly appreciated ... I wanted to build one with all the options parameterized but if I have something readily available that would make my life lot easier .. thanks in advance

Hey, question about the cloudposse module for ec2 instance group. Is this the place to ask a question about the modules from cloudposse here?

Cloudposse provides the modules like this:
https://github.com/cloudposse/terraform-aws-multi-az-subnets
Creates a subnet with multi AZ setup, real nice. However the https://github.com/cloudposse/terraform-aws-ec2-instance-group module only takes in 1 value in an instance group instead of taking the subnets from the AZ zone setup into account. Should i clone the repo to build in this functionality, build a wrapper module around it... Or is there a way to achieve this directly? I tried to pass multi values to this module, but not really that comfortable with terraform 0.12 syntax yet.

Cognito supports the addition of custom attributes in an existing user pool. However, when the changes are made through terraform, the old user pool is destroyed and a new one is created. Based on terraform documentation, this should not happen if the constraints block is used for the custom attributes (https://www.terraform.io/docs/providers/aws/r/cognito_user_pool.html). Did anyone faced similar issue and were able to fix it ... any help would be appreciated