DOCSP-17300 ADL should not need to list a bucket to save a config (#171)

* DOCSP-17300 ADL should not need to list a bucket to save a config

* DOCSP-17300 updates for copy review feedback

Author: kanchana-mongodb

source/includes/steps-deploy-s3-json-editor.yaml

@@ -24,7 +24,7 @@ content: |
      :language: json
 
   To learn more about these configuration settings, see 
-  :ref:`datalake-stores-reference`.
+  :ref:`datalake-databases-reference`.
 ---
 title: "Repeat steps 1 and 2 in the |json| Editor tab above to define 
        additional |aws| |s3| data stores and virtual databases, 
@@ -42,8 +42,22 @@ content: |
 
    - :ref:`federated-queries`  
    - :ref:`federated-config-eg`
+
 ---
 title: "Click :guilabel:`Save` to create the {+dl+}."
 level: 4
-ref: save-s3-json-configuration
+ref: save-configuration
+content: | 
+
+  .. note:: 
+
+     If {+adl+} is unable to read the specified |s3| bucket, it 
+     displays a modal to: 
+
+     - :guilabel:`Cancel` this operation and specify a different |iam| 
+       role to retrieve the object metadata from the specified |s3| 
+       bucket. 
+     - :guilabel:`Use Role Anyway` to create the {+dl+} for the 
+       specified bucket using the specified |iam| role. 
+       
 ...

source/includes/steps-deploy-s3-visual-editor.yaml

@@ -37,7 +37,10 @@ content: |
      In the |service| UI, click and expand one of the following:
 
      - The :guilabel:`Create New Role with the AWS CLI` shows how to 
-       use the |arn| and the unique External ID to add |service| to the trust relationships of a new |aws| |iam| role. Follow the steps in the |service| UI for creating a new role. To learn more, see  :atlas:`Create New Role with the AWS CLI 
+       use the |arn| and the unique External ID to add |service| to the 
+       trust relationships of a new |aws| |iam| role. Follow the steps 
+       in the |service| UI for creating a new role. To learn more, see  
+       :atlas:`Create New Role with the AWS CLI 
        </security/set-up-unified-aws-access/#procedure>`. 
 
        When authorizing a new role, if you quit the ``Configure a New 
@@ -51,7 +54,7 @@ content: |
          the workflow when you have the |aws| IAM role |arn|.
        - After validating the role, |service| will not create the 
          {+dl+}. However, the role is available in the role selection 
-         drop-down and can be used to create a {+dl+}. You do not need 
+         dropdown and can be used to create a {+dl+}. You do not need 
          to authorize the role again. 
 
      - The :guilabel:`Add Trust Relationships to an Existing Role` 
@@ -106,6 +109,11 @@ content: |
 
      Corresponds to :datalakeconf:`stores.[n].region` |json| 
      configuration setting.
+
+     .. note::
+
+        You can't create a {+dl+} if {+adl+} is unable to retrieve the  
+        region of the specified |s3| bucket.
   
   #. **Optional**. Specify a prefix that {+dl+} should use when 
      searching the files in the |s3| bucket. If omitted, {+dl+} 
@@ -222,4 +230,17 @@ content: |
 title: "Click :guilabel:`Save` to create the {+dl+}."
 level: 4
 ref: save-configuration
+content: | 
+
+  .. note:: 
+
+     If {+adl+} is unable to read the specified |s3| bucket, it 
+     displays a modal to: 
+
+     - :guilabel:`Cancel` this operation and specify a different |iam| 
+       role to retrieve the object metadata from the specified |s3| 
+       bucket. 
+     - :guilabel:`Use Role Anyway` to create the {+dl+} for the 
+       specified bucket using the specified |iam| role. 
+       
 ...