# Google Cloud Functions

Google Cloud Functions enables you to build and connect cloud services 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 Cloud Functions and manage access to those applications with Apono.

{% hint style="danger" %}
Apono currently supports the original version of Google Cloud Functions, 1st Gen.
{% endhint %}

***

### Prerequisites

<table><thead><tr><th width="231">Item</th><th>Description</th></tr></thead><tbody><tr><td><strong>Apono Connector</strong></td><td>On-prem <a href="../apono-connector-for-gcp">connection</a> serving as a bridge between your Google Function and Apono, deployed with a GCP service account<br><br><strong>Minimum Required Version</strong>: 1.5.3<br><br>Use the following steps if you need to <a href="../apono-connector-for-gcp/updating-a-connector-in-google-cloud">update an existing connector</a>.</td></tr><tr><td><strong>Cloud Function (1st gen)</strong></td><td>Named function set up within <a href="https://cloud.google.com/functions/docs">Cloud Functions</a><br><br>To allow the Apono connector to call the Cloud Function, add the <strong>Cloud Functions Invoke</strong> and <strong>Cloud Functions Viewer</strong> roles to the apono-connector service account <code>apono-connector-iam-sa</code> for that Cloud Function.</td></tr></tbody></table>

***

### Integrate a Google Cloud Function

{% hint style="success" %}
You can also use the steps below to integrate with Apono using Terraform.

In step **8**, instead of clicking **Confirm**, follow the **Are you integrating with Apono using Terraform?** guidance.
{% endhint %}

Follow these steps to complete the integration:

1. On the [**Catalog**](https://app.apono.io/catalog?search=cloudfunction) tab, click **Cloud Function 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.

{% hint style="success" %}
If the desired connector is not listed, click **+ Add new connector** and follow the instructions for creating a [GCP connector](https://docs.apono.io/docs/gcp-environment/apono-connector-for-gcp).
{% endhint %}

4. Click **Next**. The **Integration Config** section expands.
5. Define the **Integration Config** settings.

   <table><thead><tr><th width="176">Setting</th><th>Description</th></tr></thead><tbody><tr><td><strong>Integration Name</strong></td><td>Unique, alphanumeric, user-friendly name used to identify this integration when constructing an access flow</td></tr><tr><td><strong>Access Details</strong></td><td>Instructions for accessing this integrations's resources</td></tr><tr><td><strong>Custom Parameters</strong></td><td>Key-value pairs to send to the Google Cloud Function<br><br>For example, you can provide a Google Function with a redirect URL that is used for internal provisioning access and passed as part of the action requests.</td></tr><tr><td><strong>Project ID</strong></td><td>ID of the project associated with the Cloud Function</td></tr><tr><td><strong>Region</strong></td><td>Location of the Google Cloud Function instance</td></tr><tr><td><strong>Function Name</strong></td><td>Name of the Google Cloud Function</td></tr></tbody></table>
6. Click **Next**. The **Get more with Apono** section expands.
7. Define the **Get more with Apono** settings.

   <table><thead><tr><th width="179">Setting</th><th>Description</th></tr></thead><tbody><tr><td><strong>Credential Rotation</strong></td><td>(Optional) Number of days after which the database credentials must be rotated<br><br>Learn more about the <a href="../../architecture-and-security/credentials-rotation-policy">Credentials Rotation Policy</a>.</td></tr><tr><td><strong>User cleanup after access is revoked (in days)</strong></td><td><p>(Optional) Defines the number of days after access has been revoked that the user should be deleted</p><p><br>Learn more about <a href="../../architecture-and-security/periodic-user-cleanup-and-deletion">Periodic User Cleanup &#x26; Deletion</a>.</p></td></tr><tr><td><strong>Custom Access Details</strong></td><td>(Optional) Instructions explaining how to access this integration's resources<br><br>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 <strong>400 characters</strong>.<br><br>To view the message as it appears to end users, click <strong>Preview</strong>.</td></tr><tr><td><strong>Integration Owner</strong></td><td><p>(Optional) Fallback approver if no <a href="../../access-flows/dynamic-access-management/resource-and-integration-owners">resource owner</a> is found<br><br>Follow these steps to define one or several integration owners:</p><ol><li>From the <strong>Attribute</strong> dropdown menu, select <strong>User</strong> or <strong>Group</strong> under the relevant identity provider (IdP) platform.</li><li>From the <strong>Value</strong> dropdown menu, select one or multiple users or groups.</li></ol><p><br><strong>NOTE</strong>: When <strong>Resource Owner</strong> is defined, an <strong>Integration Owner</strong> must be defined.</p></td></tr><tr><td><strong>Resource Owner</strong></td><td><p>(Optional) Group or role responsible for managing access approvals or rejections for the resource<br><br>Follow these steps to define one or several <a href="../../access-flows/dynamic-access-management/resource-and-integration-owners">resource owners</a>:</p><ol><li>Enter a <strong>Key name</strong>. This value is the name of the tag created in your cloud environment.</li><li>From the <strong>Attribute</strong> dropdown menu, select an attribute under the IdP platform to which the key name is associated.<br><br>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.</li></ol><p><br><strong>NOTE</strong>: When this setting is defined, an <strong>Integration Owner</strong> must also be defined.</p></td></tr></tbody></table>
8. Click **Confirm**.

<details>

<summary>💡Are you integrating with Apono using Terraform?</summary>

If you want to integrate with Apono using Terraform, follow these steps instead of clicking **Confirm**:

1. At the top of the screen, click **View as Code**. A modal appears with the completed Terraform configuration code.
2. Click to copy the code.
3. Make any additional edits.
4. Deploy the code in your Terraform.

Refer to [Integration Config Metadata](https://docs.apono.io/metadata-for-integration-config/integration-metadata/cloudfunction-custom-integration) for more details about the schema definition.

</details>

Now that you have completed this integration, you can [create access flows](https://docs.apono.io/docs/access-flows/access-flows) that grant permission to your internal application.