Challenge Overview
Project Overview
We are currently working with Amazon to add further code examples to their existing libraries to help build out their code base and documentation, in this case towards their AWS Lambda Service.
Challenge Overview
In this article, written by Amazon, the basic framework is described for implementing a system that leverages AWS Lambda services: https://aws.amazon.com/blogs/compute/fanout-s3-event-notifications-to-multiple-endpoints/. In the article they have called out 3 possible use cases for use of this architecture, image processing, application log processing or content transformation. In this challenge we would like to explore and expand upon the log processing use case.
The results from this challenges should be a simple P.O.C. that demonstrates this stack in action.
-
Utilize sample log data that is readily available on the internet.
-
Upload sample log data to S3 Input bucket for processing.
-
Create derivatives that provide information on logs, this should be useful for security, marketing or operations, feel free to be creative.
-
-
Properly log performed Lambda processes for tracking.
The challenger need not adhere to every step within the article they must implement a simple POC that uses fanout S3 notifications to accomplish the desired use case.
Other Lambda Reference:
Lambda Reference Architecture - Reference Architecture
PLATFORMS
-
AWS Lambda Services
-
AWS S3
TECHNOLOGIES
-
AWS Services and related technologies.
- Javascript
Final Submission Guidelines
Final Submission Guidelines/Deliverables
-
Code base that covers implementation of additional functions. Winning submission will be checked into existing github repository.
-
Deployment guide detailing setup and installation of new functions. Detail the outputs that you've created.
-
Video detailing submission in action
PAYMENTS
Topcoder will compensate members in accordance with the payment structure of this challenge. Initial payment for the winning member will be distributed in two installments. The first payment will be made at the closure of the approval phase. The second payment will be made at the completion of the support period.
RELIABILITY RATING AND BONUS
For challenges that have a reliability bonus, the bonus depends on the reliability rating at the moment of registration for that project. A participant with no previous projects is considered to have no reliability rating, and therefore gets no bonus. Reliability bonus does not apply to Digital Run winnings. Since reliability rating is based on the past 15 projects, it can only have 15 discrete values.