Cost Explorer
Amorphic Cost Explorer allows you to keep track of the costs associated with the usage of AWS services and the Amorphic platform over a period of a month. This feature provides you with an overview of the costs you incur and also gives you the ability to drill down and see the cost incurred for each individual service.
The "Usage by Service" section allows you to examine the cost breakdown per service and permits you to choose the specific service for which you wish to view the cost details. This feature helps you in monitoring your expenditure and helps in optimizing your usage of the services. You will also get alerts about resources every twelve hours to clean up or terminate desired resources for cost saving purposes.
You can view two type of costings:
Licenses & Billings
- Costs you incur over a month for AWS services and Amorphic platform.High Costing Resources
- Shows active high costing resources in the application.
Amorphic Cost explorer lists the following high costing service resources along with their approximate estimated cost:
Resource | Description |
---|---|
Endpoints | Lists all the currently running or active glue development endpoints. |
Notebooks | Lists all the currently running Machine learning notebooks. |
Jobs | Lists all the long running ETL jobs which are running for more than 2 hours. |
Workflows | Lists all the long running workflows which are running for more than 2 hours. |
Deep Search Indices | Lists all active deep search indices. |
Interactive Sessions | Lists all currently running or active interactive sessions. |
Streams | Lists all the currently active Streams. |
Connection Instances | Lists all the currently active shared/non-shared DMS instances under Amorphic Connection. |
Omics Stores | Lists all the currently active Omics Stores. |
Omics Workflows | Lists all the currently running Omics Workflows. |
Health Lake Stores | Lists all the currently active Health Lake Stores. |
As the name suggests, Cost Explorer displays an approximate EstimatedCost
of a resource (Eg. Streams, Endpoints, etc.), hence, the cost calculation will vary if any of the resource is modified(updated)
by user.
Whenever a resource gets modified by user, cost will be re-estimated
based on the newly updated configuration(Eg. InstanceClass, AllocatedStorage, etc.)
of a resource. Hence we try to show an EstimatedCost based on most recent configuration
of a resource.