View source for IBM Sterling Connect:Direct: Configuring C:D to use AWS S3 Storage provide an AWS credentials file as a volume

This article describes how to configure IBM Connect:Direct (CDU) to access S3-compatible object storage. 

The setup involves preparing AWS-style configuration files, updating `Initparm.cfg`, and mounting the necessary credential files into the Connect:Direct pod using Kubernetes `extraVolume` and `extraVolumeMount` parameters.

== AWS Configuration Files ==

Two files must be created under the user's `.aws` directory: the **config** file and the **credentials** file.

=== Example: config File ===
<syntaxhighlight lang="ini">[default]
output = json
region = us-east-1

[profile emc]
</syntaxhighlight>

=== Example: credentials File ===
<syntaxhighlight lang="ini">[emc]
aws_access_key_id = <profile id>
aws_secret_access_key = <access key>
</syntaxhighlight>

These files can be automatically generated using the AWS CLI:

<syntaxhighlight lang="bash">aws configure --profile emc</syntaxhighlight>

You will be prompted to enter region, access key, and secret key. After creation, the `.aws` directory must later be mounted inside the pod.

== Updating Initparm.cfg ==
The following S3 I/O Exit configuration must be added to `Initparm.cfg`:

<syntaxhighlight lang="ini"># S3 IO Exit parameters
file.ioexit::name=s3::library=/opt/cdunix/ndm/lib/libcdjnibridge.so::home.dir=/opt/cdunix/ndm/ioexit-plugins/s3::options=-Xmx640m -Djava.class.path=/opt/cdunix/ndm/ioexit-plugins/s3/cd-s3-ioexit.jar -Ds3.endPointUrl=<Dell EMC IP> -Ds3.endPointPort=<port number> -Ds3.endPointSecure=NO -Ds3.profilePath='/home/cduser/.aws/credentials' -Ds3.profileName=<profile name> com.aricent.ibm.mft.connectdirect.s3ioexit.S3IOExitFactory:
</syntaxhighlight>

== Using S3 in Process Files ==
When referencing S3 paths in Connect:Direct processes, use the **s://** prefix to indicate that S3 object storage is being accessed.

== Mounting the .aws Directory in Kubernetes ==
The `.aws` directory containing the **config** and **credentials** files must be mounted on the Connect:Direct container at:

<syntaxhighlight lang="bash">/home/cduser/.aws</syntaxhighlight>

This can be achieved via Helm chart configuration using `extraVolume` and `extraVolumeMount`.

=== Example Helm Values Configuration ===
<syntaxhighlight lang="yaml"># Mount the .aws directory in the container
extraVolumeMounts:
  - name: extravol
    mountPath: /home/cduser/.aws

# Define the NFS volume in the pod spec
extraVolume:
  - name: extravol
    nfs:
      server: <NFS server IP>
      path: /srv/nfs/.aws/
</syntaxhighlight>

Ensure that the `.aws/config` and `.aws/credentials` files are already placed on the NFS path **before** deploying the chart.

== Summary ==
By preparing AWS configuration files, configuring the S3 I/O Exit in `Initparm.cfg`, and mounting the `.aws` directory via Kubernetes volumes, IBM Connect:Direct can seamlessly interact with S3-compatible object storage systems such as Dell EMC. This setup allows secure and flexible object-based file transfers within Connect:Direct processes.


= Ver também =

* [[IBM Sterling| Artigos sobre IBM Sterling]]

* [[Cloud| Artigos sobre Cloud]]
* [[Tecnologias|  Mais Artigos sobre Cloud / WebDev / Tecnologias]]

[[Category:IBM Sterling]]
[[Category:Connect Direct]]
[[Category:B2B Integrator]]
[[Category:CDP]]