2 Antworten
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
0
We had the same issue previously, because our hosts url was wrong and we did not set "serverless: true".
Solution: Based on the doc, we need to use correct collection id and set "serverless: true:" (shown in below).
sink:
- opensearch:
hosts: [ "https://{collection-id}.us-east-1.aoss.amazonaws.com" ]
index: "my_logs"
aws:
sts_role_arn: "arn:aws:iam::{your-account-id}:role/PipelineRole"
region: "us-east-1"
serverless: true # set it to true
beantwortet vor 3 Monaten
-1
Where does the “search-mydomain-” string come from?
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 3 Jahren
- AWS OFFICIALAktualisiert vor 3 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor einem Jahr
I'm unsure. That is the error message it is presenting me with. I'm using the
AWS-DynamoDBChangeDataCapturePipeline
blueprint.This is what i have within
sink: - opensearch
that is flagging as an error:hosts: [ "https://9o6osesuap5k5r9z8iw8.eu-west-1.aoss.amazonaws.com" ]
(endpoint id changed for this comment)