Select your cookie preferences

We use essential cookies and similar tools that are necessary to provide our site and services. We use performance cookies to collect anonymous statistics, so we can understand how customers use our site and make improvements. Essential cookies cannot be deactivated, but you can choose “Customize” or “Decline” to decline performance cookies.

If you agree, AWS and approved third parties will also use cookies to provide useful site features, remember your preferences, and display relevant content, including relevant advertising. To accept or decline all non-essential cookies, choose “Accept” or “Decline.” To make more detailed choices, choose “Customize.”

AWS HealthImaging and interface VPC endpoints (AWS PrivateLink)

Focus mode
AWS HealthImaging and interface VPC endpoints (AWS PrivateLink) - AWS HealthImaging

You can establish a private connection between your VPC and AWS HealthImaging by creating an interface VPC endpoint. Interface endpoints are powered by AWS PrivateLink, a technology that you can use to privately access HealthImaging APIs without an internet gateway, NAT device, VPN connection, or AWS Direct Connect connection. Instances in your VPC don't need public IP addresses to communicate with HealthImaging APIs. Traffic between your VPC and HealthImaging does not leave the Amazon network.

Each interface endpoint is represented by one or more Elastic Network Interfaces in your subnets.

For more information, see Interface VPC endpoints (AWS PrivateLink) in the Amazon VPC User Guide.

Considerations for HealthImaging VPC endpoints

Before you set up an interface VPC endpoint for HealthImaging, make sure that you review Interface endpoint properties and limitations in the Amazon VPC User Guide.

HealthImaging supports making calls to all AWS HealthImaging actions from your VPC.

Creating an interface VPC endpoint for HealthImaging

You can create a VPC endpoint for the HealthImaging service using the Amazon VPC console or the AWS Command Line Interface (AWS CLI). For more information, see Creating an interface endpoint in the Amazon VPC User Guide.

Create VPC endpoints for HealthImaging using the following service names:

  • com.amazonaws.region.medical-imaging

  • com.amazonaws.region.runtime-medical-imaging

  • com.amazonaws.region.dicom-medical-imaging

Note

Private DNS must be enabled to use PrivateLink.

You can make API requests to HealthImaging using its default DNS name for the Region, for example, medical-imaging.us-east-1.amazonaws.com.

For more information, see Accessing a service through an interface endpoint in the Amazon VPC User Guide.

Creating a VPC endpoint policy for HealthImaging

You can attach an endpoint policy to your VPC endpoint that controls access to HealthImaging. The policy specifies the following information:

  • The principal that can perform actions

  • The actions that can be performed

  • The resources on which actions can be performed

For more information, see Controlling access to services with VPC endpoints in the Amazon VPC User Guide.

Example: VPC endpoint policy for HealthImaging actions

The following is an example of an endpoint policy for HealthImaging. When attached to an endpoint, this policy grants access to HealthImaging actions for all principals on all resources.

API
{ "Statement":[ { "Principal":"*", "Effect":"Allow", "Action":[ "medical-imaging:*" ], "Resource":"*" } ] }
CLI
aws ec2 modify-vpc-endpoint \ --vpc-endpoint-id vpce-id --region us-west-2 \ --private-dns-enabled \ --policy-document \ "{\"Statement\":[{\"Principal\":\"*\",\"Effect\":\"Allow\",\"Action\":[\"medical-imaging:*\"],\"Resource\":\"*\"}]}"
{ "Statement":[ { "Principal":"*", "Effect":"Allow", "Action":[ "medical-imaging:*" ], "Resource":"*" } ] }
PrivacySite termsCookie preferences
© 2025, Amazon Web Services, Inc. or its affiliates. All rights reserved.