Create a connection

• •AWS Secrets Manager
• •Azure Key Vault

1In Administrator, select Connections.
2Click Add Connection.
3Search for and select Amazon S3 V2 and then click Next.
4Enter the following connection details:

Property	Description
Connection Name	Name of the connection. Each connection name must be unique within the organization. Connection names can contain alphanumeric characters, spaces, and the following special characters: _ . + -, Maximum length is 255 characters.
Description	Description of the connection. Maximum length is 4000 characters.
Use Secret Vault	Stores sensitive credentials for this connection in the secrets manager that is configured for your organization. This property appears only if secrets manager is set up for your organization. When you enable the secret vault in the connection, you can select the credentials that the Secure Agent retrieves from the secrets manager. If you don't enable this option, the credentials are stored in the repository or on a local Secure Agent, depending on how your organization is configured. Note: If you’re using this connection to apply data access policies through pushdown or proxy services, you cannot use the Secret Vault configuration option. For information about how to configure and use a secrets manager, see Secrets manager configuration.
Runtime Environment	The name of the runtime environment where you want to run tasks.
Access Key	The access key ID used to access the Amazon account resources. Required if you do not use AWS Identity and Access Management (IAM) authentication. Note: Ensure that you have valid AWS credentials before you create a connection.
Secret Key	The secret access key used to access the Amazon account resources. This value is associated with the access key and uniquely identifies the account. You must specify this value if you specify the access key ID. Required if you do not use AWS Identity and Access Management (IAM) authentication.
Folder Path	Bucket name or complete folder path to the Amazon S3 objects. For tasks other than application ingestion and database ingestion tasks, don't use a slash at the end of the folder path. For example, <bucket name>/<my folder name>.
IAM Role ARN (Advanced Setting)	The Amazon Resource Name of the IAM role assumed by the IAM user or the EC2 role to use temporary security credentials and access the AWS resources.
External ID (Advanced Setting)	The AssumeRole request parameter to generate temporary session credentials that enable an IAM user or AWS service to assume a role. For more information about how to use the assume role, see the Using an assume role for Amazon S3 resources in Informatica Cloud Data Integration How-To Library.
Use EC2 Role to Assume Role (Advanced Setting)	Enables the EC2 role to assume an IAM role specified in the IAM Role ARN option. Note: If you choose to configure the IAM user to assume an IAM role specified in the IAM Role ARN option, clear this option.
S3 Account Type (Advanced Setting)	The type of the Amazon S3 account. Select one of the following options: - Amazon S3 Storage. Enables you to use the Amazon S3 services. - S3 Compatible Storage. Enables you to use the endpoint for a third-party storage provider such as Scality RING or MinIO. Default is Amazon S3 storage.
REST Endpoint (Advanced Setting)	The S3 storage endpoint required for an S3 compatible storage. Enter the S3 storage endpoint in the HTTP or HTTPs format. For example, http://s3.isv.scality.com.

5Select the authentication type to connect to Amazon S3 and enter the required properties.
You can use the following authentication types:
• - Basic Authentication
• - AssumeRole via EC2 role Authentication
• - Credential Profile File Authentication
• - IAM Roles Anywhere Authentication
6Click Test to test your connection to the source system.
7Click Save.

Basic authentication

AssumeRole via EC2 role authentication

Credential Profile File authentication

IAM Roles Anywhere authentication