AWS sap documentation change
Summary
Removed a sentence about compliance/security requirements for DNS and corrected 'AWS-hosed' to 'AWS-hosted'.
Security assessment
Sentence removal discusses compliance/security but doesn't indicate a vulnerability fix. Typo fix has no security impact. No evidence of addressing a specific security weakness.
Diff
diff --git a/sap/latest/general/rise-dns.md b/sap/latest/general/rise-dns.md index bd88aefcb..c0e063edb 100644 --- a//sap/latest/general/rise-dns.md +++ b//sap/latest/general/rise-dns.md @@ -13 +13 @@ A bi-directional DNS integration is essential for connecting RISE with SAP syste -Conversely, external systems and applications usually require a DNS lookup to access resources in the RISE with SAP environment, particularly when calling ODATA API endpoints to execute business transactions such as generating a work orders. Integration scenarios between RISE with SAP systems and existing enterprise systems typically require internal network connectivity due to compliance and security requirements. This is particularly true for RISE with SAP deployments, which is why the following sections focus on DNS resolution within private networks. +Conversely, external systems and applications usually require a DNS lookup to access resources in the RISE with SAP environment, particularly when calling ODATA API endpoints to execute business transactions such as generating a work orders. @@ -103 +103 @@ The following diagram shows a reference architecture for integrating the RISE en - 2. AWS-bound DNS queries: Zone transfer of aws.<customer>.<domain> from AWS-hosed DNS server + 2. AWS-bound DNS queries: Zone transfer of aws.<customer>.<domain> from AWS-hosted DNS server