AWS Security ChangesHomeSearch

AWS connect documentation change

Service: connect · 2026-05-10 · Documentation low

File: connect/latest/adminguide/connect-format-physical-address-e911.md

Summary

Updated terminology from 'Amazon Connect' to 'Connect Customer' throughout the document

Security assessment

Changes are purely branding/terminology updates with no security implications. No vulnerabilities, security features, or security procedures were modified or added.

Diff

diff --git a/connect/latest/adminguide/connect-format-physical-address-e911.md b/connect/latest/adminguide/connect-format-physical-address-e911.md
index 1d5c38543..dca34f361 100644
--- a//connect/latest/adminguide/connect-format-physical-address-e911.md
+++ b//connect/latest/adminguide/connect-format-physical-address-e911.md
@@ -9 +9 @@ Programming notes
-# Format a physical address for E911 to pass to Amazon Connect
+# Format a physical address for E911 to pass to Connect Customer
@@ -11 +11 @@ Programming notes
-This topic explains how to format a physical address so it can be passed to Amazon Connect.
+This topic explains how to format a physical address so it can be passed to Connect Customer.
@@ -13 +13 @@ This topic explains how to format a physical address so it can be passed to Amaz
-E911 outbound calls require a physical address to be passed to Amazon Connect as a JSON string with keys and values that represent the various fields in the address. For example, consider the following US address:
+E911 outbound calls require a physical address to be passed to Connect Customer as a JSON string with keys and values that represent the various fields in the address. For example, consider the following US address:
@@ -51 +51 @@ It is your responsibility to validate the address against a standard repository
-Currently it isn't possible to pass a JSON structure as an `Attribute` to Amazon Connect. Therefore, the location retrieved by the Lambda function needs to be converted to a JSON string before it is passed to Amazon Connect. For example, using the Python programming language, if the location retrieved is stored in a JSON structure `json_agent_location` then it can be passed to Amazon Connect (from the Lambda function) as follows:
+Currently it isn't possible to pass a JSON structure as an `Attribute` to Connect Customer. Therefore, the location retrieved by the Lambda function needs to be converted to a JSON string before it is passed to Connect Customer. For example, using the Python programming language, if the location retrieved is stored in a JSON structure `json_agent_location` then it can be passed to Connect Customer (from the Lambda function) as follows:
@@ -66 +66 @@ The key-value pair:
-And the corresponding JSON string that is actually passed to Amazon Connect:
+And the corresponding JSON string that is actually passed to Connect Customer: