AWS guidance documentation change
Summary
Removed 'GPS injection' from the table of contents and deleted the entire GPS injection section that explained how GPS coordinates are obtained and injected in simulation and production modes.
Security assessment
This change removes technical implementation details about GPS data handling but doesn't indicate any security vulnerability. The removal could be part of documentation simplification or feature deprecation, but there's no evidence of security concerns being addressed.
Diff
diff --git a/guidance/latest/connected-mobility-on-aws/fleetwise-edge-integration.md b/guidance/latest/connected-mobility-on-aws/fleetwise-edge-integration.md index 7d853baae..0ffd649b5 100644 --- a//guidance/latest/connected-mobility-on-aws/fleetwise-edge-integration.md +++ b//guidance/latest/connected-mobility-on-aws/fleetwise-edge-integration.md @@ -3 +3 @@ -Agent lifecycleCampaign statesProtobuf decode processGPS injection +Agent lifecycleCampaign statesProtobuf decode process @@ -83,4 +82,0 @@ Failed decodes are dropped (not passed through as poison messages) and counted i -## GPS injection - -GPS coordinates are not available on the CAN bus — they come from a separate interface. In simulation mode, the simulator injects GPS coordinates into the FWE agent through a Unix domain socket. The agent includes these coordinates in its protobuf upload alongside the CAN signals. In production, the FWE agent can be configured to read GPS from a serial device, a network source, or an external GPS module. -