0.4.2

Make SNS optional again (#15)

0.4.1 Fix index cleanup lambda failure due to AWS changes

#14 also closes #5 but see #12

0.4.0 Fix SNS

Note: this release made providing an SNS ARN required. It was made optional again in release 0.4.2

what

• Fix SNS
• Add permission for lambda function to publish to SNS

why

• Fix issue s #9 and #10
• Closes #9
• Closes #10

0.3.0: Use relative path name for lambda

Incompatible change (#8):

Previously we used the full path name for the lambda file. We now use the path name relative to the current working directory. This change will reduce unnecessary Terraform updates in the future, but will cause one when first applied.

0.2.0

Add enabled flag, fix IAM permissions (#6)

0.1.2

Allow outbound DNS requests from Lambda SG (#3)

So that we can resolve DNS for the ES cluster.

0.1.1

Add readme (#2)

0.1.0: Add ES cleanup module (#1)

* Add first cut of the ES cleanup module

* Add working example usage

This creates all the base resources necessary to test the
elasticsearch-cleanup module. Unfortunately this requires a two stage
apply as the `aws_route53_zone` resource fails to compute ID when
passed into other modules. See: https://github.com/cloudposse/terraform-aws-elasticsearch/issues/13

* Deploy Lambda artifact from S3 bucket

Pull the deployment artifact from S3 using the new
terraform-external-module-artifact module. This approach has the benefit
of not checking in zip files into git, but the downside of more preamble
when wanting to test this module as per the example docs. You need to
know that the function should already be in S3 at a pre determined path.

We need to think of proper deployment and promotion of these artifacts
through different S3 buckets e.g.
artifacts.testing.cloudposse.org -> artifacts.prod.cloudposse.org