
Security News
Security Community Slams MIT-linked Report Claiming AI Powers 80% of Ransomware
Experts push back on new claims about AI-driven ransomware, warning that hype and sponsored research are distorting how the threat is understood.
emittableevent
Advanced tools
EmittableEvent is an opinionated abstraction class for generating rich EventBridge events.
EmittableEvent is an opinionated abstraction class for generating rich EventBridge events.
The problem that EmittableEvent solves is that it provides a simple interface to create richly metadata-detailed events. The risk of not using a utility to do this is, of course, sprawl and unsynced solutions. Not using a conformant way will mean that teams across your organization will all have to deal with building possibly (unsynced) solutions to produce the events. Creating rich events is a non-trivial matter so it's just more boilerplate off your hands.
Note that EmittableEvent is primarily meant to function in an AWS Lambda context, however it will function just fine also outside of one but will be missing certain metadata.
For a great complementary solution using a Domain Event Publisher and an Event Emitter abstraction together with EmittableEvent, see my related Gist.
Using EmittableEvent is mostly a concern of creating your own classes extending it and providing the initial, required static metadata.
// ES5 format
const { EmittableEvent } = require('emittableevent');
// ES6 format
import { EmittableEvent } from 'emittableevent';
// Request context from API Gateway or whatever
const awsRequestContext = event.requestContext;
// Your own event class
class MyEvent extends EmittableEvent {
  // Do something here if you want, else just leave it as is!
}
// Convenience utility to produce required static metadata
// Can of course be a static metadata JSON as well!
const getMetadataConfig = (
  version = 1,
  eventType: any = 'DomainEvent',
  jurisdiction: any = 'eu'
): MetadataConfigInput => {
  return {
    version,
    eventType,
    domain: 'MyDomain',
    system: 'MySystem',
    service: 'MyService',
    team: 'MyTeam',
    hostPlatform: 'aws',
    owner: 'Sam Person',
    jurisdiction
  };
};
// Input for actually creating the event
const eventInput = {
  eventName: 'MyEvent',
  eventBusName: 'MyEventBus',
  data: {
    something: 'some value here if you want'
  },
  metadataConfig: getMetadataConfig()
};
// Create the event
const myEvent = new MyEvent(eventInput, awsRequestContext);
Another benefit of this approach is that you can now "type" your events rather than pass around dumb data blobs.
This is simple. Just do:
// ...and here's the actual full body of the event
const eventPayload = MyEvent.get();
The final event will look similar to:
{
  "EventBusName": "MyEventBus",
  "Source": "mydomain.mysystem.myevent",
  "DetailType": "MyEvent",
  "Detail": "{\"metadata\":{\"version\":1,\"eventType\":\"DomainEvent\",\"domain\":\"MyDomain\",\"system\":\"MySystem\",\"service\":\"MyService\",\"team\":\"MyTeam\",\"hostPlatform\":\"aws\",\"owner\":\"Sam Person\",\"jurisdiction\":\"eu\",\"eventName\":\"MyEvent\",\"timestamp\":\"1666808901725\",\"timestampHuman\":\"2022-10-26T18:28:21.725Z\",\"requestTimeEpoch\":1666808901376,\"id\":\"f9cd2b03-c0ce-4678-8307-a51dd69d4284\",\"correlationId\":\"39594a3d-26d5-4d06-85e0-6d77afbe4ea9\",\"resource\":\"/demo\",\"accountId\":\"123412341234\",\"runtime\":\"AWS_Lambda_nodejs16.x\",\"functionName\":\"my-service-dev-Demo\",\"functionMemorySize\":\"1024\",\"functionVersion\":\"$LATEST\",\"lifecycleStage\":\"dev\",\"region\":\"eu-north-1\"},\"data\":{\"something\":\"some value here if you want\"}}"
}
The below is an example of how a generated EventBridge event might look like. The detail section is a string, but for readability I've made it into an object here.
{
  "EventBusName": "MyEventBus",
  "Source": "mydomain.mysystem.myevent",
  "DetailType": "MyEvent",
  "Detail": {
    "metadata": {
      "version": 1,
      "eventType": "DomainEvent",
      "domain": "MyDomain",
      "system": "MySystem",
      "service": "MyService",
      "team": "MyTeam",
      "hostPlatform": "aws",
      "owner": "Sam Person",
      "jurisdiction": "eu",
      "eventName": "MyEvent",
      "timestamp": "1666808901725",
      "timestampHuman": "2022-10-26T18:28:21.725Z",
      "requestTimeEpoch": 1666808901376,
      "id": "f9cd2b03-c0ce-4678-8307-a51dd69d4284",
      "correlationId": "39594a3d-26d5-4d06-85e0-6d77afbe4ea9",
      "resource": "/demo",
      "accountId": "123412341234",
      "runtime": "AWS_Lambda_nodejs16.x",
      "functionName": "my-service-dev-Demo",
      "functionMemorySize": "1024",
      "functionVersion": "$LATEST",
      "lifecycleStage": "dev",
      "region": "eu-north-1"
    },
    "data": { "something": "some value here if you want" }
  }
}
MIT. See LICENSE for more details.
FAQs
EmittableEvent is an opinionated abstraction class for generating rich EventBridge events.
The npm package emittableevent receives a total of 112 weekly downloads. As such, emittableevent popularity was classified as not popular.
We found that emittableevent demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
Experts push back on new claims about AI-driven ransomware, warning that hype and sponsored research are distorting how the threat is understood.

Security News
Ruby's creator Matz assumes control of RubyGems and Bundler repositories while former maintainers agree to step back and transfer all rights to end the dispute.

Research
/Security News
Socket researchers found 10 typosquatted npm packages that auto-run on install, show fake CAPTCHAs, fingerprint by IP, and deploy a credential stealer.