AWS wickr: Recommend redundant DR bot and S3/EBS DR for data retention
Summary
Adds a monitoring link and recommends running a second data retention bot in parallel plus EBS snapshots and S3 cross-region replication to avoid missed messages during maintenance.
Security assessment
Improves continuity of retained message logs by recommending redundant DR bot operation, but does not address a specific vulnerability or security control.
Evidence
+For Disaster Recovery, we recommend Snapshot Lifecycles on the Amazon EBS volume(s) and Amazon S3 Cross-Region Replication to protect the data your DR Bot has captured. For redundancy during instance rotations, upgrades, and other maintenance windows, we recommend running a second DR Bot in parallel on a separate host, with its own Amazon EBS volume. While one bot is being restarted or replaced, the other continues to capture messages, so no messages are missed. To configure how often messages are sent to Amazon S3, you can set the environment variable `WICKRIO_COMP_FILESIZE` or `WICKRIO_COMP_TIMEROTATE` to rotate on size or time. Message logs and file attachments will get delivered into the same prefix in the same bucket. For more information, see [Environment variables to configure data retention bot in AWS Wickr](./data-retention-bot-env-variables.html).
Diff
diff --git a/wickr/latest/adminguide/configure-data-retention.md b/wickr/latest/adminguide/configure-data-retention.md index 88d42eb..bbea6f4 100644 --- a//wickr/latest/adminguide/configure-data-retention.md +++ b//wickr/latest/adminguide/configure-data-retention.md @@ -45,0 +46,2 @@ For more information on Amazon EBS, see [Amazon EBS snapshot lifecycle](https:// + * [Monitor the data retention bot for your Wickr network](./data-retention-bot-monitoring.html) + @@ -84 +86 @@ The DR Bot is validated for sustained processing at approximately 11,000 message -For Disaster Recovery, we recommend Snapshot Lifecycles on the Amazon EBS volume(s) and Amazon S3 Cross-Region Replication. To configure how often messages are sent to Amazon S3, you can set the environment variable WICKRIO_COMP_FILESIZE or `WICKRIO_COMP_TIMEROTATE` to rotate on size or time. Message logs and file attachments will get delivered into the same prefix in the same bucket. For more information, see [Environment variables to configure data retention bot in AWS Wickr](./data-retention-bot-env-variables.html). +For Disaster Recovery, we recommend Snapshot Lifecycles on the Amazon EBS volume(s) and Amazon S3 Cross-Region Replication to protect the data your DR Bot has captured. For redundancy during instance rotations, upgrades, and other maintenance windows, we recommend running a second DR Bot in parallel on a separate host, with its own Amazon EBS volume. While one bot is being restarted or replaced, the other continues to capture messages, so no messages are missed. To configure how often messages are sent to Amazon S3, you can set the environment variable `WICKRIO_COMP_FILESIZE` or `WICKRIO_COMP_TIMEROTATE` to rotate on size or time. Message logs and file attachments will get delivered into the same prefix in the same bucket. For more information, see [Environment variables to configure data retention bot in AWS Wickr](./data-retention-bot-env-variables.html).