-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[managed-cloud] Policy and module updates; Support for CloudFormation #39
Conversation
- !Ref ControlPlaneManagerArn | ||
- !Ref VendorSupportRoleArn | ||
Action: sts:AssumeRole | ||
- Sid: AllowStreamNativeControlPlaneAccess |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think we need this here, as the access first comes from the our AWS account, not direct from the control plane cluster
Principal: | ||
AWS: | ||
- !Ref ControlPlaneManagerArn | ||
- !Ref VendorSupportRoleArn |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My thinking is we can still just use a single ARN as trust, as we can just grant go through control plane ARN
TODO:
|
This adds a CloudFormation template to the
managed-cloud
module, as an alternative method of deploying the resources used for StreamNative's vendor access.Additional policy updates have been made to the
managed-cloud
module to support access by StreamNative's Control Plane for Cloud Managed environments.