Google Search API Secret Configuration

Google Search API Secret Configuration

AWS Secrets Manager Secret Format

For non-local environments (dev, stage, prod), the Google Search API credentials should be stored in AWS Secrets Manager with the following format:

Secret Name

{environment}-rover-mcp/google-api

Examples:

• dev-rover-mcp/google-api
• stage-rover-mcp/google-api
• prod-rover-mcp/google-api

Secret Value Format (JSON)

{
  "api_key": "YOUR_GOOGLE_SEARCH_API_KEY",
  "search_engine_id": "YOUR_GOOGLE_SEARCH_ENGINE_ID"
}

Creating the Secret

Using AWS CLI

# Example for dev environment
aws secretsmanager create-secret \
  --name dev-rover-mcp/google-api \
  --secret-string '{"api_key":"YOUR_API_KEY","search_engine_id":"YOUR_ENGINE_ID"}' \
  --region us-east-1

# Example for stage environment
aws secretsmanager create-secret \
  --name stage-rover-mcp/google-api \
  --secret-string '{"api_key":"YOUR_API_KEY","search_engine_id":"YOUR_ENGINE_ID"}' \
  --region us-east-1

# Example for prod environment (in production account)
aws secretsmanager create-secret \
  --name prod-rover-mcp/google-api \
  --secret-string '{"api_key":"YOUR_API_KEY","search_engine_id":"YOUR_ENGINE_ID"}' \
  --region us-east-1

Using AWS Console

1. Navigate to AWS Secrets Manager
2. Click “Store a new secret”
3. Select “Other type of secret”
4. Enter the JSON value as shown above
5. Name the secret according to the pattern: {environment}-rover-mcp/google-api

Local Development

For local development, continue using the .env file with:

GOOGLE_SEARCH_API_KEY=your_api_key
GOOGLE_SEARCH_ENGINE_ID=your_engine_id

The service automatically detects local development (when FSD_DEPLOY is not set) and uses environment variables instead of AWS Secrets Manager.