This is meant to be a guide for understanding how the elements in the AWS architecture fit in the code base
This is meant to be a guide for understanding how the elements in the AWS architecture fit in the code base
Analytics application, SQL: threshold-scheduler-v1-prod |-> https://github.com/swipesense/asset_service_scheduler/blob/master/delayed_delivery.sql it is critical to understand the SQL statements above for asset/badge tracking |->destinations: |->LAMBDA: threshold-scheduler-v1-prod-publish_to_sns https://github.com/swipesense/asset_service_scheduler/blob/master/handler.py From here, we publish to SNS and land in asset_service repo to invoke other lambdas/functions. THRESHOLD_SNS_TOPIC_ARN arn:aws:sns:us-east-1:825374148190:threshold-scheduler-v1-prod |-> SNS topic: threshold-scheduler-v1-prod |-> LAMBDA: asset-service-v4-prod-put_asset_location https://github.com/swipesense/asset_service/blob/master/handler.py |->Kinesis Firehose Stream, threshold-scheduler-v1-prod-all-tags Destination, S3 threshold-scheduler-v1-prod-all-tags |-> SNS topic: threshold-scheduler-v1-prod-all-tags |->LAMBDA: hardware-service-go-v1-prod-badge-active-go https://github.com/swipesense/hardware_service/tree/master/badgeactiveservice/main.go |->Kinesis Firehose Stream, threshold-scheduler-v1-prod-all-tags-status |->Transformation with LAMBDA: kinesis-analytics-processor (nodejs) https://github.com/swipesense/pdf_reports/blob/master/src/index.js |-> S3 destination, threshold-scheduler-v1-prod-all-tags-status S3 destination: ingest-mesh-events-v3-production 1MB or 60sec after 90 days object transition to Glacier (archive) https://github.com/swipesense/hardware_service/blob/master/hardwareservice/main.go https://github.com/swipesense/mesh_events_dynamo/blob/master/handler.py https://github.com/swipesense/contact_tracing_service/blob/master/scheduler/main.go https://github.com/swipesense/visit_algorithm_scheduler/blob/master/main.go