Closed kaiyan-sheng closed 2 years ago
Looks like this is the same issue showing up in this discuss thread: https://discuss.elastic.co/t/aws-fleet-integration-fails-with-api-key-error-on-ingest/304846/3
the same seems to be when setting a cloudwatch logs integration without custom namespace and dataset:
- data_stream:
namespace: default
[...]
streams:
- dataset: generic
[...]
the default is logs-generic-default
the permission are on logs-aws.cloudwatch_logs-default
indices:
- names:
- logs-aws.cloudwatch_logs-default
privileges:
- auto_configure
- create_doc
fixed by #3844
When I create a cloudwatch log integration with a custom namespace and dataset name, I got an error:
Here is the agent policy:
We can see from the agent policy,
logs-aws.cloudwatch_logs-development
is the index with the correct privileges, notlogs-generic-development
.