Discussions

Hi Team,

I'm trying to understand what is now happening with Add-On integration.

I have found out that because I'm using a new developer account, compared to my other business' account, that AWS Lambdas are now deprecated, and are no longer available to new accounts.

This explains why AWS Lambda invocations are no longer available to my new account.

However, this is NOT reflected in the developer guide, which still lists the AWS Lambda as THE Serverless Add-On to use.

That aside, I am told by developer.support, that I should be using the External Integration method and use the AWS Lambda URL.

The Problem:

There is no documentation in the Developer Resources that list how an External Integration is to be implemented, instead developer.support refer me to these forums.

Some starting Questions:

1. When I invoke an External Integration, am I also sent a JWT in lieu of an event data package (such as would be supplied with an AWS Lambda invocation)? Or is just the bare URL triggered?
2. Does the External Integration invoke the Activation URL (in my case, an AWS Lambda URL) from the same address everytime, so that I can lock down who can access the URL?
   1. If not, can I use the AWS Principal number for ServiceM8 to lock it down?
3. Does the External Integration method allow for iFrame invocations (ie within the app), in the same way that AWS Lambdas did previously?
4. Are resources coming that have information about how ServiceM8 handles/invocates External Integrations, so that they can be used?

I'm sure I'll have more questions to come.