Supported Storage Providers, what details are required for configuration?
OfficeGx currently supports the following storage providers for integration:
Amazon AWS S3
Microsoft Azure Blob Storage
Google Drive
Only one storage account can be configured per company. The Admin must enter the details during setup. If any changes are needed after configuration, please contact support@officegx.com.
Below are the required fields for each provider:
🌐 For AWS S3
| Field | Description / Where to Find |
|---|---|
| Service Provider | AWS |
| Storage Account Name | A name to identify your storage connection |
| Container/Bucket Name | Your AWS S3 bucket name |
| Client ID / Access Key ID | From IAM > User > Security Credentials |
| Client Secret / Secret Access Key | Paired with Access Key ID, downloaded from AWS |
| Session Token (Optional) | Used if temporary credentials via STS are enabled |
| Region | e.g., us-east-1, ap-south-1, etc. |
☁️ For Azure Blob Storage
| Field | Description / Where to Find |
|---|---|
| Service Provider | Azure |
| Storage Account Name | Azure Storage Account name (from Azure Portal) |
| Container/Bucket Name | Container name inside your Azure Storage account |
| Client ID / Access Key ID | From Azure AD > App Registrations > Overview |
| Client Secret / Secret Key | Created in Azure AD > Certificates & Secrets |
| Tenant ID | Found in Azure AD > App Registrations > Directory (Tenant) ID |
| Blob Container Endpoint URL | From Azure Storage > Containers > Properties > Container URL |
📁 For Google Drive
| Field | Description / Where to Find |
|---|---|
| Service Provider | Google Drive |
| Storage Account Name | A label to identify the integration |
| Container/Bucket Name | Not applicable – use same as Folder Name |
| Client ID / Access Key ID | From Google Cloud Console > OAuth 2.0 Client Credentials |
| Client Secret / Secret Key | From the same OAuth credential set |
| Drive Folder ID | From folder URL → e.g., https://drive.google.com/drive/folders/<ID> |
| Refresh Token | Generated through OAuth consent flow during setup |
♥
