# tS3Configuration

Reuses the connection configuration to S3 in the same Job. The Spark cluster to be used reads this configuration to eventually connect to S3.

Multiple tS3Configuration components are allowed per Job.

### In this section

* [tS3Configuration properties for Apache Spark Batch](https://help.qlik.com/talend/en-US/components/8.0/amazon-s3/ts3configuration-properties-for-apache-spark-batch)
* [tS3Configuration properties for Apache Spark Streaming (deprecated)](https://help.qlik.com/talend/en-US/components/8.0/amazon-s3/ts3configuration-properties-for-apache-spark-streaming)
* [tS3Configuration properties for Apache Spark Structured Streaming](https://help.qlik.com/talend/en-US/components/8.0/amazon-s3/ts3configuration-properties-for-apache-spark-structured-streaming)

**Related concepts**

* [Writing and reading data from S3 (Databricks on AWS)](https://help.qlik.com/talend/en-US/components/8.0/amazon-s3/ts3configuration-tfileinputparquet-tfileoutputparquet-tfixedflowinput-writing-and-reading-data-from-s3-databricks-on-aws-the "In this scenario, you create a Spark Batch Job using tS3Configuration and the Parquet components to write data on S3 and then read the data from S3.")
* [Writing server-side KMS encrypted data on EMR](https://help.qlik.com/talend/en-US/components/8.0/amazon-s3/ts3configuration-thdfsconfiguration-tfixedflowinput-tfileoutputparquet-writing-server-side-kms-encrypted-data-on-emr "If the AWS SSE-KMS encryption (at-rest encryption) service is enabled to set Default encryption to protect data on the S3A system of your EMR cluster, select the SSE-KMS option in tS3Configuration when writing data to that S3A system.")