-
Notifications
You must be signed in to change notification settings - Fork 208
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
AdotCollectorAddOn - Ability to Deploy in AWS GovCloud(US) #874
Comments
This issue has been automatically marked as stale because it has been open 60 days |
This issue has been automatically marked as stale because it has been open 60 days |
Issue closed due to inactivity. |
This issue has been automatically marked as stale because it has been open 60 days |
This issue has been automatically marked as stale because it has been open 60 days |
Describe the feature
The AdotCollectorAddOn utilizes a custom IAM policy (https://github.com/aws-quickstart/cdk-eks-blueprints/blob/main/lib/addons/adot/iam-policy.ts) that contains a hardcoded AWS partition. Because of this the addon cannot be used for EKS Blueprints deployments to AWS GovCloud(US) or other partitions.
This feature would allow for the addon to be deployed in partitions beyond the standard one.
Use Case
Customers operate EKS workloads in partitions other than the standard AWS partition and should be able to use all addons via EKS blueprints.
Proposed Solution
Provide the partition in the policy at synth/deployment time using the cdk.Aws.PARTITION as an interpolated value in the policy.
Other Information
No response
Acknowledgements
CDK version used
2.99.1
EKS Blueprints Version
1.12.0
Node.js Version
v21.1.0
Environment details (OS name and version, etc.)
MacOS 13.5
The text was updated successfully, but these errors were encountered: