AWS HealthImaging now supports OAuth 2.0-compatible identity providers for authentication of DICOMweb requests using OpenID Connect (OIDC). With OIDC authentication, you can manage secure access to DICOM resources using your organization’s standard procedures for creating, enabling, and disabling user accounts.
With this launch, you can now use existing identity providers (IdPs)—such as Amazon Cognito, Okta, or Auth0—to issue JSON Web Tokens (JWTs) that authorize secure access to your DICOMweb endpoints. This launch makes it simpler to integrate AWS HealthImaging into existing medical imaging applications and expands HealthImaging’s support of DICOMweb standard interfaces that rely on OAuth 2.0-compatible authentication. Support for OIDC is limited to DICOMweb REST API requests. HealthImaging includes native support for AWS Identity and Access Management (IAM) users and roles for authentication of all API requests.
Support for OpenID Connect (OIDC) is available in all AWS Regions where AWS HealthImaging is generally available: US East (N. Virginia), US West (Oregon), Asia Pacific (Sydney), and Europe (Ireland).
To learn more, visit Using DICOMweb with AWS HealthImaging.
Categories: general:products/aws-healthimaging,general:products/amazon-machine-learning,marketing:marchitecture/management-and-governance
Source: Amazon Web Services
Latest Posts
- (Updated) Microsoft Teams: Shorter meeting URLs [MC772556]
- Introducing AWS CDK Refactor (Preview)
- AWS Elastic Beanstalk now supports IPv6 in dual stack configuration for Application and Network Load Balancers
- Amazon Bedrock AgentCore Gateway supports AWS PrivateLink invocation and invocation logging
