Hello,
Below you can find my deployment YAML. When I deploy version 2.19.2, I can successfully add the S3 repository via the dashboard without any issues. However, when I deploy version 3.0.0 or 3.1.0, I encounter the following error:
Deployment YAML
apiVersion: opensearch.opster.io/v1
kind: OpenSearchCluster
metadata:
name: opensearch-cluster
namespace: opensearch
spec:
general:
serviceName: cluster
version: 3.0.0
setVMMaxMapCount: true
pluginsList: ["repository-s3"]
keystore:
- secret:
name: s3-secret
keyMappings:
accessKey: s3.client.default.access_key
secretKey: s3.client.default.secret_key
additionalConfig:
s3.client.default.endpoint: endpoint.com
s3.client.default.max_retries: "3"
s3.client.default.path_style_access: "true"
s3.client.default.protocol: https
s3.client.default.read_timeout: 50s
s3.client.default.use_throttle_retries: "true"
s3.client.default.region: us-east-2
bootstrap:
additionalConfig:
network.bind_host: "0.0.0.0"
dashboards:
enable: true
opensearchCredentialsSecret:
name: dashboards-credentials
tls:
enable: true
generate: true
version: 3.0.0
replicas: 2
resources:
requests:
memory: "5500Mi"
cpu: "5000m"
limits:
memory: "5500Mi"
cpu: "5000m"
additionalConfig:
opensearch_security.multitenancy.enabled: "true"
nodePools:
- component: masters
replicas: 3
diskSize: "50Gi"
resources:
requests:
memory: "10Gi"
cpu: "5000m"
limits:
memory: "10Gi"
cpu: "5000m"
roles:
- "cluster_manager"
- component: nodes
replicas: 3
diskSize: "100Gi"
resources:
requests:
memory: "10Gi"
cpu: "5000m"
limits:
memory: "10Gi"
cpu: "5000m"
roles:
- "data"
- component: coordinators
replicas: 3
diskSize: "10Gi"
resources:
requests:
memory: "10Gi"
cpu: "5000m"
limits:
memory: "10Gi"
cpu: "5000m"
roles:
- "ingest"
security:
config:
adminCredentialsSecret:
name: admin-credentials-secret
securityConfigSecret:
name: securityconfig-secret
tls:
transport:
generate: true
perNode: true
http:
generate: true
ERROR
{"error":{"root_cause":[{"type":"repository_verification_exception","reason":"[testa] path is not accessible on cluster-manager node"}],"type":"repository_verification_exception","reason":"[test] path is not accessible on cluster-manager node","caused_by":{"type":"i_o_exception","reason":"Unable to upload object [tests-ud79g-x2Rg2EhXIdNTd_Zg/master.dat] using a single upload","caused_by":{"type":"s3_exception","reason":"s3_exception: (Service: S3, Status Code: 403, Request ID: 80000000000001380002fe084a4df944) (SDK Attempt Count: 1)"}}},"status":500}