Connect Amazon S3 or Dropbox
Localize locale files that live in an S3 bucket or a Dropbox folder: pull the source file in, translate it, and write the target-locale files back next to it.
If your locale files live in cloud storage rather than in a code repository, connect the bucket or folder to a project. Each time you select Sync now, transglot reads the source locale file, adds its new and changed strings to the project, and writes one file per target locale back into the same place. Your source file is never overwritten.
Requirements
- Plan: Starter or above. On a lower plan the card offers Upgrade plan instead of Connect.
- Role: Admin of the workspace, or an Owner of its account.
- Your files: one source locale file whose name or path contains the locale code, for example
locales/en.json.
Each workspace holds one Amazon S3 connection and one Dropbox connection, and each feeds one project.
Connect
Amazon S3 connects with an access key you create in AWS. There is no sign-in step.
Create an access key
In AWS IAM, create a user or role for transglot with an access key. Grant it only s3:GetObject, s3:PutObject and s3:ListBucket on the bucket and prefix that holds your locale files.
Open the Amazon S3 page
In your workspace, open Integrations and select Connect on the Amazon S3 card.
Fill in Bucket & credentials
| Field | What to enter |
|---|---|
| Project | The transglot project the files feed |
| Region | The bucket's region, for example eu-west-1 |
| Bucket | The bucket name, for example my-localization-bucket |
| Key prefix (blank = whole bucket) | The folder inside the bucket, for example app/locales |
| Access key ID | The key ID, starting AKIA |
| Secret access key | The secret. It is stored encrypted and cannot be read back |
| Source file name | The file name under the prefix, with {locale} in place of the locale code, for example {locale}.json |
| Format | The file format. See file formats |
| Source locale | The locale your team writes in, for example en |
| Target locales (comma-separated, blank = all) | The locales to write, for example fr, de, es. Leave it blank for every target language in the project |
Select Save configuration. The confirmation reads "Amazon S3 connected. Use Sync now to run the first sync."
Sync
Select Sync now on the connector's page. The sync runs in the background:
- transglot downloads the source locale file and adds its new and changed strings to the project, where translation memory, the glossary and quality checks apply to them like any other content. If automatic translation is on for the project, the new strings are translated.
- transglot writes one file per target locale, named from your Source file name with each locale filled in, next to the source file. A file whose content has not changed is left alone.
Each sync writes the translations the project holds at that moment. Strings translated after the sync started reach your storage on the next Sync now. Syncing is manual: nothing runs on a schedule or when a file changes.
The connector's card on the Integrations page shows the last sync, for example "Source pulled in; 3 target files written."
Disconnect
Select Disconnect on the connector's page and confirm.
- Amazon S3: the stored access key and secret are deleted and cannot be recovered. Objects in the bucket are untouched.
- Dropbox: the stored access is deleted, so reconnecting means signing in to Dropbox again. Files already synced into transglot stay where they are.
Troubleshooting
Write the Source file name with {locale} where the locale code goes, for example {locale}.json.
transglot looked for the source file at the Key prefix plus the Source file name with your Source locale filled in, and found nothing. Check all three, and that the region matches the bucket: the address transglot calls is built from the region and the bucket, so a wrong region reads as a missing file.
Check the Dropbox folder path, the Source file name and the Source locale together name a file that exists.
Access was revoked on the Dropbox side. Select Reconnect and sign in again.
The Source locale on the connection is not a language of the project. Set it to the project's source language, as a locale code such as en, and save again.