AWS data-exchange documentation change
Summary
Updated subscription verification process documentation with clarified form fields and automatic AWS account ID population
Security assessment
Changes focus on form field reorganization and process clarification without mentioning security vulnerabilities or new security controls
Diff
diff --git a/data-exchange/latest/userguide/complete-sub-request.md b/data-exchange/latest/userguide/complete-sub-request.md index 7063c7ef7..6a24dabbf 100644 --- a//data-exchange/latest/userguide/complete-sub-request.md +++ b//data-exchange/latest/userguide/complete-sub-request.md @@ -7 +7 @@ -For AWS Data Exchange products that require subscription verification, when you choose **Continue to subscribe** on a product page, a **Complete subscription request** page appears. You must complete the request before you can subscribe to this product. +AWS Data Exchange public products require subscription verification. After choosing **Continue to subscribe** , you must complete an additional form on the **Complete subscription request** page. @@ -17 +17 @@ For AWS Data Exchange products that require subscription verification, when you - 4. Complete the **Subscription request form** with the following information: + 4. On the **Subscription request form** , your AWS account ID will be added automatically. Complete the form by completing the following fields: @@ -19 +19 @@ For AWS Data Exchange products that require subscription verification, when you - * Your AWS account ID (added automatically) + * **Company name** @@ -21 +21 @@ For AWS Data Exchange products that require subscription verification, when you - * Your **Company name** + * **Name** @@ -23 +23 @@ For AWS Data Exchange products that require subscription verification, when you - * Your **Name** + * **Email address** @@ -25 +25 @@ For AWS Data Exchange products that require subscription verification, when you - * Your **Email address** + * **Company location** @@ -27 +27,3 @@ For AWS Data Exchange products that require subscription verification, when you - * Your **Intended use case** for the data product, along with any other comments that the provider might find useful when reviewing the subscription request + * **Intended use case** + +In addition to your proposed use case, you may include additional comments that could help the provider evaluate your request.