[
https://issues.apache.org/jira/browse/BEAM-3821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17131727#comment-17131727
]
Beam JIRA Bot commented on BEAM-3821:
-------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> Support a pluggable key management system (KMS)
> -----------------------------------------------
>
> Key: BEAM-3821
> URL: https://issues.apache.org/jira/browse/BEAM-3821
> Project: Beam
> Issue Type: Improvement
> Components: sdk-ideas
> Reporter: Luke Cwik
> Priority: P2
> Labels: stale-P2
>
> Different runners want to have access to various cloud providers such as AWS,
> Azure, GCP yet still provide users the ability to have control over access to
> those resources.
> Adding support for a pluggable key management solution would allow users to
> have control over which resources are accessed and when.
> Some concrete scenarios would be:
> * Access S3 and GCS from a Yarn cluster running on AWS.
> * Control S3 resource access for pipelines executing on Google Cloud Dataflow
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
