what

• SNS topic creation with according policy
• SNS topic monitoring with CloudWatch
• Linting modules that had failed check

why

• to utilize SNS

related

• https://github.com/cloudposse/terraform-aws-sns-topic/pull/1
• https://github.com/cloudposse/terraform-aws-sns-cloudwatch-sns-alarms/pull/1

what

• cache_registry_name adde to create ECR registry for caching

why

• might be useful for example for codefresh external cache registry

what

• ECR user added

why

• to allow to push/pull images using AWS credentials or token of this user

what

• module to create ECR repo for every github repo for given organization

why

• to automate creation of ECR repos

what

• Add SES module that creates domain identity, IAM user that can send emails and verification DNS records in Route53

why

• To send emails via SES with sentry

what

• unnecessary Security Group removed

why

• to avoid duplicate Security Group rule error

what

• RDS instance postgres added for Sentry backend

why

• Sentry requires backend DB

what

• Update terraform-aws-lambda-elasticsearch-cleanup version

why

• Added enabled and artifact_url variables to the module
• When the terraform-external-module-artifact module is used in this module with enabled variable set to false, terraform-external-module-artifact needs to be disabled as well (otherwise it throws errors that it can't download the artifact)
• Allow to override the artifact_url URL template

references

• https://github.com/cloudposse/terraform-aws-lambda-elasticsearch-cleanup/releases/tag/0.6.0
• https://github.com/cloudposse/terraform-external-module-artifact/releases/tag/0.3.0

what

• [elasticsearch] Bump terraform-aws-elasticsearch version

why

• When an output from a data source is used in counts, in some cases Terraform can't compute the counts throwing the errors (it's working in the Terratest, but does not work for some customers):

Error: Invalid count argument
 on .terraform/modules/search_service_elasticsearch_master.elasticsearch/main.tf line 76, in resource "aws_iam_service_linked_role" "default":
 76:   count            = var.enabled && var.create_iam_service_linked_role && length(data.aws_iam_role.default.*.id) == 0 ? 1 : 0
The "count" value depends on resource attributes that cannot be determined
until apply, so Terraform cannot predict how many instances will be created.
To work around this, use the -target argument to first apply only the
resources that the count depends on.

• We have a bool variable create_iam_service_linked_role to control that without using data sources. If the AWS account (where the module is provisioned) already has the AWSServiceRoleForAmazonElasticsearchService service role, set the variable create_iam_service_linked_role to false. On a new account, set it to true

references

• https://github.com/cloudposse/terraform-aws-elasticsearch/pull/52

[elasticsearch] Convert to TF 0.12 (#236)

what

• Add iam_role_arns variable to specify additional IAM roles to allow access to the Elasticsearch domain

why

• When Elasticsearch is accessed from applications running on a Kubernetes cluster, the applications are usually running by assuming an IAM role using kiam or EKS Service Account IAM Roles. We need to be able to give the application's role permissions to access the ES domain without forcing the application code to assume another IAM role

what

• [elasticsearch] list of subnet_ids is not sliced any more

why

• to avoid ValidationException: You must specify exactly three subnets because you’ve set zone count to three error.

what

• terraform-aws-elasticsearch version bump

why

• 0.3.4 was a broken release

what

• terraform-aws-elasticsearch version bump

why

• to support elasticsearch_subdomain_name variable

what

• elasticsearch_subdomain_name variable added

why

• to be able to override default value (var.name) with custom subdomain hostname

what

• create_iam_service_linked_role variables added to pass to elasticsearch module

why

• to be able to disable creating AWSServiceRoleForAmazonElasticsearchService. For example in case it is already there

What

• Added ability to override params for CIS instances

Why

• Allow specifying an account-specific values