AWS data-exchange medium security documentation change
Summary
Updated subscription verification documentation with expanded details about required subscriber information (including Country of Concern/Covered Person checks), removed EPP provider references, and streamlined console navigation instructions
Security assessment
Added explicit requirement for subscribers to declare if they're from Countries of Concern or Covered Persons, which relates to regulatory compliance and access control. Strengthens documentation about data provider responsibility for PII handling.
Diff
diff --git a/data-exchange/latest/userguide/subscription-verification-pro.md b/data-exchange/latest/userguide/subscription-verification-pro.md index a92f96178..b29ca743c 100644 --- a//data-exchange/latest/userguide/subscription-verification-pro.md +++ b//data-exchange/latest/userguide/subscription-verification-pro.md @@ -11 +11 @@ Effective April 8, 2025, you may not use AWS Data Exchange to provide products c -As a provider, when you create a new public product, you have the option to enable subscription verification on the **Add public offer** section of the **Publish new product** page. +Subscription verification gives you the ability to review a potential subscriber’s identity and approve that subscriber for your product. Approving subscription requests to your product is useful when you have restricted or regulated products, or you have products that you want to limit access to. Subscription verification is on the **Add public offer** section of the **Publish new product** page. @@ -13 +13 @@ As a provider, when you create a new public product, you have the option to enab -Subscription verification gives you the ability to review a potential subscriber’s identity and approve that subscriber for your product. Approving subscription requests to your product can be useful when you have restricted or regulated products, or you have products that you want to limit access to. +Potential subscribers must complete and submit a form for your review. The form requires the following information: @@ -15 +15 @@ Subscription verification gives you the ability to review a potential subscriber -When the verification option is not enabled, you won’t have access to the identity of your subscribers. + * Prospective subscriber's contact details, including contact name, company name, email address, and whether the subscriber is in a Country of Concern or a Covered Person. For more information on this requirement, see the [Publishing guidelines for AWS Data Exchange](./publishing-guidelines.html). @@ -17 +17 @@ When the verification option is not enabled, you won’t have access to the iden -When you turn on the verification option, potential subscribers must complete a form about who they are and what they intend to do with the data before they can subscribe. + * Prospective subscriber's intended use case. @@ -19,7 +19 @@ When you turn on the verification option, potential subscribers must complete a -The form requires the following information: - - * Prospective subscriber's contact details, including contact name, company name, and email address - - * Prospective subscriber's intended use case - - * Prospective subscriber's AWS account ID + * Prospective subscriber's AWS account ID. @@ -32,3 +26 @@ The form requires the following information: -The subscriber must enter information in each field, but AWS Data Exchange doesn't review or validate the information. You're solely responsible for reviewing and verifying the information that the subscriber provides. - -For more information about how to enable subscription verification for your product, see [Publishing a new product in AWS Data Exchange](./publishing-products.html). +AWS Data Exchange doesn't review or validate the information provided by a prospective subscriber on the request form. You are solely responsible for reviewing and verifying the information that the subscriber provides. @@ -36 +28 @@ For more information about how to enable subscription verification for your prod -After you enable subscription verification for your product, you can view, approve, or decline all subscription verification requests for all of your products. Use the **Subscription verification** page under **Publish data** on the AWS Data Exchange console. For more information, see [Approve or decline requests for subscription verification in AWS Data Exchange](./approve-or-decline-requests.html). +To view, approve, or decline all subscription verification requests for all of your products, in the AWS Data Exchange console, under **Published to AWS Marketplace** , choose **Verify subscriptions**. For more information, see [Approve or decline requests for subscription verification in AWS Data Exchange](./approve-or-decline-requests.html). @@ -40,2 +31,0 @@ After you enable subscription verification for your product, you can view, appro -Subscription verification is automatically enabled for all public products from Extended Provider Program (EPP) providers that contain non-public, personal information. - @@ -46,3 +36 @@ If you change the product offer terms after a subscriber makes the request, the -The AWS Data Exchange console maintains a history of requests. You control when you delete the subscriber’s contact details and personally identifiable information (PII). For more information about how to view the request history, see [Viewing subscription verification requests in AWS Data Exchange](./view-requests.html). - -You can also edit the subscription verification option after the product is published. For more information, see [Editing a subscription verification request in AWS Data Exchange](./edit-requests.html). +The AWS Data Exchange console maintains a history of requests. You control when you delete the subscriber’s contact details and personally identifiable information (PII). For more information about how to view the request history, see [Viewing subscription verification requests](./view-requests.html). @@ -58,2 +45,0 @@ The following topics provide more information about subscription verification fo - * [Editing a subscription verification request](./edit-requests.html) -