Skip to content
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

Open
1 task
b-eisen opened this issue Nov 9, 2023 · 5 comments
Open
1 task

AdotCollectorAddOn - Ability to Deploy in AWS GovCloud(US) #874

b-eisen opened this issue Nov 9, 2023 · 5 comments

Comments

@b-eisen
Copy link

b-eisen commented Nov 9, 2023

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

  • I may be able to implement this feature request

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

@b-eisen b-eisen added the feature label Nov 9, 2023
Copy link

github-actions bot commented Feb 8, 2024

This issue has been automatically marked as stale because it has been open 60 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

@github-actions github-actions bot added the stale label Feb 8, 2024
@shapirov103 shapirov103 removed the stale label Feb 8, 2024
Copy link

github-actions bot commented May 9, 2024

This issue has been automatically marked as stale because it has been open 60 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

@github-actions github-actions bot added the stale label May 9, 2024
Copy link

github-actions bot commented Jul 8, 2024

Issue closed due to inactivity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jul 8, 2024
@shapirov103 shapirov103 reopened this Jul 8, 2024
@shapirov103 shapirov103 removed the stale label Jul 8, 2024
Copy link

github-actions bot commented Oct 7, 2024

This issue has been automatically marked as stale because it has been open 60 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

@github-actions github-actions bot added the stale label Oct 7, 2024
@shapirov103 shapirov103 removed the stale label Oct 7, 2024
Copy link

github-actions bot commented Jan 6, 2025

This issue has been automatically marked as stale because it has been open 60 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

@github-actions github-actions bot added the stale label Jan 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants