Installing a Custom Resource Integration

The Custom Resource integration allows you to securely manage access to external or on-premise applications using AWS Lambda or Google Cloud Run. Whenever a user is granted or revoked access through P0, your service provider is automatically invoked β€” giving you full control over how access is provisioned or removed within your systems.

Before you begin

Before you configure your custom resource, you'll need to set up a few prerequisites. This guide walks you through everything, but before diving into the steps, make sure you have an installed function caller component for AWS or Google Cloud. How to install the AWS function caller

How to install the Google Cloud function caller

Installing your Custom Resource

  1. Go to p0.app in your browser, navigate to Integrations, and select AWS.

2. Scroll to the Resources section and search for β€œCustom” to find the Custom Resource integration type.

  1. Click β€œAdd Resource” to create a new Custom Resource.

  1. Provide a globally unique ID for this resource. This identifier is sent back in the payload to your Lambda and can be used to distinguish multiple resources.

  1. Give your resource a descriptive name that will be shown to end users when they request access. Select AWS or GCP as your service provider.

  1. Click Continue to complete the integration setup. Your function caller is now linked to the P0 Custom Resource.

  1. Make a test access request via any supported P0 interface β€” Web, Slack, or Microsoft Teams β€” to confirm your Lambda is being triggered.

Review the Custom Resource OpenAPI specification

Last updated