Update 1-Understanding ephemeral blobs.md

This commit is contained in:
Reed Umbrasas 2017-11-14 15:38:32 -08:00 коммит произвёл GitHub
Родитель 4dbd794089
Коммит ee0225b338
Не найден ключ, соответствующий данной подписи
Идентификатор ключа GPG: 4AEE18F83AFDEB23
1 изменённых файлов: 5 добавлений и 0 удалений

Просмотреть файл

@ -0,0 +1,5 @@
# Understanding Ephemeral Storage Accounts
Enterprise BI and Reporting TRI Job Manager maintains Azure Storage accounts which serve as the landing spot for data to be ingested to TRI. The job manager will create a new storage account every 24 hours. After a new account is created, previously created accounts will be deleted once all the data uploaded to those accounts is successfully ingested. This ensures that one storage account contains no more than 24 hours worth of data. As a result, if one of the TRI's ingesting clients was compromised, no more than 24 hours worth of data could be impacted.
The Job Manager exposes an API to fetch the SAS URI for the currently active Storage Account. Therefore, when integrating on-prem data ingestion systems with this TRI, the first step is to always fetch the SAS URI for the currently active Storage Account.