terraform-aws-elastic-beanstalk-environment
terraform-aws-elastic-beanstalk-environment copied to clipboard
Terraform module to provision an AWS Elastic Beanstalk Environment
hello people is there any possibility to manage ebextentions using terraform because my needs is : - create resources with names for the elastic load balancer and autoscaling group and...
Hello, I'm trying to add the RDS settings to my EB environments configuration, and it seems that functionality does not work at all. Based on your documentation & AWS: https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/command-options-general.html#command-options-general-rdsdbinstance...
## what Fixed creating environment for version 4.0.0 aws provider ## why With the recent aws provider version 4 upgrade, significant changes to s3 bucket resource were introduced. ## references...
Found a bug? Maybe our [Slack Community](https://slack.cloudposse.com) can help. [](https://slack.cloudposse.com) ## Describe the Bug When i deploy the project for the first time, it seems there is a race...
Currently we do not have solution stack attribute ignored. Beanstalk automatically updates environment due to managed actions being allowed, when we run terraform again, it downgrades it back to the...
## Describe the Feature The default EC2 instance profile give too many rights to deployed EC2 instance. It should not give any right at start. Currently, a newly deployed Beanstalk...
Found a bug? Maybe our [Slack Community](https://slack.cloudposse.com) can help. [](https://slack.cloudposse.com) ## Describe the Bug Various s3 bucket-related errors are thrown when trying to use this module (using the predefined...
The following change removed `ssh_source_restriction` https://github.com/cloudposse/terraform-aws-elastic-beanstalk-environment/commit/fe6d0d7242dff18928cc204fb3c693e104978b17#diff-7a370d8342e7203b805911c92454f0f4L494 but it is still present in the docs, and is also a variable that can be passed in, is this intentional? I have checked...
## what * Bring back the SSHSourceRestriction ## why * This got accidentally removed in a previous commit https://github.com/cloudposse/terraform-aws-elastic-beanstalk-environment/commit/fe6d0d7242dff18928cc204fb3c693e104978b17#diff-7a370d8342e7203b805911c92454f0f4L494 ## references * Open ticket: https://github.com/cloudposse/terraform-aws-elastic-beanstalk-environment/issues/123
## What * Allow the user of the module to specify an existing IAM Role name for the instance profile * This IAM role name will be used to create...