Connector Configuration Reference
\t
for the tab character. When entering configuration values in the API, use escaped characters, such as \\t
for the tab character.ListBucket
and GetObject
permissions.
The following is an IAM policy example. When you set permissions, replace bucketname
with the value used in your implementation.
retryCount
field sets the number of times the S3 client connection should retry when a document fails to index. Issues with AWS connectivity might result in the S3 connector being unable to crawl all of the data. The default for this field is retrying three times. If you are having trouble with AWS connectivity, try setting this field to a higher value, for example, 10
retries.
Configure Remote V2 Connectors
remote-connectors
or admin
role.remote-connectors
role by default, you can create one. No API or UI permissions are required for the role.values.yaml
file, configure this section as needed:enabled
to true
to enable the backend ingress.
pathtype
to Prefix
or Exact
.
path
to the path where the backend will be available.
host
to the host where the backend will be available.
ingressClassName
to one of the following:
nginx
for Nginx Ingress Controlleralb
for AWS Application Load Balancer (ALB)logging.config
property is optional. If not set, logging messages are sent to the console.plain-text
to true
.connectors-backend
pod shuts down and is replaced by a new pod. Once the connector shuts down, connector configuration and job execution are disabled. To prevent that from happening, you should restart the connector as soon as possible.You can use Linux scripts and utilities to restart the connector automatically, such as Monit.max-grpc-retries
bridge parameters.job-expiration-duration-seconds
parameter. The default value is 120
seconds.connector-plugins
entry in your values.yaml
file: