chore: rename example notebook and add clarifying comments

Author: BassemHalim

.gitignore

@@ -42,3 +42,4 @@ sagemaker_train/src/**/container_drivers/sourcecode.json
 sagemaker_train/src/**/container_drivers/distributed.json
 .kiro
 docs/api/generated/
+.hypothesis

…-store-lakeformation-cross-account.ipynb …store-lake-formation-cross-account.ipynbv3-examples/ml-ops-examples/v3-feature-store-examples/feature-store-lakeformation-cross-account.ipynb renamed to v3-examples/ml-ops-examples/v3-feature-store-examples/v3-feature-store-lake-formation-cross-account.ipynb v3-examples/ml-ops-examples/v3-feature-store-examples/feature-store-lakeformation-cross-account.ipynb renamed to v3-examples/ml-ops-examples/v3-feature-store-examples/v3-feature-store-lake-formation-cross-account.ipynb

@@ -167,7 +167,9 @@
     "## 1. Create Feature Group in central account and register it with Lake Formation\n",
     "\n",
     "We will create a Feature Group with online and offline store. We will use the execution role as a registration role for Lake Formation for simplicity. \n",
-    "The registration role is the role Lake Formation uses to access your s3 bucket. You also have the option to use a service linked role (SLR). However, an SLR cannot be used with cross-account sharing.\n",
+    "The registration role is the role Lake Formation uses to access your s3 bucket. You also have the option to use a service linked role (SLR). **However, an SLR cannot be used with cross-account credential vending.**\n",
+    "\n",
+    "**Hybrid access mode must also be disabled on Glue Table and Database in order for cross-account credential vending to work**\n",
     "\n",
     "![lakeformation flow](./imgs/lakeformation-flow.png)"
    ]
@@ -220,7 +222,8 @@
     "    enabled=True,\n",
     "    use_service_linked_role=False,\n",
     "    registration_role_arn=acc_to_role_arn[central_account],\n",
-    "    disable_hybrid_access_mode=False\n",
+    "    disable_hybrid_access_mode=True,\n",
+    "    acknowledge_risk=True # You acknowledge that IAM based access to the glue table will stop working\n",
     ")\n",
     "\n",
     "# create FG in central account and enable LF\n",
@@ -501,6 +504,14 @@
     "    print('No pending RAM invitations (may already be accepted)')"
    ]
   },
+  {
+   "cell_type": "markdown",
+   "id": "72073ee9",
+   "metadata": {},
+   "source": [
+    "**Hybrid access mode must be disabled on Glue Table and Database in order for cross-account credential vending to work**"
+   ]
+  },
   {
    "cell_type": "code",
    "execution_count": null,