AWS iot-mi medium security documentation change
Summary
Added note about CreateAccountAssociation API OAuth requirements and VPC endpoint limitations.
Security assessment
Explicitly documents security-relevant network containment limitations (AWS PrivateLink incompatibility with OAuth flows) that could impact traffic security architecture.
Diff
diff --git a/iot-mi/latest/devguide/vpc-endpoints-limitations.md b/iot-mi/latest/devguide/vpc-endpoints-limitations.md index a6bffcb30..ee70f3494 100644 --- a//iot-mi/latest/devguide/vpc-endpoints-limitations.md +++ b//iot-mi/latest/devguide/vpc-endpoints-limitations.md @@ -5,2 +4,0 @@ -Managed integrations for AWS IoT Device Management is in preview release and is subject to change. For access, contact us from the [managed integrations console](https://console.aws.amazon.com/iot/home#/managed-integrations/intro). - @@ -9 +7,6 @@ Managed integrations for AWS IoT Device Management is in preview release and is -VPC endpoints for AWS IoT Managed integrations are not available in AWS GovCloud (US) Regions. + * The [CreateAccountAssociation](https://docs.aws.amazon.com/iot-mi/latest/APIReference/API_CreateAccountAssociation.html) API, is designed to perform OAuth with third-party cloud services, which requires the request to leave the Amazon network. This is important for customers using AWS PrivateLink to contain their traffic within the VPC, as AWS PrivateLink cannot provide complete end-to-end containment for this API call. + + * VPC endpoints for AWS IoT Managed integrations are not available in AWS GovCloud (US) Regions. + + + @@ -21 +24 @@ Pricing -Monitoring +Connect to managed integrations for AWS IoT Device Management FIPS endpoints