Safer starts for the systems behind care.

Apollo delivers supported AWS virtual machines shaped for healthcare environments, giving platform teams secure defaults they can test against the way care is actually delivered.

Scope note:Apollo images can support HIPAA security requirements. Compliance still depends on the complete system, its operation, and your organization.
HIPAA Security Rule

Turn technical safeguards into infrastructure questions.

1.
Access

Pair authenticated administration and least privilege with the controls configured in the selected image.

OS LAYER
2.
Integrity

Validate secure defaults against the software, interfaces, and change process used by the workload.

OS LAYER
3.
Transmission

Complete the image with encryption, network policy, and protocols appropriate to the data in motion.

OS LAYER

Choose by workload, not by guesswork.

Filter Apollo by stack, operating system, and architecture, then continue to the exact AWS Marketplace record.

View all 20 builds
Used by

Apollo has been used by teams at these organizations.

Where Apollo fits

For the teams keeping health data in motion.

Explore industry pages →

01

Care delivery

Operating-system foundations for applications and services that support providers and patient operations.

02

Health technology

Supported cloud images for software teams building, testing, and operating healthcare products.

03

Life sciences

Supported infrastructure for regulated research, data, and operational workloads.

Workload review

Four checks before a healthcare workload goes live.

1.
Name the workload

Start with its operating system, software stack, architecture, data type, and care setting.

2.
Rehearse the real behavior

Run the exact build with application services, integrations, identities, and support workflows outside production.

3.
Complete the control set

Add encryption, networking, logging, monitoring, backup, recovery, and incident-response measures.

4.
Record the decision

Retain the listing, test results, exceptions, procedures, and ownership around ePHI.

Healthcare references

Six sources for a more grounded review.

Connect the exact Apollo build to the rules, guidance, practices, and assurance model that shape your environment.

Important: These references help frame evaluation. They do not make an Apollo image, workload, or organization compliant, certified, or authorized.

Before you choose

What healthcare teams should ask first.

What does Apollo provide?+

Apollo provides supported virtual machines and application stacks for AWS, with a healthcare-focused approach to operating-system hardening and technical support.

Does an Apollo image make a workload HIPAA compliant?+

No. A hardened image can support HIPAA security requirements, but compliance depends on the complete system and operating program. Customers remain responsible for architecture, identity, networking, encryption, applications, monitoring, procedures, evidence, and legal determinations.

Which products are available today?+

Apollo's current public AWS catalog contains 20 supported Linux operating-system and application-stack listings. Use the product catalog to confirm the exact version and architecture.

Can hardening affect healthcare applications?+

Yes. Secure defaults can restrict services, protocols, permissions, or authentication methods that an application expects. Test every image, interface, and dependency in a non-production environment before promotion.

Which healthcare security frameworks does Apollo support?+

Apollo supports evaluation against the HIPAA Security Rule, NIST SP 800-66 Rev. 2, the HITECH Act, HHS Healthcare and Public Health Cybersecurity Performance Goals, HICP 2023, and the HITRUST CSF. Framework support does not mean that an image or workload is automatically compliant or certified.

Find the Apollo build that fits your care environment.

Compare current products, open the exact AWS record, and put the selected image through a real workload rehearsal.