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
@@ -301,6 +306,10 @@ See also AWS article: [Working with Regions](https://aws.amazon.com/blogs/develo
301
306
302
307
Enable [S3 Transfer Acceleration](https://docs.aws.amazon.com/AmazonS3/latest/dev/transfer-acceleration.html) for uploads. **IMPORTANT**: For this to work, you must first enable this feature on your destination S3 bucket.
303
308
309
+
**enable_dual_stack**
310
+
311
+
Enable [Amazon S3 Dual-Stack Endpoints](https://docs.aws.amazon.com/AmazonS3/latest/dev/dual-stack-endpoints.html) for uploads. Will make it possible to use either IPv4 or IPv6 when connecting to S3.
312
+
304
313
**use_bundled_cert**
305
314
306
315
For cases where the default SSL certificate is unavailable (e.g. Windows), you can set this option to true in order to use the AWS SDK bundled certificate. Default is false.
@@ -422,16 +431,16 @@ Change one line format in the S3 object. Supported formats are "out_file",
422
431
423
432
424
433
At this format, "time" and "tag" are omitted. But you can set these
425
-
information to the record by setting "include_tag_key" / "tag_key" and
426
-
"include_time_key" / "time_key" option. If you set following configuration in
434
+
information to the record by setting `<inject>` option. If you set following configuration in
427
435
S3 output:
428
436
429
437
# v1
430
438
<format>
431
439
@type json
432
-
include_time_key true
433
-
time_key log_time # default is time
434
440
</format>
441
+
<inject>
442
+
time_key log_time
443
+
</inject>
435
444
# v0.12
436
445
@format json
437
446
include_time_key true
@@ -441,15 +450,14 @@ then the record has log_time field.
441
450
442
451
{"log_time":"time string",...}
443
452
453
+
See also [official Inject Section article](https://docs.fluentd.org/configuration/inject-section).
454
+
444
455
* ltsv
445
456
446
457
key1:value1\tkey2:value2
447
458
key1:value1\tkey2:value2
448
459
...
449
460
450
-
451
-
"ltsv" format also accepts "include_xxx" related options. See "json" section.
log.warn"No ${chunk_id} or %{uuid_flush} in s3_object_key_format with multiple flush threads. Recommend to set ${chunk_id} or %{uuid_flush} to avoid data lost by object conflict"
0 commit comments