Skip to main content
 print this page

JDBC Bulk data load Entities

JDBC Bulk data load dataflows in Amorphic use Replication Instances of DMS (Database Migration Service) to ingest data from source to target. This feature allows setting up multiple dataflows with a single instance, rather than one instance for each dataflow.

These Shared Instances are independent of each JDBC datasource, meaning when a shared instance is created for a datasource, only the dataflows within that datasource can use this instance. Instances here refer to entities that are created within the JDBC datasources, ensuring that dataflows from different datasources cannot share the same instance.

How to create an Entity (Shared Instance)​

Below are the steps that are required to create an entity for JDBC datasource

  • Entity Name : Name of the entity to be used, an identifier of the Instance.

  • Description : Purpose of this entity which will be helpful for all the authorized users to understand the requirement

  • Instance Availability Zone : Availability zone to be used to launch the replication instance. When an AZ is selected, all the available instance classes in that AZ will be shown and one can be selected from the list.

  • Instance Class : Type of DMS instance class to be used. Please choose approx Instance based on the usability in dataflows.

  • Allocated Storage: Amount of storage space you want for your replication instance. AWS DMS uses this storage for log files and cached transactions while dataflows are in progress.

  • Multi-AZ : Specifies whether the replication instance is a Multi-AZ deployment. When Multi-AZ setting is enabled Instance Availability Zone setting will be nullified in the backend.

  • Auto Minor Version Upgrade : A value that indicates whether minor engine upgrades are applied automatically to the replication instance during the maintenance window. This parameter defaults to true if not specified.

  • Auto Terminate : This enables Shared Instance termination to save resource costs based on the termination time value provided by the user. Auto termination process is triggered every hour and looks for any Shared Instance that needs to be notified or deleted and sends an email when one of the below criteria is met. The user will receive a notification email in the following scenarios:

    • If the difference between the auto-terminate process trigger run (every whole hour) and the termination time is less than 30 minutes.
    • If the auto-termination process was successfully able to delete the Instance after the termination time
    • If the auto-termination process wasn't able to delete the Instance due to some fatal errors.

  • Auto Termination Time : You can set auto termination time for Shared Instance to less than 168 hours (7 days). If current time is greater than termination time, Instance will be deleted next whole hour.

  • DmsVersion: Users have the option to specify the DMS engine version to be used on the replication instance. This attribute is optional, if no version is provided, the replication instance will be created with the latest DMS engine version. Users can update it as well.

JDBC Datasource entity creation

How to edit an Entity​

Once the entity creation is successful and is in active status, entity configuration can be updated with Edit option.

Only certain configurations can be updated and the same will be shown when an update entity is clicked and the configuration that are not editable will be greyed out. Entity Name and Instance Availability Zone are not editable and the rest all can be changeable.

JDBC Datasource entity updation

View Entity details and Dataflows associated​

To view additional details of the entity and also the list of all dataflows associated with the entity, one can click on View Entity button which will show all the additional details and the dataflows.

JDBC Datasource entity details

How to delete an Entity​

An entity can be deleted with the Delete Entity option that can be seen in the options of a particular Instance. Please note that if there are any active dataflows linked to the entity, it cannot be deleted.

JDBC Datasource entity delete

Note

In the Entity listing page all the entities that are being used in the JDBC datasource will be shown (Shared + Dedicated instances) but any action can be made only for shared instances. If the Entity configuration needs to be updated for a dedicated entity then it can be done in the dataflow listing page in Edit Dataflow option.