elastic / elastic/integrations

[aws.s3access] Grok fails on CloudFront Origin Access Identity requester

Open Beginner friendly
#20,417 0 comments 0 reactions 0 assignees View on GitHub
bug Integration:aws Team:obs-ds-hosted-services
Dominant language
Handlebars
Stars
333
Forks
647
Avg merge
3d 4h
Merged PRs (30d)
209

Description

### Integration Name

AWS [packages/aws]

### Dataset Name

aws.s3access

### Integration Version

(all)

### Problem

S3 server access logs from CloudFront Origin Access Identity (OAI) requests fail ingest grok parsing. The requester field contains spaces, and `S3REQUESTER` does not allow spaces, so those events land as `event.kind: pipeline_error`.

Example:

```
arn:aws:iam::cloudfront:user/CloudFront Origin Access Identity E2EXAMPLEID
```

This is a real AWS principal ARN format for CloudFront OAI (see [CloudFront OAI docs](https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/private-content-restricting-access-to-s3.html)).

But it fails current pattern:

```yaml
S3REQUESTER: "[a-zA-Z0-9\\/_\\.\\-%:@]+"
```

Contributor guide

Open the contributing guide

Research direction

Start in packages/aws and locate the aws.s3access ingest pattern containing S3REQUESTER. Check the parser against the CloudFront Origin Access Identity ARN shown in the issue; it is done when that requester with spaces is accepted without producing event.kind: pipeline_error.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
cloud, observability
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.