aws-microservices
AWS Serverless Event-driven Microservices with using AWS Lambda, AWS DynamoDB, AWS API Gateway, AWS EventBridge, AWS SQS, AWS CDK stands for Cloud Development Kit for IaC, Infrastructure as Code tool and AWS CloudWatch for monitoring.
Not yet testedsource: GitHubhomepageJavaScriptMITcommit b96acb04709d
JavaScript, MIT licensed. The project labels itself: api gateway, aws, aws apigateway, aws dynamodb, aws lambda, cdk, cloudwatch and dynamodb.
aws-microservices has not been verified yet.
Measured by Argusic on a fresh machine every time. Every number links to its evidence.
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
No recorded runs.
Topics (from GitHub)
api-gatewayawsaws-apigatewayaws-dynamodbaws-lambdacdkcloudwatchdynamodbeventbridgelambdalambda-functionssnssns-topicsqssqs-queuestep-functions
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/aws-microservices)Questions
- Does aws-microservices run?
- aws-microservices has not been fully verified yet. No recorded run has produced a verdict yet.
- How did Argusic test aws-microservices?
- On a fresh, disposable machine, with every command recorded. 0 attempts are recorded, and the full method is on the methodology page.
- Where is the evidence for aws-microservices?
- All 0 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.