diff --git a/content/operate/rc/security/aws-privatelink.md b/content/operate/rc/security/aws-privatelink.md
index 26e69cadf0..6e95cb1ee2 100644
--- a/content/operate/rc/security/aws-privatelink.md
+++ b/content/operate/rc/security/aws-privatelink.md
@@ -24,6 +24,8 @@ AWS PrivateLink provides the following benefits:
 - **Network Flexibility**: PrivateLink enables cross-account and cross-VPC connectivity and can be configured even when the Redis Cloud VPC and your consumer VPC have overlapping CIDR/IP ranges.
 - **Simplified architecture and low latency**: PrivateLink does not require NAT, internet gateways, or VPNs. It provides simplified network routing, without the need for a network load balancer between the application and the Redis database.
 
+See [Connecting to Redis Cloud with AWS PrivateLink vs. VPC Peering](https://redis.io/blog/connecting-to-redis-cloud-with-aws-privatelink-vs-vpc-peering/) to learn more about the benefits of using AWS PrivateLink to connect to Redis Cloud.
+
 {{< video-link >}}
 See [Connect to Redis Cloud with AWS PrivateLink](https://www.youtube.com/watch?v=i3aTmcyFihY) for a short video tutorial on how to connect to Redis Cloud with AWS PrivateLink.
 {{< /video-link >}}
@@ -72,7 +74,7 @@ In this step, you will associate the Redis Cloud resource share with an AWS Acco
 
 1. From the [Redis Cloud console](https://cloud.redis.io/), select the **Subscriptions** menu and then select your subscription from the list.
 
-1. Select **Connectivity > PrivateLink** to view the PrivateLink settings.
+1. Select **Connectivity > PrivateLink** to view the PrivateLink settings. If you haven't set up AWS PrivateLink before, select **Set up PrivateLink**. 
 
 1. In the **Resource Share** section, select **Manage Principals** to open the **Manage Principals** window.
 
@@ -84,7 +86,7 @@ In this step, you will associate the Redis Cloud resource share with an AWS Acco
 
     {{<image filename="images/rc/icon-add.png" width="30px" alt="The Add button adds principals to the resource share." >}}
 
-1. Enter the account's ID in the **Principal ID** field. You can also add an optional alias in the **AWS principal alias** field.
+1. Enter the account's ID in the **AWS Account** field. You can also add an optional alias in the **AWS principal alias** field.
 
     {{<image filename="images/rc/privatelink-aws-consumer-principals.png" width="80%" alt="The AWS consumer principals section with an AWS account added as a principal." >}}
 
diff --git a/static/images/rc/privatelink-aws-consumer-principals.png b/static/images/rc/privatelink-aws-consumer-principals.png
index 6b0e9acb15..179591363e 100644
Binary files a/static/images/rc/privatelink-aws-consumer-principals.png and b/static/images/rc/privatelink-aws-consumer-principals.png differ
diff --git a/static/images/rc/privatelink-manage-principals.png b/static/images/rc/privatelink-manage-principals.png
index 584306b911..11cca1d7c7 100644
Binary files a/static/images/rc/privatelink-manage-principals.png and b/static/images/rc/privatelink-manage-principals.png differ
diff --git a/static/images/rc/privatelink-principal-accepted.png b/static/images/rc/privatelink-principal-accepted.png
index 52354107b7..0310d0d3a5 100644
Binary files a/static/images/rc/privatelink-principal-accepted.png and b/static/images/rc/privatelink-principal-accepted.png differ