Merge branch 'DOC-761' of https://github.com/arangodb/docs-hugo into DOC-761

Author: Simran-B

site/content/ai-suite/graphml/quickstart.md

@@ -53,7 +53,6 @@ with the Arango team.
   - Metadata capture
   - Model management
 
-![ArangoGraphML Pipeline](../../images/ArangoGraphML_Pipeline.png)
 {{< /tab >}}
 
 {{< /tabs >}}

site/content/amp/api/get-started.md

@@ -38,16 +38,14 @@ key you will need to be signed into your account at
 [dashboard.arangodb.cloud](https://dashboard.arangodb.cloud/home?utm_source=docs&utm_medium=cluster_pages&utm_campaign=docs_traffic).
 Once you are signed in, hover over the profile icon in the top right corner.
 
-![Profile Icon](../../images/arangograph-my-account-hover.png)
-
 Click _My API keys_.
 
 This will bring you to your API key management screen. From this screen you can
 create, reject, and delete API keys.
 
 Click the _New API key_ button.
 
-![Blank API Screen](../../images/arangograph-my-api-keys.png)
+![Blank API Screen](../../images/amp-api-keys.png)
 
 The pop-up box that follows has a few options for customizing the access level
 of this API key.
@@ -63,8 +61,6 @@ your API key ID and API key secret. It is very important that you capture the
 API key secret before clicking the close button. There is no way to retrieve
 the API key secret after closing this pop-up window.
 
-![API Secret Key](../../images/arangograph-api-key-secret.png)
-
 Once you have securely stored your API key ID and secret, click close.
 
 That is all there is to setting up API access to your AMP organizations.

site/content/amp/backups.md

@@ -11,8 +11,6 @@ description: >-
 To backup data in AMP for an ArangoDB installation, navigate to the
 **Backups** section of your deployment created previously.
 
-![Backup ArangoDB](../images/arangograph-backup-section.png)
-
 There are two ways to create backups. Create periodic backups using a
 **Backup policy**, or create a backup manually.
 Both ways allow you to create [backups in multiple regions](#multi-region-backups)
@@ -23,13 +21,13 @@ as well.
 Periodic backups are created at a given schedule. To see when the new backup is
 due, observe the schedule section.
 
-![Backup Policy schedule](../images/arangograph-backup-policy-schedule.png)
+![Arango Managed Platform Backup Policy schedule](../images/amp-backup-policy-schedule.png)
 
 When a new deployment is created, a default **Backup policy** is created for it
 as well. This policy creates backups every two hours. To edit this policy
 (or any policy), highlight it in the row above and hit the pencil icon.
 
-![Edit Backup Policy](../images/arangograph-edit-backup-policy.png)
+![Arango Managed Platform Edit Backup Policy](../images/amp-edit-backup-policy.png)
 
 These backups are not automatically uploaded. To enable this, use the
 **Upload backup to storage** option and choose a retention period that
@@ -44,9 +42,9 @@ The regions where the default backup is copied are shown in the
 
 It's also possible to create a backup on demand. To do this, click **Back up now**.
 
-![Back up Now](../images/arangograph-back-up-now.png)
+![Arango Managed Platform Back up Now](../images/amp-back-up-now.png)
 
-![Back up Now Dialog](../images/arangograph-back-up-now-dialog.png)
+![Arango Managed Platform Back up Now Dialog](../images/amp-back-up-now-dialog.png)
 
 If you want to manually copy a backup to a different region than the default
 one, first ensure that the **Upload backup to storage** option is enabled.
@@ -56,9 +54,7 @@ Then, highlight the backup row and use the
 The source backup ID from
 which the copy is created is displayed in the **Copied from Backup** column.
 
-![Copy backup to a different region](../images/arangograph-copy-backup-different-region.png)
-
-![Multiple Backups](../images/arangograph-multiple-backups.png)
+![Arango Managed Platform Copy backup to a different region](../images/amp-copy-backup-different-region.png)
 
 ### Uploading backups
 
@@ -110,7 +106,7 @@ regions, significantly improving reliability.
 Multiple region backup is only available when the
 **Upload backup to cloud storage** option is enabled.
 
-![Multiple Region Backup](../images/arangograph-multi-region-backup.png)
+![Arango Managed Platform Multiple Region Backup](../images/amp-multi-region-backup.png)
 
 ## How to restore backups
 
@@ -124,13 +120,7 @@ backup before using the **Restore Backup** feature.
 During restore, the deployment is temporarily not available.
 {{< /warning >}}
 
-![Restore From Backup](../images/arangograph-restore-from-backup.png)
-
-![Restore From Backup Dialog](../images/arangograph-restore-from-backup-dialog.png)
-
-![Restore From Backup Status Pending](../images/arangograph-restore-from-backup-status-pending.png)
-
-![Restore From Backup Status Restored](../images/arangograph-restore-from-backup-status-restored.png)
+![Arango Managed Platform Restore From Backup](../images/amp-restore-from-backup.png)
 
 ## How to clone deployments using backups
 
@@ -157,16 +147,10 @@ The *root password* for this deployment will be different.
 
 1. Highlight the backup you wish to clone from and hit **Clone backup to new deployment**.
 
-   ![ArangoGraph Clone Deployment From Backup](../images/arangograph-clone-deployment-from-backup.png)
-
 2. Choose whether the clone should be created using the current provider and in
    the same region as the backup or using a different provider, a different region,
    or both.
 
-   ![ArangoGraph Clone Deployment Select Region](../images/arangograph-clone-deployment-select.png) 
-
 3. The view should navigate to the new deployment being bootstrapped.
 
-   ![ArangoGraph Cloned Deployment](../images/arangograph-cloned-deployment.png)
-
 This feature is also available through [oasisctl](oasisctl/_index.md).

site/content/amp/data-loader/_index.md

@@ -57,6 +57,4 @@ get the ArangoDB client tools for your operating system from the
 1. If you do not have a deployment yet, [create a deployment](../deployments/_index.md#how-to-create-a-new-deployment) first.
 2. Open the deployment you want to load data into.
 3. In the **Load Data** section, click the **Load your data** button.
-4. Select your migration use case.
-
-![ArangoGraph Data Loader Migration Use Cases](../../images/arangograph-data-loader-migration-use-cases.png)
+4. Select your migration use case.

site/content/amp/data-loader/add-files.md

@@ -17,7 +17,7 @@ You can upload your CSV files in the following ways:
 - Drag and drop your files in the designated area.
 - Click the **Browse files** button and select the files you want to add.
 
-![ArangoGraph Data Loader Upload Files](../../images/arangograph-data-loader-upload-files.png)
+![Data Loader Upload Files](../../images/amp-data-loader-upload-files.png)
 
 You have the option to either upload several files collectively as a batch or
 add them individually. Furthermore, you can supplement additional files later on.

site/content/amp/data-loader/design-graph.md

@@ -26,7 +26,7 @@ objects.
    reference the nodes when you define relations with edges.
    - For **File Headers**, select one or more attributes from the list.
 
-![ArangoGraph Data Loader Add Node](../../images/arangograph-data-loader-add-node.png)
+![Data Loader Add Node](../../images/amp-data-loader-add-node.png)
 
 ## How to connect nodes
 
@@ -60,7 +60,7 @@ See below the steps to add details to an edge.
    destination file (`_to`).
    - For **File Headers**, select one or more attributes from the list.
 
-![ArangoGraph Data Loader Edit Edge](../../images/arangograph-data-loader-edit-edge.png)
+![Data Loader Edit Edge](../../images/amp-data-loader-edit-edge.png)
 
 ## How to delete elements
 

site/content/amp/data-loader/example.md

@@ -36,14 +36,12 @@ The whole process can be broken down into these steps:
 
 Start by creating a new database and adding a name for your graph.
 
-![Data Loader Example Step 1](../../images/arangograph-data-loader-example-choose-names.png)
-
 ## Step 2: Add files
 
 Upload your CSV files to the Data Loader web interface. You can drag and drop
 them or upload them via a file browser window.
 
-![Data Loader Example Step 2](../../images/arangograph-data-loader-example-add-files.png)
+![Data Loader Example Step 2](../../images/amp-data-loader-example-add-files.png)
 
 See also [Add files into Data Loader](../data-loader/add-files.md).
 
@@ -69,15 +67,15 @@ In this example, two node collections have been created (`origin_airport` and
 attribute for documents in both node collections. The header preview makes it
 easy to select the headers you want to use.
 
-![Data Loader Example Step 3 Nodes](../../images/arangograph-data-loader-example-map-nodes.png)
+![Data Loader Example Step 3 Nodes](../../images/amp-data-loader-example-map-nodes.png)
 
 For edges, the **Edge label** is going to be an edge collection name. Then, you
 need to specify how edges will connect nodes. You can do this by selecting the
 *from* and *to* nodes to give a direction to the edge.
 In this example, the `source airport` header has been selected as a source and
 the `destination airport` header as a target for the edge.
 
-![Data Loader Example Step 3 Edges](../../images/arangograph-data-loader-example-map-edges.png)
+![Data Loader Example Step 3 Edges](../../images/amp-data-loader-example-map-edges.png)
 
 Note that the values of the source and target for the edge correspond to the
 **Primary identifier** (`_key` attribute) of the nodes. In this case, it is the
@@ -93,11 +91,11 @@ After all the mapping is done, all you need to do is click
 processed and the documents created, as well as a link to your new graph.
 See also [Start import](../data-loader/import.md).
 
-![Data Loader Example Step 4 See your new graph](../../images/arangograph-data-loader-example-data-import.png)
+![Data Loader Example Step 4 See your new graph](../../images/amp-data-loader-example-data-import.png)
 
 Finally, click **See your new graph** to open the ArangoDB web interface and
 explore your new collections and graph.
 
-![Data Loader Example Step 4 Resulting graph](../../images/arangograph-data-loader-example-resulting-graph.png)
+![Data Loader Example Step 4 Resulting graph](../../images/amp-data-loader-example-resulting-graph.png)
 
 Happy graphing!

site/content/amp/deployments/_index.md

@@ -13,8 +13,6 @@ You can have any number of deployments under one project.
 
 **Organizations → Projects → <u>Deployments</u>**
 
-![ArangoGraph Deployments](../../images/arangograph-deployments-page.png)
-
 ## How to create a new deployment
 
 1. If you do not have a project yet,
@@ -24,6 +22,8 @@ You can have any number of deployments under one project.
 4. Select the project you want to create the deployment for.
 5. Set up your deployment. The configuration options are described below.
 
+![Arango Managed Platform New Deployment Overview](../../images/amp-new-deployment.png)
+
 {{< info >}}
 Deployments contain exactly **one policy**. Within that policy, you can define
 role bindings to regulate access control on a deployment level.
@@ -38,7 +38,7 @@ role bindings to regulate access control on a deployment level.
   provider and region anymore.
   {{< /warning >}}
 
-![ArangoGraph New Deployment General](../../images/arangograph-new-deployment-general.png)
+![Arango Managed Platform New Deployment general](../../images/amp-new-deployment-general.png)
 
 ### In the **Sizing** section
 
@@ -60,7 +60,7 @@ role bindings to regulate access control on a deployment level.
 - Select a __NODE SIZE__ from the list of available options. Each option is a
   combination of vCPUs, memory, and disk space per node.
 
-![ArangoGraph New Deployment Sizing](../../images/arangograph-new-deployment-sizing.png)
+![Arango Managed Platform New Deployment Sizing](../../images/amp-new-deployment-sizing.png)
 
 ### In the **Advanced** section
 
@@ -84,7 +84,7 @@ role bindings to regulate access control on a deployment level.
   {{< /security >}}
 - Select a __Deployment Profile__. Profile options are only available on request.
 
-![ArangoGraph New Deployment Advanced](../../images/arangograph-new-deployment-advanced.png)
+![Arango Managed Platform New Deployment Advanced](../../images/amp-new-deployment-advanced.png)
 
 ### In the **Summary** panel
 
@@ -161,7 +161,7 @@ periodically to improve security.
 3. In the __Password Settings__ dialog, turn the automatic password rotation on
    and click the __Save__ button.
 
-   ![ArangoGraph Deployment Password Rotation](../../images/arangograph-deployment-password-rotation.png)
+   ![Arango Managed Platform Deployment Password Rotation](../../images/amp-deployment-password-rotation.png)
 4. You can expand the __Root password__ panel to see when the password was
    rotated last. The rotation takes place every three months.
 
@@ -290,25 +290,7 @@ configuration. To achieve the best possible availability, your client
 application has to handle connection failures by retrying operations if needed.
 {{< /tip >}}
 
-![ArangoGraph Connecting Drivers Example](../../images/arangograph-connecting-drivers-example.png)
-
-## How to pause a deployment
-
-1. In the __Deployments__ page, click the deployment you wish to pause.
-2. Click the __Delete/Lock__ entry in the navigation.
-3. Click the __Pause deployment...__ button.
-4. To resume the deployment, go to the __Overview__ tab and click __Resume deployment__. The
-   deployment being paused displays the __Hibernated__ status until it has been
-   successfully resumed.
-
-## How to pause a deployment
-
-1. In the __Deployments__ page, click the deployment you wish to pause.
-2. Click the __Delete/Lock__ entry in the navigation.
-3. Click the __Pause deployment...__ button.
-4. To resume the deployment, go to the __Overview__ tab and click __Resume deployment__. The
-   deployment being paused displays the __Hibernated__ status until it has been
-   successfully resumed.
+![Arango Managed Platform Connecting Drivers Example](../../images/amp-connecting-drivers-example.png)
 
 ## How to pause a deployment
 

site/content/amp/deployments/private-endpoints.md

@@ -47,11 +47,11 @@ service attachment that you need during the creation of your private endpoint(s)
 2. In the **Quick start** section, click the **Edit** button with an ellipsis (`…`)
    icon. 
 3. Click **Change to private endpoint** in the menu.
-   ![ArangoGraph Deployment Private Endpoint Menu](../../images/arangograph-gcp-change.png)
+   ![Arango Managed Platform GCP Deployment Private Endpoint Menu](../../images/amp-gcp-change-to-private-endpoint.png)
 4. In the configuration wizard, click **Next** to enter your configuration details.
 5. Enter one or more Google project names. You can also add them later in the summary view.
    Click **Next**.
-   ![ArangoGraph Deployment Private Endpoint Setup 2](../../images/arangograph-gcp-private-endpoint.png)
+   ![Arango Managed Platform GCP Deployment Private Endpoint Setup 2](../../images/amp-gcp-private-endpoint-configure.png)
 6. Configure custom DNS names. This step is optional and disabled by default.
    Note that, once enabled, this setting is immutable and cannot be reverted.
    Click **Next** to continue.
@@ -62,7 +62,7 @@ service attachment that you need during the creation of your private endpoint(s)
    If the custom DNS is enabled, you will be responsible for the DNS of your
    private endpoints.
    {{< /info >}}
-   ![ArangoGraph Private Endpoint Custom DNS](../../images/arangograph-gcp-custom-dns.png)
+   ![ArangoGraph Private Endpoint Custom DNS](../../images/amp-gcp-private-endpoint-custom-dns.png)
 7. Click **Confirm Settings** to change the deployment.
 8. Back in the **Overview** page, scroll down to the **Private Endpoint** section
    that is now displayed to see the connection status and to change the
@@ -107,7 +107,7 @@ that automatically connects to private endpoints that are created in those princ
 2. In the **Quick start** section, click the **Edit** button with an ellipsis (`…`)
    icon.
 3. Click **Change to private endpoint** in the menu.
-   ![ArangoGraph Deployment AWS Change to Private Endpoint](../../images/arangograph-aws-change-to-private-endpoint.png)
+   ![Arango Managed Platform Deployment AWS Change to Private Endpoint](../../images/amp-aws-change-to-private-endpoint.png)
 4. In the configuration wizard, click **Next** to enter your configuration details.
 5. Click **Add Principal** to start configuring the AWS principal(s). 
    You need to enter a valid account, which is your 12 digit AWS account ID.
@@ -120,7 +120,7 @@ that automatically connects to private endpoints that are created in those princ
    To verify your endpoint service in AWS, you must use the same principal as
    configured in AMP. Otherwise, the service name cannot be verified.
    {{< /warning >}}
-   ![ArangoGraph AWS Private Endpoint Configure Principals](../../images/arangograph-aws-endpoint-configure-principals.png)
+   ![Arango Managed Platform AWS Private Endpoint Configure Principals](../../images/amp-aws-endpoint-configure-principals.png)
 6. Configure custom DNS names. This step is optional and disabled by default,
    you can also add or change them later from the summary view.
    Click **Next** to continue.
@@ -130,13 +130,13 @@ that automatically connects to private endpoints that are created in those princ
    If the custom DNS is enabled, you will be responsible for the DNS of your
    private endpoints. 
    {{< /info >}}
-   ![ArangoGraph AWS Private Endpoint Alternate DNS](../../images/arangograph-aws-private-endpoint-dns.png)
+   ![Arango Managed Platform AWS Private Endpoint Alternate DNS](../../images/amp-aws-private-endpoint-dns.png)
 7. Confirm that you want to use a private endpoint for your deployment by
    clicking **Confirm Settings**.
 8. Back in the **Overview** page, scroll down to the **Private Endpoint** section
    that is now displayed to see the connection status and change the
    configuration, if needed.
-   ![ArangoGraph AWS Private Endpoint Overview](../../images/arangograph-aws-private-endpoint-overview.png)
+   ![Arango Managed Platform AWS Private Endpoint Overview](../../images/amp-aws-private-endpoint-overview.png)
    {{< info >}}
    Note that
    [Availability Zones](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-regions-availability-zones.html#concepts-availability-zones)

site/content/amp/migrate-to-the-cloud.md

@@ -150,8 +150,6 @@ have and how often write operations are executed during the process.
 You can also track the progress by checking the **Migration status** section of
 your target deployment in AMP dashboard.
 
-![ArangoGraph Cloud Migration Progress](../images/arangograph-migration-agent.png)
-
 ### Getting the current status
 
 To print the current status of the migration, run the following command: