Event Handler is a service that allows you to build automations that react to different SIM events. An event handler consists of a rule and one or more actions, which can be freely combined to fit a variety of situations, as well as variables which can be used to customize certain actions.

• Examples of rules that Event Handler can check:

  • Perform an action when a SIM is activated (its status changes to Active)
  • Perform an action when a SIM exceeds 1 GiB of data transfer within one month
  • Perform an action when a SIM's expiration date has passed

• Examples of action that Event Handler can perform:

  • Send a notification by email
  • Change the speed class of the SIM
  • Call an AWS Lambda function

Event Handler has been updated and now supports the following additional rules, actions, and variables:

New Rule: Match when a SIM status is changed to Standby

The Target Status property of the Sim status attribute and Subscriber status attribute rules can now be set to Standby. With this configuration, an Event Handler will run its actions when a SIM's status is changed to Standby.

Updated Rule: Match source SIM status

In addition to configuring an Event Handler rule to run its actions when a SIM's status is changed to a specific status (such as when a SIM status changes to Active or Inactive), you can now also match a specific SIM status before the status change.

This gives you finer control over your devices, such as running different actions when a SIM changes from Ready to Active, than when it changes from Inactive to Active.

New Action: Suspend a SIM

You can now choose to suspend a SIM (change its status to Suspended) as an action to perform when an Event Handler's rule is matched.

• Note: A fee may apply

  Note that a suspension fee or a reactivation fee will apply when changing a SIM status to or from the Suspended status, respectively, depending on the subscription plan of the SIM. For more information, refer to the Pricing & Fee Schedule documentation.

New Variable: Coverage Type

Event Handlers only apply to the coverage type in which they are created. In other words, an Event Handler created for Global coverage will only apply to SIMs which are also managed in the Global coverage type, and likewise for Japan coverage. If you have configured Event Handlers in both coverage types, you can now use the ${coverage} variable in the Send email, Send mail to operator, Execute web request, and Invoke AWS Lambda actions to differentiate which coverage type the action is coming from. This variable will return the following values:

• When an Event Handler in Global coverage executes, ${coverage} will be replaced with g
• When an Event Handler in Japan coverage executes, ${coverage} will be replaced with jp

For more information, please refer to the Event Handler documentation.