AWS mgn documentation change
Summary
Removed section 'Missing Amazon Linux 2023 repository configuration' which was redundant after similar content was added to Troubleshooting-Communication-Errors.md
Security assessment
This is a content reorganization change with no security implications. Removal of documentation doesn't indicate resolution of security issues.
Diff
diff --git a/mgn/latest/ug/common-replication-errors.md b/mgn/latest/ug/common-replication-errors.md index bd2e5298a..547bf0938 100644 --- a//mgn/latest/ug/common-replication-errors.md +++ b//mgn/latest/ug/common-replication-errors.md @@ -7 +7 @@ -Agent not seenNot convergingSnapshot failureUnstable networkFailed to connect AWS replication Agent to replication softwareFailed to establish communication with replication softwareFailed to create firewall rulesFailed to authenticate with serviceFailed to create staging disksReplication stuck at Attach Staging DisksFailed to pair the replication agent with replication serverStalled replication when replicating a source volume smaller than 1MiBUnknown data replication errorMissing Amazon Linux 2023 repository configuration +Agent not seenNot convergingSnapshot failureUnstable networkFailed to connect AWS replication Agent to replication softwareFailed to establish communication with replication softwareFailed to create firewall rulesFailed to authenticate with serviceFailed to create staging disksReplication stuck at Attach Staging DisksFailed to pair the replication agent with replication serverStalled replication when replicating a source volume smaller than 1MiBUnknown data replication error @@ -43,2 +42,0 @@ This section describes common replication errors, possible explanations, and pot - * Missing Amazon Linux 2023 repository configuration - @@ -183,28 +180,0 @@ Unknown errors (unknown_error) can occur for any number of reasons. There are se -## Missing Amazon Linux 2023 repository configuration - -Replication servers use Amazon Linux 2023 (AL2023) and require access to the AL2023 package repository hosted in Amazon S3. If the staging area subnet does not have outbound internet access and the Amazon S3 VPC gateway endpoint policy does not allow access to the AL2023 repository bucket, replication servers may fail to launch or function correctly. - -Symptoms of this issue include: - - * Replication stalling or failing after the replication server is launched. - - * Replication server unable to install or update required packages. - - - - -To resolve this issue: - - 1. Ensure that the Amazon S3 VPC gateway endpoint policy associated with your staging area subnet allows access to the AL2023 package repository bucket (`al2023-repos-<REGION>-de612dc2`). Add the following resource ARN to the endpoint policy: - - "arn:aws:s3:::al2023-repos-<REGION>-de612dc2/*" - - 2. If you use a firewall or proxy, allowlist the following Amazon S3 URL: - - https://al2023-repos-<REGION>-de612dc2.s3.<REGION>.amazonaws.com/ - - - - -For the complete list of Amazon S3 buckets required by AWS Application Migration Service, including the example Amazon S3 VPC endpoint policy, see [Network requirements](./preparing-environments.html). -