Installing a Custom Resource Integration
Last updated
Last updated
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 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.
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.
Click “Add Resource” to create a new Custom Resource.
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.
This ID cannot be changed after installation — you’ll need to reinstall if you want to update it.
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.
Click Continue to complete the integration setup. Your function caller is now linked to the P0 Custom Resource.
via any supported P0 interface — Web, Slack, or Microsoft Teams — to confirm your Lambda is being triggered.
