S3-based connectors: S3 operation latency warning note (#706)

Author: Paul-Cornell

snippets/general-shared-text/delta-table.mdx

@@ -10,6 +10,10 @@ allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; pic
 allowfullscreen
 ></iframe>
 
+import S3OperationLatency from '/snippets/general-shared-text/s3-operation-latency.mdx';
+
+<S3OperationLatency />
+
 The preceding video does not show how to create an AWS account. 
 
 For more information about requirements, see the following:

snippets/general-shared-text/s3-operation-latency.mdx

@@ -0,0 +1,9 @@
+<Warning>
+    If you are experiencing S3 connector or workflow failures after adding a new S3 bucket or updating an existing S3 bucket, 
+    it could be due to S3 latency issues. You might need to wait up to a few hours before any related S3 connectors 
+    and workflows begin working without failures.
+
+    Various Amazon S3 operations such as propagating DNS records for new buckets, updating bucket access policies and 
+    permissions, reusing bucket names after deletion, and using AWS Regions that are not geographically closer 
+    to your users or applications, can take a few minutes to hours to fully propagate across the Amazon network. 
+</Warning>

snippets/general-shared-text/s3.mdx

@@ -10,6 +10,10 @@ allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; pic
 allowfullscreen
 ></iframe>
 
+import S3OperationLatency from '/snippets/general-shared-text/s3-operation-latency.mdx';
+
+<S3OperationLatency />
+
 The preceding video does not show how to create an AWS account; enable anonymous access to the bucket (which is supported but 
 not recommended); or generate AWS STS temporary access credentials if required by your organization's security 
 requirements. For more information about requirements, see the following: