Page Comparison

Overall Status Updates

• DEX Development, Status Updates, and Timeline:

  • Upload API: Working ON v1.1-In progress, status of upload

    • V1.1.2-Will work on authenticating via SAMS SSO

    • Milestones on progress

• Reviewing AIMS connection to DEX options: Research/Analysis: In Progress

  • Upload API - AIMS has reviewed docs, but have not yet requested to be added to the DEX activity.

    • Pro: resumable technology looks like it solves a the problem of supporting large file uploads to web apis.

    • Con: is that it would be a client agent within AIMS that would need continual maintenance and also the ability to track success/failure (queue/dead letter) and team prepared to debug if certificates, credentials, etc change.

  • AWS data sync to azure blob storage -

    • Background: the integration for azure blob storage is notably a “preview” feature on AWS’s side.

    • Pro: job would be configured on each side with no code to maintain.

    • Con: A downside is that this is a job that has to run on some cron frequency - so data flow will be in chunks as opposed to a “real time” stream.

  • Alternative research: potential other project’s integration into azure using Azure Connectors for SQS and S3 to see if it would apply to this problem. This would match how AIMS already internally handles event driven processing & would inherit what the team already knows how to use.

    • Geo is working on proto-typing this option and will have an update next time we meet

    • Need to investigate the effort on the Azure side to make configurations and/or services to use these connectors.

  • Research in progress, AIMS has not requested access

  • Other Options: Will continue to research

• • AIMS/APHL Updates:

    1. SDS (Send to DEX Servce) / Upload API

       1. Tested connectivity successfully

       2. Prototyped runtime using Docker image & lambda using aims sandbox

       3. Next:

          1. Determine what a load/performance test should look like & perform the test

          2. Determine if we want the runtime to be in Lambda, Mirth, Fargate, or k8s

    2. AWS DataSync

       1. Prerequisite for transfer test: EC2 instance to run data sync agent - did not complete this

       2. Tested connectivity to S3 and Azure locations

       3. Further research/additional information needed regarding cost / architecture questions for scaling this solution long term

    3. Azure Logic Apps / Connectors

       1. Further research/additional information needed regarding cost implications in azure to run

       2. Need help understanding continued monitoring & maintenance of a logic app

       3. https://learn.microsoft.com/en-us/microsoft-365/community/power-automate-vs-logic-apps

    4. RAS (Receive from AIMS Service)

       1. With a slight modification, the SDS can run as a poller

       2. Have built similar poller services many times, can be done with this for performance testing in a few days if there is interest

       3. Would run on the DEX/Azure side to poll SQS and get data from AIMS S3

Mtg Notes:

DRAFT Data Flow Diagram

Questions

Next Steps & Action Items

• Next steps: