diff --git a/docs/setup_installation/aws/instance_profile_permissions.md b/docs/setup_installation/aws/instance_profile_permissions.md
index 3be3ad208..caa0430d3 100644
--- a/docs/setup_installation/aws/instance_profile_permissions.md
+++ b/docs/setup_installation/aws/instance_profile_permissions.md
@@ -48,7 +48,8 @@ Replace the following placeholders with their appropiate values
         "arn:aws:ecr:REGION:822623301872:repository/airflow",
         "arn:aws:ecr:REGION:822623301872:repository/git",
         "arn:aws:ecr:REGION:822623301872:repository/testconnector",
-        "arn:aws:ecr:REGION:822623301872:repository/flyingduck"
+        "arn:aws:ecr:REGION:822623301872:repository/flyingduck",
+        "arn:aws:ecr:REGION:822623301872:repository/rdrs"
       ]
     },
     {
@@ -81,7 +82,8 @@ Replace the following placeholders with their appropiate values
         "arn:aws:ecr:REGION:ECR_AWS_ACCOUNT_ID:repository/*/airflow",
         "arn:aws:ecr:REGION:ECR_AWS_ACCOUNT_ID:repository/*/git",
         "arn:aws:ecr:REGION:ECR_AWS_ACCOUNT_ID:repository/*/testconnector",
-        "arn:aws:ecr:REGION:ECR_AWS_ACCOUNT_ID:repository/*/flyingduck"
+        "arn:aws:ecr:REGION:ECR_AWS_ACCOUNT_ID:repository/*/flyingduck",
+        "arn:aws:ecr:REGION:ECR_AWS_ACCOUNT_ID:repository/*/rdrs"
       ]
     },
     {
diff --git a/docs/setup_installation/aws/restrictive_permissions.md b/docs/setup_installation/aws/restrictive_permissions.md
index 6b4b42837..d0d9b085c 100644
--- a/docs/setup_installation/aws/restrictive_permissions.md
+++ b/docs/setup_installation/aws/restrictive_permissions.md
@@ -264,7 +264,7 @@ If you are using terraform, then you can also remove most of the *Describe* perm
 ```
 
 #### Load balancers permissions for external access 
-If you plan to access your Hopsworks cluster from an external python environment, especially if you plan to use the [ArrowFlight with DuckDB](../../common/arrow_flight_duckdb), then it is required to create a network load balancer that forward requests to the ArrowFlight server(s) co-located with the RonDB MySQL Server(s). If you are not planning to use ArrowFlight server(s) or multiple mysql server(s), you can skip adding the following permissions. If you still wish to use the ArrowFlight server(s) but without adding the following permissions to your cross account role, check [this advanced terraform example for more details](https://github.com/logicalclocks/terraform-provider-hopsworksai/tree/main/examples/complete/aws/advanced/arrowflight-no-loadbalancer-permissions).
+If you plan to access your Hopsworks cluster from an external python environment, especially if you plan to use the [ArrowFlight with DuckDB](../../common/arrow_flight_duckdb) and the [Feature Store REST API server](../../../user_guides/fs/feature_view/feature-server), then it is required to create a network load balancer that forward requests to the ArrowFlight server(s) co-located with the RonDB MySQL Server(s). If you are not planning to use ArrowFlight server(s) or multiple mysql server(s), you can skip adding the following permissions. If you still wish to use the ArrowFlight server(s) but without adding the following permissions to your cross account role, check [this advanced terraform example for more details](https://github.com/logicalclocks/terraform-provider-hopsworksai/tree/main/examples/complete/aws/advanced/arrowflight-no-loadbalancer-permissions).
 
 
 ```json