AWS drs documentation change
Summary
Minor grammatical fixes and clarifications in the documentation for adding EC2 instances as source servers in DRS, including corrections to sentence structure and verb agreement.
Security assessment
The changes are purely grammatical and editorial, correcting phrases like 'allowing to install' to 'allowing you to install' and 'by adding to them' to 'by adding them'. There is no mention of security vulnerabilities, incidents, or new security features. The content about required IAM policies (AmazonSSMManagedInstanceCore and AWSElasticDisasterRecoveryEC2InstancePolicy) is pre-existing and unchanged in substance.
Diff
diff --git a/drs/latest/userguide/adding-servers-from-aws-instances.md b/drs/latest/userguide/adding-servers-from-aws-instances.md index 77d09bccc..16f488976 100644 --- a//drs/latest/userguide/adding-servers-from-aws-instances.md +++ b//drs/latest/userguide/adding-servers-from-aws-instances.md @@ -11 +11 @@ Add instancesSupported EC2 instancesTarget disaster recovery regionInstance prof -You can now add EC2 instances as source servers in DRS, starting from the EC2 console. New or existing instances can be added by selecting the appropriate action on the EC2 console, sending you to the AWS focused page allowing to install the AWS replication agent used by DRS on the selected instances. +You can now add EC2 instances as source servers in DRS, starting from the EC2 console. New or existing instances can be added by selecting the appropriate action on the EC2 console, sending you to the AWS focused page allowing you to install the AWS replication agent used by DRS on the selected instances. @@ -15 +15 @@ You can now add EC2 instances as source servers in DRS, starting from the EC2 co -You can protect your EC2 instances using AWS Elastic Disaster Recovery (DRS) in the chosen AWS Region, by adding to them to AWS DRS as source servers. Utilize AWS Systems Manager (SSM) if present on your instance to install the AWS replication agent, a step needed to start replicating data from your instance to AWS. Only instances managed by AWS Systems Manager would be able to have the AWS replication agent installed on them. +You can protect your EC2 instances using AWS Elastic Disaster Recovery (DRS) in the chosen AWS Region, by adding them to AWS DRS as source servers. Utilize AWS Systems Manager (SSM) if present on your instance to install the AWS replication agent, a step needed to start replicating data from your instance to AWS. Only instances managed by AWS Systems Manager would be able to have the AWS replication agent installed on them. @@ -38 +38 @@ This section lists all the instances that were selected to be protected by AWS D -To have an instance managed by SSM, requires the SSM agent to be installed on a compatible operating system ([or preinstalled in the AMI](https://docs.aws.amazon.com/systems-manager/latest/userguide/ami-preinstalled-agent.html)), and the instance to have the correct permissions (as defined in the [AmazonSSMManagedInstanceCore](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AmazonSSMManagedInstanceCore.html) and the [AWSElasticDisasterRecoveryEC2InstancePolicy](https://docs.aws.amazon.com/drs/latest/userguide/security-iam-awsmanpol-AWSElasticDisasterRecoveryEc2InstancePolicy.html) policies). To update the instance profiles, the **Instance profile role installation** section allows you to create the default instance profile (with the two policies mentioned above) if needed. The **Instance profiles** section allow you to assign instance profiles to instances, and automatically assigns the default instance profile to all instances that do not have any instance profile attached to them. Use the **Attach profiles to all instances** button to attach the assigned instance profiles to the instances in case the default profile was created and automatically assigned to them or if you changed the assigned instance profile. +To have an instance managed by SSM, requires the SSM agent to be installed on a compatible operating system ([or preinstalled in the AMI](https://docs.aws.amazon.com/systems-manager/latest/userguide/ami-preinstalled-agent.html)), and the instance to have the correct permissions (as defined in the [AmazonSSMManagedInstanceCore](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AmazonSSMManagedInstanceCore.html) and the [AWSElasticDisasterRecoveryEC2InstancePolicy](https://docs.aws.amazon.com/drs/latest/userguide/security-iam-awsmanpol-AWSElasticDisasterRecoveryEc2InstancePolicy.html) policies). To update the instance profiles, the **Instance profile role installation** section allows you to create the default instance profile (with the two policies mentioned above) if needed. The **Instance profiles** section allows you to assign instance profiles to instances, and automatically assigns the default instance profile to all instances that do not have any instance profile attached to them. Use the **Attach profiles to all instances** button to attach the assigned instance profiles to the instances in case the default profile was created and automatically assigned to them or if you changed the assigned instance profile.