v4.10.0

feat: Add filter_prefix, filter_suffix config options for queues and topics @vonZeppelin (#261)

## what

• Adds missing filter_prefix and filter_suffix options in event notifications config for queues and topics.
• set lambda list filter arguments to optional

Signed-off-by: Leonid Bogdanov [email protected]

references

• Closes #260
• https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3_bucket_notification#lambda_function

v4.9.0

feat: add s3 request payment config @nitrocode (#259)

## what

• add s3 request payment config

why

• make requester pay

references

• closes #156
• https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3_bucket_request_payment_configuration
• https://docs.aws.amazon.com/AmazonS3/latest/userguide/RequesterPaysBuckets.html

v4.8.0

feat: support eventbridge bucket notification @nitrocode (#255)

## what

• support eventbridge bucket notification

why

• Emit s3 events to eventbridge

references

• Closes #254

v4.7.3

🚀 Enhancements

fix: use new destination.bucket key in policy @nitrocode (#256)

## what

• use new destination.bucket key in policy

why

• Support both deprecated destination_bucket and new destination.bucket
• Previous changes created destination.bucket and left destination_bucket for backwards compatibility, as stated in variables.tf, and forgot to include the new value in the IAM policy

references

• Closes #215

🐛 Bug Fixes

fix: use new destination.bucket key in policy @nitrocode (#256)

## what

• use new destination.bucket key in policy

why

• Support both deprecated destination_bucket and new destination.bucket
• Previous changes created destination.bucket and left destination_bucket for backwards compatibility, as stated in variables.tf, and forgot to include the new value in the IAM policy

references

• Closes #215

v4.7.2

🚀 Enhancements

fix: correct bucket name to fix broken `-replication` role @amila-ku (#250)

## what

• Fixes replication IAM role name that gets created as '-replication'

why

• Replication IAM role name gets created as '-replication'. This made the replication role unsusable.
• Used Terraform version: 1.8.0

references

• Resolves #251

v4.7.1

🚀 Enhancements

fix: s3 lambda event notification assignments @mpajuelofernandez (#253)

## what

It seems there is a typo kind if error here

dynamic "lambda_function" {
    for_each = var.event_notification_details.lambda_list
    content {
      lambda_function_arn = lambda_function.value.arn
      events              = lambda.value.events
      filter_prefix       = lambda_function.value.filter_prefix
      filter_suffix       = lambda_function.value.filter_suffix
    }
  }

I think it should be

dynamic "lambda_function" {
    for_each = var.event_notification_details.lambda_list
    content {
      lambda_function_arn = lambda_function.value.arn
      events              = lambda_function.value.events
      filter_prefix       = lambda_function.value.filter_prefix
      filter_suffix       = lambda_function.value.filter_suffix
    }
  }

why

The S3 notification can not be created unless this is fixed

references

This should fix #252

🐛 Bug Fixes

fix: s3 lambda event notification assignments @mpajuelofernandez (#253)

## what

It seems there is a typo kind if error here

dynamic "lambda_function" {
    for_each = var.event_notification_details.lambda_list
    content {
      lambda_function_arn = lambda_function.value.arn
      events              = lambda.value.events
      filter_prefix       = lambda_function.value.filter_prefix
      filter_suffix       = lambda_function.value.filter_suffix
    }
  }

I think it should be

dynamic "lambda_function" {
    for_each = var.event_notification_details.lambda_list
    content {
      lambda_function_arn = lambda_function.value.arn
      events              = lambda_function.value.events
      filter_prefix       = lambda_function.value.filter_prefix
      filter_suffix       = lambda_function.value.filter_suffix
    }
  }

why

The S3 notification can not be created unless this is fixed

references

This should fix #252

🤖 Automatic Updates

Update terratest to '>= 0.46.0' @osterman (#235)

## what - Update terratest `>= 0.46.0`

why

• Support OpenTofu for testing

References

• https://github.com/gruntwork-io/terratest/releases/tag/v0.46.0
• DEV-374 Add opentofu to all our Terragrunt Testing GHA matrix

Migrate new test account @osterman (#248)

## what - Update `.github/settings.yml` - Update `.github/chatops.yml` files

why

• Re-apply .github/settings.yml from org level to get terratest environment
• Migrate to new test account

References

• DEV-388 Automate clean up of test account in new organization
• DEV-387 Update terratest to work on a shared workflow instead of a dispatch action
• DEV-386 Update terratest to use new testing account with GitHub OIDC

Update .github/settings.yml @osterman (#247)

## what - Update `.github/settings.yml` - Drop `.github/auto-release.yml` files

why

• Re-apply .github/settings.yml from org level
• Use organization level auto-release settings

references

• DEV-1242 Add protected tags with Repository Rulesets on GitHub

Update .github/settings.yml @osterman (#246)

## what - Update `.github/settings.yml` - Drop `.github/auto-release.yml` files

why

• Re-apply .github/settings.yml from org level
• Use organization level auto-release settings

references

• DEV-1242 Add protected tags with Repository Rulesets on GitHub

v4.7.0

Make sure replica_kms_key_id is truly empty @stephan242 (#244)

references

closes #243

v4.6.0

Addition of S3 bucket event notification resource and Addition of S3 directory optional resource @mayank0202 (#240)

Issue - GH-239

what

This feature will make s3 event notifications which will have 3 options to trigger lambda or queue or topic so we can define a resource from this documentation.
aws_s3_bucket_notification

we also added s3 directory bucket which is a new feature in aws so addition of optional resource can be done if someone needs to use that with the help of terraform
aws_s3_directory_bucket

why

• Enhanced Event-Driven Architecture: The introduction of S3 event notifications allows the S3 bucket to trigger Lambda functions, SQS queues, or SNS topics. This facilitates seamless integration with other AWS services and enables real-time processing of data, which is crucial for building event-driven architectures.

• New AWS Feature Adoption: The addition of the aws_s3_directory_bucket resource reflects the latest AWS capabilities, ensuring that our infrastructure is up-to-date with current AWS offerings. This optional resource allows users to leverage new AWS features as they become available, promoting flexibility and future-proofing our Terraform configurations.

• Improved Flexibility: By providing options to trigger different AWS services (Lambda, SQS, SNS), the solution becomes more versatile, catering to a wide range of use cases and workflows. This flexibility can lead to more efficient and effective data processing pipelines.

• Reduced Operational Overhead: Automating responses to S3 events using Lambda functions, queues, or topics can significantly reduce manual intervention and operational overhead. This leads to improved efficiency and allows teams to focus on higher-value tasks.

references

https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3_bucket_notification
https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3_directory_bucket
https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-buckets-overview.html

v4.5.0

feat: Add missed tags @MaxymVlasov (#241)

what

Add tags to resources where they missed

v4.4.0

226: Add Expected Bucket Owner @houserx-ioannis (#238)

what

This PR addresses #226 about not being able to specify expected bucket owner in various S3 resources.

why

From AWS docs:

Because Amazon S3 identifies buckets based on their names, an application that uses an incorrect bucket name in a request could inadvertently perform operations against a different bucket than expected. To help avoid unintentional bucket interactions in situations like this, you can use bucket owner condition. Bucket owner condition enables you to verify that the target bucket is owned by the expected AWS account, providing an additional layer of assurance that your S3 operations are having the effects you intend.

references

#226