Merge pull request #2928 from port-labs/PORTN-123-rename-old-aws-to-aws-on-prem-2

docs: update AWS integration references to "AWS On-Premise" for consistency across documentation

Author: sivanel97

docs/build-your-software-catalog/sync-data-to-catalog/cloud-providers/aws-v3/Overview.md

@@ -35,7 +35,7 @@ We're actively working on adding support for additional AWS resource types to pr
 
 ## Key advantages
 
-AWS Hosted by Port provides several advantages over the [self-hosted AWS integration](/build-your-software-catalog/sync-data-to-catalog/cloud-providers/aws/installations/installation.md):
+AWS Hosted by Port provides several advantages over the [AWS on-premise integration](/build-your-software-catalog/sync-data-to-catalog/cloud-providers/aws/installations/installation.md):
 
 - **Fully hosted**: No infrastructure to maintain, update, or monitor.
 - **Simplified installation**: Just deploy CloudFormation templates to create IAM roles.

docs/build-your-software-catalog/sync-data-to-catalog/cloud-providers/aws/_category_.json

@@ -1,4 +1,4 @@
 {
-  "label": "AWS",
+  "label": "AWS on-premise",
   "position": 11
 }

docs/build-your-software-catalog/sync-data-to-catalog/cloud-providers/aws/aws.md

@@ -7,9 +7,9 @@ import TabItem from "@theme/TabItem";
 import Image from "@theme/IdealImage";
 import MetricsAndSyncStatus from "/docs/build-your-software-catalog/sync-data-to-catalog/templates/_metrics_and_sync_status.mdx"
 
-# AWS
+# AWS on-premise
 
-Port's AWS integration allows you to import your AWS resources into Port, according to your configuration.  
+Port's AWS on-premise integration allows you to import your AWS resources into Port, according to your configuration.  
 After the initial import of data, the integration will also listen to live events from AWS to update data in Port in real time.
 
 The integration with AWS supports real-time event processing, which allows for an accurate **real-time** representation of your AWS infrastructure inside Port.
@@ -18,7 +18,7 @@ The integration with AWS supports real-time event processing, which allows for a
 Port's AWS integration is open source, view the source code [**here**](https://github.com/port-labs/ocean/tree/main/integrations/aws).
 :::
 
-## 💡 AWS integration common use cases
+## 💡 AWS on-premise integration common use cases
 
 Easily fill your software catalog with data directly from your AWS Organization, for example:
 
@@ -34,7 +34,7 @@ The AWS integration allows you to perform extract, transform, load (ETL) on data
 
 ## Getting started
 
-Continue to the [installation](./installations/installation.md) guide to learn how to install the AWS integration.
+Continue to the [installation](./installations/installation.md) guide to learn how to install the AWS on-premise integration.
 
 ## Multiple accounts support
 
@@ -48,7 +48,7 @@ The mapping makes use of the [JQ JSON processor](https://stedolan.github.io/jq/m
 
 ### Default mapping configuration
 
-This is the default mapping configuration you get after installing the AWS integration.
+This is the default mapping configuration you get after installing the AWS on-premise integration.
 
 <details>
 <summary><b>Default mapping configuration (Click to expand)</b></summary>

docs/build-your-software-catalog/sync-data-to-catalog/cloud-providers/aws/installations/installation.md

@@ -11,7 +11,7 @@ import IntegrationVersion from "/src/components/IntegrationVersion/IntegrationVe
 ## Permissions
 
 - To get Port API credentials, you check out the [Port API documentation](/build-your-software-catalog/custom-integration/api/#find-your-port-credentials).
-- In order to successfully deploy the AWS integration, it's crucial to ensure that the user who deploys the integration in the AWS Organization has the appropriate access permissions to create all of the relevant resources (ECS, IAM, and VPC).
+- In order to successfully deploy the AWS on-premise integration, it's crucial to ensure that the user who deploys the integration in the AWS Organization has the appropriate access permissions to create all of the relevant resources (ECS, IAM, and VPC).
 
 :::tip Multiple Account Support
 To do the following:
@@ -29,7 +29,7 @@ Choose one of the following installation methods:
 
 <IntegrationVersion integration="aws" />
 
-The AWS integration is deployed using Helm on you cluster.
+The AWS on-premise integration is deployed using Helm on you cluster.
 You can check out the Helm chart [here](https://github.com/port-labs/helm-charts/tree/main/charts/port-ocean).
 
 ## Prerequisites

docs/build-your-software-catalog/sync-data-to-catalog/cloud-providers/aws/installations/multi_account.md

@@ -6,7 +6,7 @@ import CenterRoundedImage from "/src/components/CenterRoundedImage/index.jsx";
 
 # Multi account support
 
-This guide will provide you with the necessary tools for enabling our Ocean AWS Integration to digest multiple account's data.
+This guide will provide you with the necessary tools for enabling our Ocean AWS on-premise Integration to digest multiple account's data.
 
 ## Prerequisites