# tS3BucketExist Verifies if the specified bucket exists on Amazon S3. "Bucket" is a term used by AWS for top level folders on S3, which can contain sub folders and store all your data (objects). ## tS3BucketExist Standard properties These properties are used to configure tS3BucketExist running in the Standard Job framework. The Standard tS3BucketExist component belongs to the Cloud family. The component in this framework is available in all Talend products. ## Basic settings | Properties | Description | | --- | --- | | Property type | Either Built-In or Repository.


Built-In: No property data stored centrally.


Repository: Select the repository file where the
properties are stored. | | Use existing connection | Select this check box and in the Component
List drop-down list, select the desired connection component to
reuse the connection details you already defined. | | Credential provider | Specify the way to obtain AWS security credentials.



This option can work as a dynamic parameter and be assigned a value using a
context variable.

Information noteNote: tRedshiftBulkExec, tRedshiftOutputBulk, and tRedshiftOutputBulkExec support
S3 connections that are established with Credential
Provider being Static Credentials or
Inherit credentials from AWS role only. | | Assume Role | If you temporarily need some access permissions associated to an AWS IAM
role that is not granted to your user account, select this checkbox to assume that
role. Then specify the values for the following parameters to create a new assumed
role session. | | Region | Specify the AWS region by selecting or entering a region name between double
quotation marks (e.g. *"us-east-1"*). For more information about the
AWS Region, see [Regions and Endpoints](http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region). | | Bucket | Enter the name of the bucket, namely the top level folder, on
the S3 server.

If using Express One Zone (S3 directory buckets), you must specify the full
bucket name in the format
<bucketBaseName>--<availabilityZoneID>--x-s3,
as required by AWS. For more information about directory buckets, see the [AWS Documentation](https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-bucket-naming-rules.html).

Information noteNote: The support of
S3 Express One Zone comes with the 8.0.1-R2026-01 Talend Studio monthly update or a later one delivered by Talend. | | Die on error | This checkbox is cleared by default, meaning to skip the row on
error and to complete the process for error-free rows. | ## Advanced settings | Properties | Description | | --- | --- | | tStatCatcher Statistics | Select this checkbox to collect log data at the component
level. | | Use a custom region endpoint | Select this checkbox to use a custom endpoint and in the field displayed,
specify the URL of the custom endpoint to be used.

This option can work as a
dynamic parameter and be assigned a value using a context
variable. | | Signing region | Select the AWS region of the STS service. If the region is
not in the list, you can enter its name between double quotation marks. The
default value is us-east-1.

This dropdown list is available only when the Assume role
checkbox is selected. | | Specify STS endpoint | Select this check box to specify the AWS Security
Token Service (STS) endpoint from which to retrieve the session credentials.
For example, enter sts.amazonaws.com.

This checkbox is available only when the Assume
role checkbox is selected. | | External ID | If the administrator of the account to which the role
belongs provided you with an external ID, enter its value here. The
External Id is a unique
identifier that allows a limited set of users to assume the role.

This field is available only when the Assume role checkbox
is selected. | | Serial number | When you assume a role, the trust policy of this role might
require Multi-Factor Authentication (MFA). In this case, you must indicate
the identification number of the hardware or virtual MFA device that is
associated with the user who assumes the role.

This field is available only when the Assume role checkbox
is selected. | | Token code | When you assume a role, the trust policy of this role might
require Multi-Factor Authentication (MFA). In this case, you must indicate a
token code. This token code is a time-based one-time password produced by
the MFA device.

This field is available only when the Assume role checkbox
is selected. | | Tags | List session tags in the form of key-value pairs. You can
then use these session tags in policies to allow or deny access to requests.


Transitive: select this checkbox to indicate that a tag
will persist to the next role in a role chain.

For more information about tags, see [Passing Session Tags in AWS
STS](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_session-tags.html#id_session-tags_role-chaining)

This field is available only when the Assume role checkbox
is selected. | | IAM policy ARNs | Enter the Amazon Resource Names (ARNs) of the IAM managed
policies that you want to use as managed session policies. Use managed
session policies to limit the permissions of the session. The policies must
exist in the same account as the role. The resulting session's permissions
are the intersection of the role's identity-based policy and the session
policies.

For more information about session policies, see the
corresponding section in [Policies and Permissions](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html#policies_session)

This field is available only when the Assume role checkbox
is selected. | | Policy | Enter an IAM policy in JSON format that you want to use as a
session policy. Use session policies to limit the permissions of the
session. The resulting session's permissions are the intersection of the
role's identity-based policy and the session policies.

For more information about session policies, see the
corresponding section in [Policies and Permissions](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html#policies_session)

This field is available only when the Assume role check box
is selected. | | Config client | Select this checkbox to configure client parameters.

Client parameter: select client
parameters from the list.

Value: enter the parameter value.

Not
available when Use existing connection
is selected. | ## Global Variables | Variables | Description | | --- | --- | | BUCKET\_EXIST | The existence of a specified bucket. This is a Flow variable
and it returns a boolean. | | BUCKET\_NAME | The name of a specified bucket. This is an After variable and
it returns a string. | | ERROR\_MESSAGE | The error message generated by the component when an error
occurs. This is an After variable and it returns a string. This variable
functions only if the Die on error
check box is selected. | ## Usage | Usage guidance | Description | | --- | --- | | **Usage rule** | This component is usually used with other S3 components, e.g. tS3BucketCreate. | | Dynamic settings | Click the [+] button to add a row in the table
and fill the Code field with a context
variable to choose your database connection dynamically from multiple
connections planned in your Job. This feature is useful when you need to
access database tables having the same data structure but in different
databases, especially when you are working in an environment where you
cannot change your Job settings, for example, when your Job has to be
deployed and executed independent of Talend Studio.

Once a dynamic parameter is defined, the Component List box in the Basic
settings view becomes unusable.

For examples on using dynamic parameters, see [Reading data from databases through
context-based dynamic connections](https://help.qlik.com/talend/r/en-US/8.0/components/defining-context-groups/reading-data-from-databases-through-context-based-dynamic-connections) and [Reading data from different MySQL databases
using dynamically loaded connection parameters](https://help.qlik.com/talend/r/en-US/8.0/components/context/reading-data-from-different-mysql-databases-using-dynamically-loaded-connection-parameters). For more information on
Dynamic settings and context variables, see
[Dynamic schema](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/dynamic-schema) and [Creating a context group and define context
variables in it](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/creating-context-group-and-define-context-variables-in-it). | **Related concepts** * [Verifing the absence of a bucket, creating it and listing all the S3 buckets](https://help.qlik.com/talend/en-US/components/8.0/amazon-s3/ts3bucketlist-ts3bucketexist-tlogrow-verifing-absence-of-bucket-creating-it-and-listing-all-s3-buckets-standard-component-in-this)