[ABTEST-217] Update API Gateway to put incoming event into correct S3 location Created: 25/May/20  Updated: 04/Jun/20  Resolved: 04/Jun/20

Status: Closed
Project: A/B Testing
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0

Type: Story Priority: Neutral
Reporter: Nguyen Phung Chi Assignee: Maxime Michel
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to ABTEST-200 Update Event composition based on the... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:
Epic Link: ABTEST MVP

 Description   

We are sending the event json to S3 via API Gateway and store directly at the root level of the bucket. E.g ab-testing-timeline/event_1.json

However, we defined the S3 storage strategy: customerID/testID/dateInTermsOfDay(24.04.2020) 

Reference: https://wiki.magnolia-cms.com/pages/viewpage.action?pageId=187204372

AC:

  • Update API Gateway to store the incoming events like the defined strategy

Notes:

  • customerID can be extracted from the license (license owner)

 



 Comments   
Comment by Maxime Michel [ 04/Jun/20 ]

After discussing with ilgun we decided to not do this for now in order to not add any more complexity on API Gateway, because we have few people who would know how to make any sort of debugging over there. We might reconsider this at a later point, though. API Gateway is able to use values it is aware of to define a path in S3.

Generated at Sun Feb 11 22:54:03 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.