Gemini is an AI platform that allows developers to integrate multimodal capabilities into their applications, including text, images, audio, and video processing. It supports tasks such as natural language processing, content generation, and data analysis.
Below you can find the Aembit configuration required to work with the Google Gemini service as a Server Workload using the REST API.
Prerequisites
Section titled “Prerequisites”Before proceeding with the configuration, ensure you have a Google account and an API key. If you have not already created a key, follow the instructions below. For more details about the Gemini API, refer to the official Gemini API documentation.
Create API Key
Section titled “Create API Key”-
Navigate to the API Keys page and sign in to your Google account.
-
Click the Create API key button in the middle of the page.
-
Click the Got it button on the Safety Setting Reminder pop-up window.
-
If you do not already have a project in Google Cloud, click Create API key in new project. Otherwise, select from your projects and click Create API key in existing project.
- Click Copy and securely store the key for later use in your tenant configuration.
Server Workload Configuration
Section titled “Server Workload Configuration”- Create a new Server Workload.
- Name - Choose a user-friendly name.
- Configure the service endpoint:
- Host -
generativelanguage.googleapis.com - Application Protocol - HTTP
- Port - 443 with TLS
- Forward to Port - 443 with TLS
- Authentication method - HTTP Authentication
- Authentication scheme - Header
- Header - x-goog-api-key
Credential Provider Configuration
Section titled “Credential Provider Configuration”- Create a new Credential Provider.
- Name - Choose a user-friendly name.
- Credential Type - API Key
- API Key - Paste the key copied from Google AI Studio.
Client Workload Configuration
Section titled “Client Workload Configuration”Aembit now handles the credentials required to access the Server Workload, eliminating the need for you to manage them directly. You can safely remove any previously used credentials from the Client Workload.
If you access the Server Workload through an SDK or library, it is possible that the SDK/library may still require credentials to be present for initialization purposes. In this scenario, you can provide placeholder credentials. Aembit will overwrite these placeholder credentials with the appropriate ones during the access process.
Access Policy
Section titled “Access Policy”- Create an Access Policy for a Client Workload to access the Gemini Server Workload. Assign the newly created Credential Provider to this Access Policy.
Required Features
Section titled “Required Features”- You will need to configure the TLS Decrypt feature to work with the Gemini Server Workload.