Hi Glenda, Looking at the documentation, an approach you could take is to create an AWSCredentialsProviderControllerService[1] as your AWS Credentials Provider Service property value in the PutS3Object processor configuration properties. You can assign a value to the access key and secret key properties of the controller service. I have not done this myself, so hopefully others can chime in to verify if this is the correct approach or not. Hope that helps.
Best, Shane [1] https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-aws-nar/1.23.0/org.apache.nifi.processors.aws.credentials.provider.service.AWSCredentialsProviderControllerService/index.html On Tue, Feb 13, 2024 at 3:59 PM Glenda Ramos <glend...@hawaii.edu> wrote: > Hi, > > > > We are currently testing Apache NiFi 1.23.0 specifically the "PutS3Object" > processor to automatically transfer data from remote site to an "internal" > S3 bucket. The standard AWSCLI commands work and able to connect the bucket > because we are able to pass in additional credentials like the > AWS_CA_BUNDLE environment variable. That being said, we need AWS_CA_BUNDLE > property added in order to connect successfully to our S3 bucket using > Apache NiFi's "PutS3Object". I have tried passing this as a Parameter and > made it available to the flow but it's not being used by the "PutS3Object" > processor to connect. Is there a way we can add an additional property for > the AWS credentials/config file? It looks like it's only looking for > "accessKey" and "secretKey". > > > > Any help would be greatly appreciated. > > > > Respectfully, > > Glenda Ramos > > Application Engineer >
