AWS Lambda Custom Integration

Learn how to integrate an AWS Lambda Custom Integration with Apono

AWS Lambda enables you to build and connect cloud services and internal web apps by writing single-purpose functions that are attached to events emitted from your cloud infrastructure and services.

Its serverless architecture frees you to write, test, and deploy functions quickly without having to manage infrastructure setup.

With this integration, you can connect your internal applications to AWS Lambda functions and manage access to those applications with Apono.

---

Prerequisites

Before starting this integration, create the items listed in the following table.

Item	Description
Apono Connector	On-prem connection serving as a bridge between your AWS Lambda functions and Apono Minimum Required Version: 1.4.1 Use the following steps to update an existing connector.
Lambda Function	Named function set up within AWS Lambda 💡 When creating the Lambda function, apply the tag apono-connector-access: "true". Sample Function function listResources(params) { return { resources: [ { 'id': 'resource1', 'name': 'Resource 1', 'type': params.resource_type, 'metadata': { 'key1': 'value1' } }, { 'id': 'resource2', 'name': 'Resource 2', 'type': params.resource_type, 'metadata': { 'key2': 'value2' } }, { 'id': 'resource3', 'name': 'Resource 3', 'type': params.resource_type, 'metadata': { 'key3': 'value3' } }, ], permissions: [ { 'id': 'admin', 'name': 'Admin' }, { 'id': 'reader', 'name': 'Reader' } ] }; } function grantAccess(params) { const username = params.username; const grantId = params.grant_id; const resources = params.resources; const permission = params.permission; const param1 = params.custom_parameters.param1 const param2 = params.custom_parameters.param2 console.log(param1) console.log(param2) return { status: 'ok' }; } function revokeAccess(params) { const username = params.username; const grantId = params.grant_id; const resources = params.resources; const permission = params.permission; const param1 = params.custom_parameters.param1 const param2 = params.custom_parameters.param2 return { status: 'ok' }; } function createCredentials(params) { const username = params.username; const grantId = params.grant_id; const resources = params.resources; const param1 = params.custom_parameters.param1 const param2 = params.custom_parameters.param2 return { status: 'ok' }; } export const handler = async (event) => { const params = event.params; switch (event.event_type) { case 'create-credentials': return createCredentials(params); case 'list-resources': return listResources(params); case 'grant-access': return grantAccess(params); case 'revoke-access': return revokeAccess(params); case 'create-credentials': return { status: 'ok', secret: 'created-credentials-secret' } case 'reset-credentials': return { status: 'ok', secret: 'reset-credentials-secret' } default: return { status: 'active' }; } };

---

Integrate an AWS Lambda Custom Integration

Follow these steps to complete the integration:

1. On the Catalog tab, click AWS Lambda Custom Integration. The Connect Integration page appears.

2. Under Discovery, click Next. The Apono connector section expands.

3. From the dropdown menu, select a connector.

If the desired connector is not listed, click + Add new connector and follow the instructions for creating an AWS connector.

4. Click Next. The Integration Config section expands.

5. Define the Integration Config settings.

   Setting	Description
   Integration Name	Unique, alphanumeric, user-friendly name used to identify this integration when constructing an access flow
   Custom Parameters	Key-value pairs to send to the lambda function For example, you can provide a lambda function with a redirect URL that is used for internal provisioning access and passed as part of the action requests.
   Region	Region of the AWS Lambda instance
   Function Name	Named of the AWS Lambda function
6. Click Next. The Get more with Apono section expands.

7. Define the Get more with Apono settings.

   Setting	Description
   Custom Access Details	(Optional) Instructions explaining how to access this integration's resources Upon accessing an integration, a message with these instructions will be displayed to end users in the User Portal. The message may include up to 400 characters. To view the message as it appears to end users, click Preview. NOTE: You can also add the custom_access_details parameter to the apono_integration schema using Terraform. For more information, learn how to integrate with Apono in the Terraform Registry.
   Integration Owner	(Optional) Fallback approver if no resource owner is found Follow these steps to define one or several integration owners: From the Attribute dropdown menu, select User or Group under the relevant identity provider (IdP) platform. From the Value dropdown menu, select one or multiple users or groups. NOTE: When Resource Owner is defined, an Integration Owner must be defined.
   Resource Owner	(Optional) Group or role responsible for managing access approvals or rejections for the resource Follow these steps to define one or several resource owners: Enter a Key name. This value is the name of the tag created in your cloud environment. From the Attribute dropdown menu, select an attribute under the IdP platform to which the key name is associated. Apono will use the value associated with the key (tag) to identify the resource owner. When you update the membership of the group or role in your IdP platform, this change is also reflected in Apono. NOTE: When this setting is defined, an Integration Owner must also be defined.
8. Click Confirm.

Now that you have completed this integration, you can create access flows that grant permission to your AWS Lambda function.