Issue type

• Bug Report

Build number

master branch

Configuration

Deployed as a Stack Set, with a CloudWatch Rule triggering the function

Summary

Can't confirm completely, but I believe the logger which is created from main.go 's setupLogging function does not get created, and therefore

I'm submitting a...

• bug report
• feature request
• support request - read the FAQ first!
• kudos, thank you, warm fuzzy

What is the current behavior?

When I apply the EKS Spot Instance [example](https://github.com/terraform-aws-modules/terraform-aws-eks/tree/master/examples/spot_

Metasploit install script not working with example as user is not root which makes this a single user install according to https://rvm.io/rvm/install this would mean you need to add
echo "source $HOME/.rvm/scripts/rvm" >> ~/.bash_profile
for it to source properly and re-source the bash profile or run the bash script as root.

This fails the install with

module.http_c2.azurerm_virtua

The docs for DB identifier say:

The name of the RDS instance, if omitted, Terraform will assign a random, unique identifier

Unfortunately for me, it doesn't work:

The argument "identifier" is required, but no definition was found.

Moreover, there is nothing said about the restrictions on the identifier format: it can't be anything but alphanumeric due apparently to AWS API limitati

Hi, I don't see anything in the examples or documentation that would allow us to add rules to an existing security group by using the existing group as a parameter.

Is this possible with this module?

https://github.com/terraform-aws-modules/terraform-aws-atlantis/blob/508eb0c3bb99a84dfe9fdbe57f1989be711f4197/main.tf#L186

When I tried to use atlantis plan or apply I found that it needed permissions for at least for (depending on the config files of course):

• • access to the backend (say S3)
• • access to IAM
    among others.

Initially I began by attaching existing policies, before I

Found a bug? Maybe our Slack Community can help.

Describe the Bug

The module docs should explain how to cleanup.

Expected Behavior

The module docs would say something like (I'm still confirming the details but I just don't want to loose this issue report

please include a example to use a log_configuration, I wasn't able to figure out how pass to module

AWS provider v1.45. has support for the new mixed type/payment autoscaling groups that was just announced

• Terraform
• AWS Annoucement

If I get time I may work on a PR

According to S3 CORS configuration Amazon documentation there is a bug in configuration of allowed origins.

Example from documentation shows that each CORS rule need to consist only one AllowedOrigin parameter:

<CORSConfiguration>
 <CORSRule>
   <AllowedOrigin>http://www.example1.com</AllowedOrigin>

   <AllowedMethod>PUT</A

chart-repo.tf sets cluster_name = "${var.region}.${var.zone_name}" however when deploying kops module there is the ability to set cluster_name_prefix which overrides the default region name.

Other modules in the root-module set cluster_name the same way. Does it make sense to move the cluster_name_prefix logic to aws/kops-aws-platform or use some other ENV?

It's not made clear that private nodes make image pulling more complicated, so this should be better documented. See #25.

The current Serverless example for PostgreSQL does not work. It is using Parameter Group aurora5.6 which is for Serverless MySQL 5.6. Instead, it should be using aurora-postgresql10 for PostgreSQL which can be found in AWS Aurora Serverless Documentation

I will be creating a PR and as

The module currently does not support cognito_options config block.
See https://www.terraform.io/docs/providers/aws/r/elasticsearch_domain.html for details.

It would be good to have this feature supported.

Any of the action variables should default to [""] otherwise even if you set alb_groupd_alarms_enabled = false you will get errors about empty list of strings:

https://github.com/cloudposse/terraform-aws-ecs-web-app/blob/9d868399eaf3f7b1326ef9cda4fee505f9a292d3/variables.tf#L307-L407

Sorry don't have time right now to fix, test and pr.

The IAM policy for the role allows * too too many aws services without resource restrictions. Allowing a var supplied policy here could be a good first step. (https://github.com/cloudposse/terraform-aws-ecs-codepipeline/blame/master/main.tf#L66-L87).