Version 3.2
Version 3.2
Amorphic 3.2 delivers a comprehensive set of new features, enhancements, and bug fixes focused on advancing data cataloging, geospatial analytics, AI-powered data discovery, and platform flexibility. This release introduces 6 major new features—including SAML group-to-tag access mapping, native ArcGIS Online integration, advanced relationship graph visualizations for ArcGIS, and full geospatial data support—accompanied by over 20 enhancements such as improved dataflow validation, enhanced code template management, more flexible OAuth2 datasource authentication, and upgrades to AI services. Additional improvements strengthen auditability, execution monitoring, user experience, and integration with both spatial and external data systems. Overall, version 3.2 delivers greater automation, connectivity, and visibility, enabling users to manage, discover, and secure their data assets more intuitively and efficiently across the Amorphic platform.
Features (06)
-
[CLOUD-6377] - Introduction of SAML group-to-tag access mapping – Users logging in via Single Sign-On (SSO), such as through Entra ID (Azure AD) or any other SAML-supported provider, will now have Amorphic tag access automatically assigned based on their SSO group membership, as long as a corresponding SAML tag mapping exists and this mapping can be configured in the admin/tags page of Amorphic .
-
[CLOUD-6228] - AI Driven Search in Catalog - This feature introduces AI-powered contextual search within Catalog, enabling users to find relevant data based on meaning rather than exact keywords by understanding the intent behind natural language queries. This feature is available only in AI Enabled environments and the user will further need to enable Catalog in the Manage AI Services section under AI Space. Users can choose Semantic Search directly from the search bar while running a query or set it as the default option in the System Settings section of the Administration panel under Application Management.
-
[CLOUD-6212] - Introducing Native ArcGIS Online Datasource Integration – Amorphic now supports ArcGIS Online as a native datasource, enabling metadata cataloging, and optional data ingestion for ArcGIS items such as Dashboards, Web Maps, Web Experiences, and Feature Services. The integration includes API Key and OAuth2 authentication, supports multiple target destinations (S3, Redshift, Lake Formation, etc.), and provides schema detection for spatial data along with batch processing and governed access for analytics.
-
[CLOUD-6140] - Capture and Visualize Relationships between ArcGIS Catalog Assets - Introduced the ability to capture and visualize relationships between ArcGIS catalog assets within Amorphic. A new Dependency Graph tab has been added under Catalog for ArcGIS assets, allowing users to explore how assets such as Hub Site Applications, Hub Pages, Web Maps, Web Experiences, Feature Services and Dashboards are interconnected. Users can select an ArcGIS catalog asset to view its relationships through an interactive graphical interface. The depth parameter enables control over the number of levels displayed in the graph. This enhancement expands the ArcGIS Catalog beyond simple item listing to include a comprehensive visualization of dependencies between resources.
-
[CLOUD-6124] - Support for GeoSpatial Data Storage – This feature introduces full geospatial data capabilities in Amorphic, allowing users to create spatial datasets from ArcGIS Online, SQL Server, or direct file uploads. Users can run spatial queries for advanced analysis, visualize results on interactive maps, and search or preview spatial datasets directly within the data catalog.
-
[[TRACE]CLOUD-5413] - Amorphic Observability Solution Trace Implementation - Trace provides comprehensive usage observability across Amorphic resources, enabling visibility into which users are creating or utilizing specific assets. It also includes robust compliance tracking and reporting features, supporting multiple industry standards such as HIPAA, NIST, CIS, and AWS Foundational Security Best Practices.
Enhancements (23)
-
[CLOUD-6450] - Execution History Support for Advanced Dataload Dataflows (Full Load) – Advanced Dataload now includes execution history tracking for Full Load dataflows, providing improved visibility into past runs. Users can view key details such as start and end times, record counts, errors, and overall status, enabling better monitoring, troubleshooting, and validation of data migrations.
-
[CLOUD-6359] - Enhancements to Code Templates - Replaced the previous iteration of code templates with more reusable and generalized scripts that restore their intended purpose as adaptable, cross-functional resources. Templates now clearly demonstrate their use cases and can be easily adapted across different ETL jobs and users.
-
[CLOUD-6351] - Enhancements to Bulk Load Dataflows: Spatial Data Support for SQL Server – Bulk-load dataflows using SQL Server sources now support ingestion of spatial datasets into S3 Athena and Redshift. Users can enable this by selecting Spatial Dataset during dataset configuration in dataflows and specifying the spatial and CRS columns. This enhancement ensures that spatial data is correctly stored, queried, and visualized in the target systems.
-
[CLOUD-6343] - Enhanced Dataset Selection Validation in Dataflows – Code changes have been implemented to ensure that the same dataset name cannot be selected more than once within a single Dataflow. This enhancement applies to both JDBC Bulk Load and JDBC Advanced Load sources, preventing dataset name conflicts during task registration and avoiding scenarios where the dataflow could remain stuck in a running state.
-
[CLOUD-6316] - Improvements to AI Services : Automated Model Syncing , Open AI Support and Dataset Ingestion Support for Chat sessions -
- Introduced biweekly auto-sync for AI models, scheduled every 15 days to ensure the latest models are consistently updated. Additionally, introduced support for OpenAI model invocation through Bedrock.
- Introduced a new API endpoint that enables ingestion of previously uploaded files from chat sessions into existing datasets, allowing seamless integration and reuse of existing data within the platform. [API-Only]
-
[CLOUD-6274] - Enhanced OAuth2 Authentication for External API Datasources – The platform now supports creating datasources using OAuth2 where ClientAuthentication can be passed in the request body, in addition to the previously supported header-based method. This enhancement provides greater flexibility when configuring external API connections/datasources.
-
[CLOUD-6272] - Improved File Extension Handling for External API Datasources dataflows – Files ingested from External API datasources that were previously assigned the generic .others extension will now default to the .json extension when the dataset file type is set to Others. This update improves usability by providing a more meaningful and recognizable file format, making file management and previewing easier and more intuitive.
-
[CLOUD-6226,6281] - SQL AI Improvements: Workbooks, Spatial Query Support, End-to-End Query Execution, Execution Controls, and Smarter Error Recovery - A new workbook component has been introduced to persist chat sessions with SQL AI, providing a structured and reusable way to manage interactions. SQL AI now supports spatial data queries, enabling advanced location-based and geospatial analyses directly within chat workflows. The component also offers full query execution support, allowing users to run and manage SQL queries with AI assistance. Additionally, enhanced error handling has been added: when a query fails, the AI will prompt the user to retry, and if approved, it will regenerate the query using the context of the encountered error. A new system configuration, SQL AI Auto Run Configuration, controls whether natural-language queries in workbooks execute automatically. When enabled, queries run instantly for a smoother workflow; when disabled, users gain greater control by choosing when queries should execute.
-
[CLOUD-6224] - Improved AGENTS Support and System Agent Creation in AWS Regions with Cross-Region Inferences - Fixed an issue where System Agent creation could fail due to the unavailability of Bedrock models in certain Regions. The system now gracefully handles such cases and provides clear instructions for verifying SCP restrictions and recreating System Agents from the UI.
-
[CLOUD-6215] - Added schedules and Global flag support for instances/entities for Bulkdataload instances/entities - JDBC BulkLoad datasources now support scheduled entity creation, along with the ability to create global entities and convert existing entities into global entities. This enhancement enables entities to be shared and reused across multiple datasources.
-
[CLOUD-6214] - Shared Kafka Cluster Support for Scheduled Advanced Dataloads – JDBC Advanced Dataload datasources now support the use of shared Kafka clusters with scheduled execution. Clusters can be pre-created from the Entities page and configured as either global (usable across all datasources) or datasource-specific (restricted to a single datasource), enabling more efficient resource reuse and easier scheduling management.
-
[CLOUD-6205] - Added pagination support for data quality checks runs list call - Introduced pagination, filtering, and attribute projection for listing data-quality-check runs within datasets. Users can now project specific attributes such as startTime, endTime, status, message, and actions, and also sort the results based on these fields. These enhancements improve usability and performance when managing large sets of data-quality-check runs.
-
[CLOUD-6201] - Chat Management Enhancement: Smarter Chat Titles for Faster Navigation and Better Organization - Enhanced chat management with automatic title generation based on conversation content, reducing manual effort and improving overall readability. Chat listings are now sorted by last modified time, making it easier for users to quickly locate and access recent discussions. These improvements streamline navigation and create a more organized chat experience.
-
[CLOUD-6180] - Resource statistics collection for AI core components - Resource Statistics for AI core components has been included under Overview in the Home Page. The components included are AI Agents, Knowledge Bases and GuardRails. Users can now see the AI core components resources in a graphical format along with other resources.
-
[CLOUD-6143] - Improvements in Data Glossaries - Glossaries in Amorphic have been enhanced with the following improvements:
- Bi-directional Linking: Previously, glossary terms could only be linked to dataset columns through the catalog’s schema section. This enhancement allows users to attach glossary terms directly from the dataset interface as well, making the linking process bi-directional and more intuitive.
- Importing Glossaries and Terms: Users can now import glossaries and terms into Amorphic using structured JSON files, enabling faster and easier setup of the semantic layer within the application.
- User Notifications:Support for user activity notifications has been extended to include glossary-related actions. Users will now receive alerts for glossary updates and linking operations.
-
[CLOUD-6136] - Support for custom actions on catalog search results - Enabled users to perform custom data actions on datasets they have access to. They can be used across tools like Playground, Amorphic BI App, Tableau, and Power BI using SQL queries. Added guidance on how datasets can be connected and utilized within these tools for enhanced analytical flexibility.
-
[CLOUD-6135] - Support for markdown format for all description metadata fields across Datasets and Datasources - Added Markdown support for datasets and datasources resource descriptions, allowing rich text formatting while maintaining compatibility with existing plain text and search functionality in catalog. This enhancement will allow users to create more expressive and well-structured descriptions in datasets and datasources to improve readability and context.
-
[CLOUD-6127] - Resource Sync Support for HCLS Components – Added support to automatically synchronize HCLS resources between Amorphic and AWS. Any HCLS resource created or deleted directly from the AWS console (with the appropriate tags applied) will now be reflected in Amorphic, ensuring consistent state and reducing manual reconciliation.
-
[CLOUD-6105] - Advanced dataload dataflows for target location S3Athena now supports the JSON data format - Advancedataload now fully supports JSON data for S3Athena targets, improving data ingestion for dataflows. This enhancement streamlines integrating JSON data into S3Athena, allowing direct querying and analysis of semi-structured data while maintaining Advancedataload's existing framework, data integrity, and performance.
-
[CLOUD-6057] - Support to Create Datasets(both views and regular datasets) from Query results - With this enhancement, users can now use results from queries run in the Playground and upload the results as a file into an existing dataset or create a new dataset — either internal or view type — based on the query output, with S3 Athena or Redshift as the target location. This streamlines data reuse and helps create a dataset faster by reducing time taken by dataset registration or file upload.
-
[CLOUD-6032] - Data profiling for hudi and delta lake datasets - With this enhancement, Hudi and Delta Lake datasets now support data profiling — a feature that was previously unavailable for these dataset types.
-
[CLOUD-6030] - Improved Handling to Prevent Files from Getting Stuck in Processing Status – The Reload dataset file processing flow has been updated to ensure that files no longer remain indefinitely in the Processing state when an internal failure occurs. The system now detects such errors and automatically transitions the file to a stable state, preventing stuck executions and removing the need for manual repair.
-
[CLOUD-6027] - Enhanced Data Validation with Consolidated Error Reporting – Data validation process now reports all detected issues in a single response instead of stopping at the first failure. Errors such as missing values, invalid data types, and column-level mismatches are grouped together, allowing users to review and resolve all problems in one upload attempt, reducing back-and-forth correction cycles.
Bug Fixes (04)
-
[CLOUD-6287] - User Removal Failure from Access Tags – Resolved an issue where a user could not be removed from a tag if they had access to an Insights dashboard both through the tag and individually via direct dashboard assignment. The removal process now works as expected in all cases.
-
[CLOUD-6279] - Fixed Incorrect Partial Failure Status for Successful Dataflows – Resolved an issue where the status of a dataflow was incorrectly marked as partial failure even when all tables were successfully ingested. The backend logic has been corrected to ensure the proper status is now reported.
-
[CLOUD-6273] - RBAC Validation failure for HCLS Omics Resources – Resolved an issue where RBAC permissions were not being enforced during the creation of Health Omics resources, resulting in resources being created every time regardless of access rights. RBAC validation is now correctly applied before resource creation.
-
[CLOUD-6181] - Resolved Bedrock Access Failure for Pre-AI Datalabs and ETL Jobs in AI-Enabled Environments - This fix ensures that all ETL Jobs and Datalabs created in AI enabled Amorphic environments are automatically updated with the required Bedrock permissions without the need for any manual steps, ensuring seamless access to Bedrock models and services from within the users’ analytic workloads.
API Only Features (04)
-
[CLOUD-6358] - Dataset Data Consumption API with Advanced Filtering & Pagination – A new API has been introduced that allows users to retrieve dataset records directly, without requiring a download step or additional processing. The API supports advanced query filtering with logical operators (AND, OR, NOT), range-based conditions, and column-level filtering, enabling precise and efficient data retrieval. Pagination is built in for large datasets, and the response format is standardized with clearer error handling for smoother integration.
-
[CLOUD-6261] - Enhancements in Data Profiling in Amorphic - Enhancements have been added to Data Profiling like separating Auto generated AI suggestions (e.g., PII detection, data classification, etc.) from the core data profiling operation (e.g., min/max, missing values, etc.), as well as the ability to trigger data profiling for a particular dataset from the dataset side, making the process more intuitive.
-
[CLOUD-6167] - Enhancements to Guardrails API’s - Introduced a dedicated API to retrieve the default guard rail (GET /ai/guard-rails/default) and updated the listing API to support fetching component-specific guard rails (GET /ai/guard-rails?component=component-name). This update improves flexibility in managing and retrieving guard rail configurations.
-
[CLOUD-6134] - Introduction to Bedrock Flows in Amorphic - This feature introduces Bedrock Flows as a new type of data pipeline within the application, enabling orchestration of AI-driven workflows. Bedrock Flows allow the user to design and execute generative AI pipelines alongside existing data workflows for advanced automation and intelligence. Native support, in the form of nodes, for features like Knowledge Base nodes and Lambda nodes is available with the new form of data-pipelines. Additionally, utility nodes like storage nodes, collector nodes, iterator node, etc are also available.
UI Features/Enhancements (03)
-
[UI-1890] - Enhanced Catalog Interface - The catalog interface has been updated for improved discovery and search. Updates include a streamlined search experience with keyword and semantic search, an enhanced filter section with organized metrics and clearer controls, improved asset details navigation with smooth animations and a new full-page details screen, better handling of search parameters and URL state management, optimized asset type tabs for easier switching, and an improved empty state with clearer guidance for new users. The redesign also adds support for new ArcGIS datasource asset types (Web Experience, Web Map, Feature Service, Hub Site Application, and Hub Page), an interactive dependency graph visualization for ArcGIS assets that shows lineage relationships, and an enhanced details screen with full-page layout and improved information architecture.
-
[UI-1921] - Improvements to main menu navigation - Navigation has been redesigned with a new services sidebar that organizes services by new categories, keyboard shortcuts (press 'k' to open search), a search overlay for quick access across services, improved mobile menu with accordion-style navigation and better accessibility, category-based organization for faster navigation, and enhanced focus management and keyboard navigation throughout the menu system.
-
[UI-1951] - Improved Governance with Default and Component Guardrails - Introduced an organization-level default guardrail to ensure consistent safety and content filtering across all components. Admins can now easily set a default guardrail from the guardrail details page, reducing manual configuration effort. Component-specific guardrail assignments provide tighter governance, improving compliance and creating a more streamlined user experience.
Cross-Account-Role Updates (01)
- [CLOUD-6526] - Cross Account Role Permission Changes v3.2 - Updated cross-account role with conditions for various services for fine grained access control along with ability to tag and untag AWS resources for improved management and removed obsolete permissions.
Known Issues (06)
-
[CLOUD-6533] - Occasional failures may be experienced during Redshift dataflow creation - In rare cases, dataflow creation with Redshift as the target (when Create Dataset = True) may fail due to a temporary network issue during table creation. The dataflow may appear in a registration-failed state. Retrying the same creation usually succeeds on the next attempt.
-
[CLOUD-6528] - Automated File Processing Fails for Reload Datasets Ingested from S3 via Scheduled Runs – When files are ingested into a Reload-type dataset through a scheduled execution from an S3 datasource, they may remain stuck in the Pending state unless the ingestion is triggered manually. This is due to a defect where the process does not detect the end-of-transfer marker from the S3 connector, preventing automatic processing from starting.
-
[CLOUD-6525] - No Results Displayed When Filtering Agents by Status on the Listing Page: The user interface fails to display any results when attempting to filter agents by their status on the agent listing page. This issue may occur when agents are filtered by statuses such as "READY" or "FAILED." While the filter functionality is active, it does not return any matching results, which could potentially confuse users.
-
[CLOUD-6507] - Cost tag activation status update and budget actions are skipped when the tag key contains an underscore () character - Cost tag activation status and related budget actions may not update correctly when the tag key contains an underscore () character.
-
[CLOUD-6523] - Dataflow for ArcGIS datasources remains stuck in “Running” state – The Glue job used for ArcGIS ingestion requires ENIs, and each ENI consumes an IP from the subnet. In some cases, AWS does not automatically clean up unused ENIs left behind from previous Glue jobs or connections, which results in IPs not being released. Over time, the subnet may run out of available IPs, causing new Glue jobs to fail. When this happens, the ArcGIS ingestion job fails silently, leaving the dataflow execution stuck in a running state.
-
[CLOUD-6543] - SQL AI Sync Job Execution Failure Due to Missing Tenant Parameters. - This issue occurs when tenant-related SSM parameters are deleted during simultaneous enable/disable operations of SQL AI within the "Manage AI Services" interface, leading to execution failures of SQL AI sync jobs due to missing parameters.
User Actions/Notice (02)
-
Omics Analytics is being deprecated starting with v3.3. Users can continue to use existing Omics Annotation and Variant Stores created in earlier versions, but new Stores cannot be created in v3.3 and later. Before upgrading to v3.3, users must delete all existing Omics Annotation and Variant Stores. For more details, refer to the AWS Documentation.
-
Newer Amazon Bedrock models, such as Claude 3.7 (and subsequent versions), leverage cross-Region inference. This means that an inference request initiated from your Amorphic region will be dynamically routed to one of several predefined destination regions. If even one destination region is restricted by a Service Control Policy (SCP), the inference request fails entirely, even if other regions are permitted. All AI components of Amorphic that rely on these models will fail if SCPs restrict any of the regions required for cross-Region inference. To prevent this, users must ensure that the SCPs set at their organizations must allow Bedrock API actions in every Region where the target models are hosted. For more details, refer to the AWS Documentation
Amorphic CICD (01)
- [CLOUD-6329] - Extend Amorphic CICD with Guardrail support - Amorphic now supports Guardrails for use with agents in the application. With this new feature in Amorphic, Amorphic CICD also now supports creating guardrails, using templates.
