While loading data from Web-APIs(S3 bucket) using APOC Extended, it is required to download several jar files. This article explains the steps for connecting to an S3 bucket using s3:// protocol with an AWS service account. Using this method, there is no need for accessKey and secretKey. This is more useful in cloud deployment, where any of the keys are exposed in config files/YAMLl files.

Steps

1. Copy the below jar files to the plugins directory

   aws-java-sdk-core-1.12.136.jar 
   aws-java-sdk-s3-1.12.136.jar 
   httpclient-4.5.13.jar
   httpcore-4.4.15.jar
   joda-time-2.10.13.jar 
   aws-java-sdk-sts-1.12.425.jar

In addition to the APOC jar files.

1. Provide a service account to access server instances or the pod.
2. In K8s deployment, additional steps are required for role.yaml and rolebinding.yaml.
3. In K8s deployment, the service account name should be mentioned in values.yaml

   podSpec.serviceAccountName: <name>

4. Verify the S3 bucket access using AWS CLI.
5. Once the connection works fine, the apoc.import.csv should work fine.

Ref :
https://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/credentials.html#credentials-default

https://neo4j.com/labs/apoc/5/import/web-apis/#_using_s3_protocol

https://docs.aws.amazon.com/eks/latest/userguide/iam-roles-for-service-accounts.html