LogoLogo
Metadata for Integration Config
Metadata for Integration Config
  • INTEGRATION METADATA
    • Amazon Account
    • AWS EC2 SSH
    • Elastic Kubernetes Service (EKS)
    • AWS Lambda Custom Integration
    • Amazon Organization
    • AWS RDS MySQL
    • AWS RDS PostgreSQL
    • Amazon RDS
    • Entra ID (Azure AD) Groups
    • Azure Kubernetes Service (AKS)
    • Azure Management Group
    • Azure MySQL
    • Azure PostgreSQL
    • Azure Subscription
    • Azure VM SSH
    • Cloud Function Custom Integration
    • F5 Network
    • Google AlloyDB
    • Google BigQuery
    • Google Cloud SQL - MySQL
    • Google Cloud SQL - PostgreSQL
    • Google Kubernetes Engine (GKE)
    • Google Organization
    • Google Project
    • Github
    • JumpCloud
    • Kubernetes Proxy
    • Kubernetes
    • LDAP Group
    • MariaDB
    • Mongo Atlas Portal
    • MongoDB Atlas
    • MongoDB
    • Microsoft SQL Server
    • MySQL
    • Okta Group
    • OneLogin Group
    • 1Password
    • OpenVPN
    • Oracle Database
    • PostgreSQL
    • RabbitMQ
    • Rancher
    • RDP
    • Redis Cloud (Redislabs)
    • Amazon Redshift
    • Snowflake
    • SSH
    • Vertica Database
    • Web App
    • Windows Domain Controller
Powered by GitBook
On this page
  • Example Usage
  • Schema
  • Integration Config

Was this helpful?

Export as PDF
  1. INTEGRATION METADATA

AWS Lambda Custom Integration

AWS Lambda Custom Integration allows use AWS Lambda as a custom implementation for resource integration

Example Usage


aws-lambda-custom-integration-integration.tf
resource "apono_integration" "aws-lambda-custom-integration-integration" {
  name                     = "AWS Lambda Custom Integration"
  type                     = "aws-lambda-custom-integration"
  connector_id             = "apono-connector-id"
  connected_resource_types = ["aws-lambda-custom-integration"]
  metadata = {
    access_details = "<Access Details>"
    custom_parameters = "<Custom Parameters>"
    region = "<Region>"
    function_name = "<Function Name>"
  }
}
aws-lambda-custom-integration-integration.tf
resource "apono_resource_integration" "aws-lambda-custom-integration-integration" {
  name                     = "AWS Lambda Custom Integration"
  type                     = "aws-lambda-custom-integration"
  connector_id             = "apono-connector-id"
  connected_resource_types = ["aws-lambda-custom-integration"]
  integration_config = {
    access_details = "<Access Details>"
    custom_parameters = "<Custom Parameters>"
    region = "<Region>"
    function_name = "<Function Name>"
  }
}

Schema


  • type aws-lambda-custom-integration

  • connected_resource_types List of resource types to sync.

Available resource types you can use
  • aws-lambda-custom-integration

Integration Config


  • access_details (Required | String) Access Details

  • custom_parameters (Required | String) Custom Parameters

  • region (Required | String) Region

    • Possible values: us-east-1, us-east-2, us-west-1, us-west-2, eu-central-1, eu-central-2, eu-west-1, eu-west-2, eu-south-1, eu-south-2, eu-west-3, eu-north-1, af-south-1, ap-east-1, ap-southeast-3, ap-southeast-4, ap-southeast-5, ap-southeast-7, ap-south-1, ap-south-2, ap-northeast-3, ap-northeast-2, ap-southeast-1, ap-southeast-2, ap-northeast-1, ca-central-1, ca-west-1, me-south-1, me-central-1, sa-east-1, il-central-1, mx-central-1

  • function_name (Required | String) Function Name

PreviousElastic Kubernetes Service (EKS)NextAmazon Organization

Last updated 3 hours ago

Was this helpful?