You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<ahref="https://github.com/gruntwork-io/terraform-aws-messaging/tree/v1.0.2/modules/kinesis-firehose"className="link-button"title="View the source code for this module in GitHub.">View Source</a>
16
+
<ahref="https://github.com/gruntwork-io/terraform-aws-messaging/tree/v1.0.3/modules/kinesis-firehose"className="link-button"title="View the source code for this module in GitHub.">View Source</a>
17
17
18
-
<ahref="https://github.com/gruntwork-io/terraform-aws-messaging/releases/tag/v0.13.0"className="link-button"title="Release notes for only versions which impacted this module.">Release Notes</a>
18
+
<ahref="https://github.com/gruntwork-io/terraform-aws-messaging/releases/tag/v1.0.3"className="link-button"title="Release notes for only versions which impacted this module.">Release Notes</a>
19
19
20
20
This module creates
21
21
an [Amazon Kinesis Data Firehose](https://docs.aws.amazon.com/firehose/latest/dev/what-is-this-service.html).
@@ -40,15 +40,12 @@ the `var.kinesis_stream_arn` to specify the kinesis data stream, we also have a
Set to true to use a Kinesis Data Stream as the source for the Firehose. When true, kinesis_stream_arn must also be provided. When false, the Firehose will use Direct PUT as the source. This variable is needed because kinesis_stream_arn may come from a resource that isn't created yet, and Terraform needs to know at plan time whether to create the kinesis source configuration.
<ahref="https://github.com/gruntwork-io/terraform-aws-messaging/tree/v1.0.2/modules/kinesis"className="link-button"title="View the source code for this module in GitHub.">View Source</a>
16
+
<ahref="https://github.com/gruntwork-io/terraform-aws-messaging/tree/v1.0.3/modules/kinesis"className="link-button"title="View the source code for this module in GitHub.">View Source</a>
17
17
18
-
<ahref="https://github.com/gruntwork-io/terraform-aws-messaging/releases/tag/v0.13.0"className="link-button"title="Release notes for only versions which impacted this module.">Release Notes</a>
18
+
<ahref="https://github.com/gruntwork-io/terraform-aws-messaging/releases/tag/v1.0.3"className="link-button"title="Release notes for only versions which impacted this module.">Release Notes</a>
19
19
20
20
This module creates a [Kinesis Data Stream](https://docs.aws.amazon.com/streams/latest/dev/key-concepts.html).
# Amazon Managed Streaming for Apache Kafka (Amazon MSK) Module
15
15
16
-
<ahref="https://github.com/gruntwork-io/terraform-aws-messaging/tree/v1.0.2/modules/msk"className="link-button"title="View the source code for this module in GitHub.">View Source</a>
16
+
<ahref="https://github.com/gruntwork-io/terraform-aws-messaging/tree/v1.0.3/modules/msk"className="link-button"title="View the source code for this module in GitHub.">View Source</a>
17
17
18
-
<ahref="https://github.com/gruntwork-io/terraform-aws-messaging/releases/tag/v1.0.1"className="link-button"title="Release notes for only versions which impacted this module.">Release Notes</a>
18
+
<ahref="https://github.com/gruntwork-io/terraform-aws-messaging/releases/tag/v1.0.3"className="link-button"title="Release notes for only versions which impacted this module.">Release Notes</a>
19
19
20
20
This Terraform module configures and launches an [Amazon MSK](https://aws.amazon.com/msk/) cluster.
21
21
@@ -145,12 +145,58 @@ The MSK module supports the following authentication and authorization methods:
# TLS encryption is required for SASL authentication
178
+
encryption_in_transit_client_broker = "TLS"
179
+
}
180
+
```
181
+
182
+
**Note**: When using multiple authentication methods, ensure `encryption_in_transit_client_broker` is set to
183
+
`TLS` or `TLS_PLAINTEXT` as SASL authentication requires TLS encryption for client-broker communication.
184
+
185
+
**Important**: This feature requires Terraform AWS Provider version 4.13.0 or later. If you encounter a
186
+
`ConflictsWith` error when enabling both TLS and SASL, please upgrade your AWS provider version.
187
+
188
+
#### Unauthenticated Access
189
+
190
+
By default, the module sets `enable_client_unauthenticated = false`, which disables unauthenticated client access
191
+
when any authentication method is enabled. If you need to allow unauthenticated access alongside authenticated
192
+
methods (e.g., during a migration), you can set `enable_client_unauthenticated = true`.
193
+
194
+
**Note**: If you have an existing cluster with `unauthenticated = true` and want to enable authentication methods,
195
+
you should explicitly set `enable_client_unauthenticated = true` to prevent Terraform from changing the
196
+
unauthenticated setting unexpectedly.
197
+
198
+
See the [msk-with-multi-auth example](https://github.com/gruntwork-io/terraform-aws-messaging/tree/v1.0.3/examples/msk-with-multi-auth) for a complete working example.
199
+
154
200
You can read more about available authentication and authorization options from
155
201
the [Authentication and authorization for Apache Kafka APIs page](https://docs.aws.amazon.com/msk/latest/developerguide/kafka_apis_iam.html)
156
202
@@ -246,7 +292,7 @@ the [Tiered storage](https://docs.aws.amazon.com/msk/latest/developerguide/msk-t
246
292
You can enable the tiered storage by setting the following variables:
247
293
248
294
*`var.storage_info = "TIERED"`
249
-
*`var.kafka_version = "2.8.2.tiered"` (Note: this is the only supported kafka version for tiered storage)
295
+
*`var.kafka_version`: set to version 3.6.0 or higher (e.g., "3.6.0", "3.7.x", "3.8.x", etc.)
250
296
*`var.instance_type`: set to other than `kafka.t3.small`.
251
297
252
298
It's only supported for the provisioned cluster type (non-serverless mode).
@@ -264,7 +310,7 @@ It's only supported for the provisioned cluster type (non-serverless mode).
Whether unauthenticated client access is enabled. When set to true, clients can connect without authentication. When using TLS or SASL authentication, you typically want this set to false.
0 commit comments