Covalent usecase: Explore running Asyncroscopy on AWS EC2

Motivation

We have successfully run Asyncroscopy on the UTK ISAAC HPC environment:

• https://github.com/pycroscopy/asyncroscopy/issues/80

As a next step, we would like to evaluate running Asyncroscopy on AWS EC2.

This is partly motivated by portability and deployment flexibility, and partly as an opportunity to better understand the infrastructure assumptions currently embedded in Asyncroscopy (networking, Tango access, instrument connectivity, etc.).

Questions

• Can Asyncroscopy be installed and run on a standard AWS EC2 instance without modification?
• Which components assume access to a university or instrument-local network?
• What are the minimum networking requirements for Tango database and device-server connectivity?
• Are there recommended deployment patterns for cloud-hosted control/analysis workflows?

Initial Scope

• Launch an Ubuntu EC2 instance.
• Install Asyncroscopy using documented installation steps.
• Verify basic functionality and example workflows.
• Document any blockers related to networking, Tango, or instrument access.

Notes

The ISAAC deployment benefited from being on the university network. AWS introduces a different networking model, so instrument connectivity may require additional architecture (VPN, hybrid deployment, tunnels, etc.).

This issue is intended as an exploration/documentation effort rather than a commitment to support AWS deployments.

Start with the documented Asyncroscopy installation steps and the example workflows on an Ubuntu AWS EC2 instance. Verify basic functionality, then investigate the networking requirements for Tango database and device-server connectivity. Document installation results and any blockers involving networking, Tango, or instrument access.