-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[awskinesisexporter] [RESOLVED] Cross account support #33891
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Bump. |
Mmm, interesting. Makes sense. I don't think it would be too hard of a change to implement. |
Hi @MovieStoreGuy , I would like to work on this issue. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Hi @parambath92, are you still working on this issue? If not, I would like to implement this feature. |
Hi @HongChenTW , I couldn't work on this feature. Please go ahead. |
Hi @chepati, would you mind to share the details of how you deploy the otel collector? While developing this feature, I was also checking the abilities of this exporter, and found out that we could send metrics to another AWS account by specify |
…telemetry#33891) Resolves open-telemetry#33891 Signed-off-by: Hong Chen <hong.chen.7219@gmail.com>
…telemetry#33891) Resolves open-telemetry#33891 Signed-off-by: Hong Chen <hong.chen.7219@gmail.com>
…telemetry#33891) Resolves open-telemetry#33891 Signed-off-by: Hong Chen <hong.chen.7219@gmail.com>
Hi, @HongChenTW. First of all, apologies for the very late reply. Yes, you're right, specifying an IAM role works. In fact, that's how I got it working. I am deploying otel collector to an EKS cluster, running under a specific service account. That service account is bound to an IAM role which is allowed to assume an IAM role in another AWS account, where the kinesis datastream is. Once this is all set up, exporting to the kinesis datastream in another AWS account just works. You can close this feature request. Perhaps a good explanation in the exporter's README will be useful. Thanks all who took the time to look into this. |
…telemetry#33891) Resolves open-telemetry#33891 Signed-off-by: Hong Chen <hong.chen.7219@gmail.com>
Component(s)
exporter/awskinesis
Is your feature request related to a problem? Please describe.
My OTel collector is in AWS account A and my Kinesis datastream is in AWS account B. It seems the awskinesisexporter can't send metrics to the datastream in another AWS account. If I specify just the stream_name, the exporter assumes it's in the same account/region and complains that it can't find it.
Describe the solution you'd like
Ideally, I can use the ARN of my kinesis datastream in stream_name:
exporters:
awskinesis:
aws:
stream_name: arn:aws:kinesis:REGION:ACCOUNT_ID:stream/stream_name
and as long as I have my IAM roles / policies set up correctly, the exporter should be able to talk to the kinesis datastream in the other AWS account.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: