Creating an Asset Source - AWS

Learn how to create an asset source in an Oracle Cloud Migrations environment.

Before you create an asset source, ensure that you have defined the required AWS privileges. See AWS Credentials for more information.

  • To create an asset source, follow these steps:
    1. Open the navigation menu and click Migration & Disaster Recovery. Under Cloud Migrations, click Discovery, and then click Create asset source.
    2. Click Create AWS asset source.
    3. Enter the following under Asset source information:
      1. Name: Enter a name for the asset source.
      2. Account id: Enter the AWS account ID. See Where Can I Find My AWS Account ID?
      3. Region: Choose the AWS region where the source resources are located.
      4. Compartment: Choose a compartment for the asset source.
      5. Target compartment: Choose the compartment where you created the inventory assets.
    4. Under Remote connections source environment, choose the source environment. You can use an existing source environment or create a new one.
      • If a source environment already exists, click Use existing source environment.
      • To create a new environment, click Create new.
    5. In the Discovery credentials section, use one of the following options:
      • Click Use existing secret and select a vault and secret for existing discovery credentials.
      • Click Create secret and enter the Access Key ID and Secret Access Key for the credentials that have discovery permissions. See Required IAM Permissions for Discovery.
    6. (Optional) In the Replication credentials section, use one of the following options:
      • Click Use discovery credentials to continue with the selected discovery credentials.
      • Click Use existing secret and select a vault and secret for existing replication credentials.
      • Click Create secret and enter the Access Key ID and Secret Access Key for the credentials that have replication permissions. See Required IAM Permissions for Replication.
    7. Under Discovery schedule, click one of the following to perform the discovery job:
      • To perform an on-demand or manual asset discovery, click No discovery schedule.
      • To use an existing discovery schedule, click Select existing schedule.
      • To create the wanted discovery schedule, click Create schedule.

        You can keep asset information up-to-date by using the discovery scheduling mechanism, as a recurring task. After creating a discovery schedule, you can attach or detach it from an existing asset source to begin or stop scheduling discovery jobs for external asset discovery and metadata collection.

    8. Click Enable collection of cost estimation metrics if you want to collect the cost estimation metrics.
      • The metrics for AWS are not selected by default.
      • Enabling real-time and historical metrics collection utilizes the Amazon CloudWatch service and enabling cost estimation metrics utilizes Amazon Cost Explorer service which are chargeable resources.
      • When Enable collection of cost estimation metrics is enabled, the metrics are automatically collected when a discovery job is run.
      • When Enable collection of real-time metrics is enabled, the metrics are automatically collected once per hour
      • When Enable collection of historical metrics is enabled, the metrics are automatically collected once per day.
      • If enabled, both Realtime and Historical metrics are also collected when discovery job is run manually.
    9. Click Create asset source.
    You are redirected to the Asset source details page after the asset source is created successfully.
    You can now create a discovery work request.
  • To create an asset source, use the create command.

    oci cloud-bridge discovery asset-source create --assets-compartment-id asset_compartment_ID --compartment-id target_compartment_ID --environment-id target_environment_ID --inventory-id assets_inventory_ID --type asset_source_type --discoveryCredentials credentials [OPTIONS]
    The required parameters for the create command are:
    • --assets-compartment-id: Specifies the OCID of the compartment that is used to create assets.
    • --compartment-id: Specifies the OCID of the compartment for the resource.
    • --environment-id: Specifies the OCID of the environment.
    • --inventory-id: Specifies the OCID of the inventory that contains the created assets.
    • --type: Specifies the type of asset source in the external environment. The accepted value is AWS.
    • --discovery-credentials: Specifies the OCI Vault secret that contains AWS credentials. The value cannot be null.
    • --aws-account-key: Specifies the AWS account key.
    • --aws-region: Specifies the AWS region where the source resources are located.
    • --are-historical-metrics-collected: Specifies the historical metrics that are collected directly from the source environment and contain a single value for the average network, memory, and CPU usage over an interval. Only one value for each is provided at the one day, one week, and one month intervals. This is optional.
    • --are-realtime-metrics-collected: Specifies the real-time metrics that are periodically collected from the source environment are stored in OCI monitoring. Overtime, more accurate calculations can be made against these metrics without relying on data provided by the source environment. This is optional.
    • --is-cost-information-collected: Specifies the cost estimation metrics. This is optional.

    To get all the commands for discovery asset-source, run:

    oci cloud-bridge discovery asset-source -h

    To get help for the create command, run:

    oci cloud-bridge discovery asset-source create -h

    For a complete list of flags and variable options for CLI commands, see the CLI Command Reference.

  • To create an asset source, use the CreateAssetSource operation.