AWS drs documentation change
Summary
Added new FAQ question about how AWS Elastic Disaster Recovery ensures replication servers are patched and follow security best practices, with detailed answer explaining automatic recycling every 14 days using latest AMI with security patches. Also updated existing answer about replication server provisioning to include security patch details and fixed minor typos.
Security assessment
The change adds documentation about security best practices for replication servers, specifically explaining how the service automatically recycles servers every 14 days to apply security patches. This is a security feature documentation update rather than addressing a specific security vulnerability. The mention of 'security patches and updates' indicates this is preventive security maintenance.
Diff
diff --git a/drs/latest/userguide/Replication-Related-FAQ.md b/drs/latest/userguide/Replication-Related-FAQ.md index 4750ca5a9..adeb1dadd 100644 --- a//drs/latest/userguide/Replication-Related-FAQ.md +++ b//drs/latest/userguide/Replication-Related-FAQ.md @@ -5 +5 @@ -Can we set specific IP addresses for the replication server or conversion server in the AWS DRS staging area?What do Lag and Backlog mean during replication?Is the replicated data encrypted?How is the replication server provisioned and managed in the Staging Area?What type of replication server is utilized in the Elastic Disaster Recovery Staging Area?Does AWS Elastic Disaster Recovery compress data during replication?Are events that are generated by the AWS Elastic Disaster Recovery servers logged in Cloudtrail in AWS?How many snapshots does Elastic Disaster Recovery create?Does Elastic Disaster Recovery delete snapshots?How much capacity is allocated to the staging area?Why is 0.0.0.0:1500 added to inbound rules in the Staging Area?What should I know about rescans?Is the Elastic Disaster Recovery replication crash consistent?How can I perform an SSL connectivity and bandwidth test? +Can we set specific IP addresses for the replication server or conversion server in the AWS DRS staging area?What do Lag and Backlog mean during replication?Is the replicated data encrypted?How is the replication server provisioned and managed in the Staging Area?What type of replication server is utilized in the Elastic Disaster Recovery Staging Area?Does AWS Elastic Disaster Recovery compress data during replication?Are events that are generated by the AWS Elastic Disaster Recovery servers logged in Cloudtrail in AWS?How many snapshots does Elastic Disaster Recovery create?Does Elastic Disaster Recovery delete snapshots?How much capacity is allocated to the staging area?Why is 0.0.0.0:1500 added to inbound rules in the Staging Area?What should I know about rescans?How does AWS Elastic Disaster Recovery ensure that replication servers are patched and follow security best practices?Is the Elastic Disaster Recovery replication crash consistent?How can I perform an SSL connectivity and bandwidth test? @@ -15 +15 @@ You cannot specify or assign static IP addresses for the replication server or c -During replication you may see a server falls out of Continuous Data Protection (CDP) mode. This may occur for various reasons, typically related to the network throughput or interruption. +During replication you may see a server fall out of Continuous Data Protection (CDP) mode. This may occur for various reasons, typically related to the network throughput or interruption. @@ -32 +32 @@ Elastic Disaster Recovery encrypts all the data in transit. -Elastic Disaster Recovery provisions the replication server(s) and automatically manages the addition and removal of the servers as necessary. +AWS Elastic Disaster Recovery automatically provisions replication servers in your staging area subnet when source servers are added. The service manages the full lifecycle of replication servers, including launching new servers when additional replication capacity is needed, removing servers that are no longer in use, and recycling servers every 14 days to ensure they run the latest AMI with up-to-date security patches. Each replication server can handle replication of volumes from multiple source servers. You can configure the replication server instance type and subnet in the [replication settings](./individual-replication-settings.html#replication-server-settings). @@ -73 +73 @@ A volume is created for each volume in the source infrastructure of the same siz -AWS Elastic Disaster Recovery uses TCP Port 1500 for replication between the source agents and the replication server. The connection is open for all IPs and can be managed by ACLs or networks controls to limit inbound IPs. +AWS Elastic Disaster Recovery uses TCP Port 1500 for replication between the source agents and the replication server. The connection is open for all IPs and can be managed by ACLs or network controls to limit inbound IPs. @@ -91,0 +92,4 @@ Causes of rescans include: +## How does AWS Elastic Disaster Recovery ensure that replication servers are patched and follow security best practices? + +AWS Elastic Disaster Recovery automatically recycles replication servers every 14 days. When a replication server reaches the end of its lifecycle, the service terminates it and launches a new replication server using the latest AMI, which includes the most recent security patches and updates. During the recycling process, you may observe temporary replication lag while the new replication server is launched and the AWS Replication Agent reconnects. Replication resumes automatically once the new server is ready. +