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

[awskinesisexporter] [RESOLVED] Cross account support #33891

Closed
chepati opened this issue Jul 3, 2024 · 9 comments
Closed

[awskinesisexporter] [RESOLVED] Cross account support #33891

chepati opened this issue Jul 3, 2024 · 9 comments
Labels
enhancement New feature or request exporter/awskinesis good first issue Good for newcomers

Comments

@chepati
Copy link

chepati commented Jul 3, 2024

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

@chepati chepati added enhancement New feature or request needs triage New item requiring triage labels Jul 3, 2024
Copy link
Contributor

github-actions bot commented Jul 3, 2024

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@chepati
Copy link
Author

chepati commented Jul 8, 2024

Bump.

@MovieStoreGuy MovieStoreGuy added good first issue Good for newcomers and removed needs triage New item requiring triage labels Jul 8, 2024
@MovieStoreGuy
Copy link
Contributor

Mmm, interesting.

Makes sense. I don't think it would be too hard of a change to implement.

@parambath92
Copy link

Hi @MovieStoreGuy , I would like to work on this issue.

Copy link
Contributor

github-actions bot commented Sep 9, 2024

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 @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@github-actions github-actions bot added the Stale label Sep 9, 2024
@HongChenTW
Copy link

Hi @parambath92, are you still working on this issue? If not, I would like to implement this feature.

@parambath92
Copy link

Hi @HongChenTW , I couldn't work on this feature. Please go ahead.

@HongChenTW
Copy link

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 role to assume role and specify region to locate the stream region.

@github-actions github-actions bot removed the Stale label Sep 10, 2024
HongChenTW added a commit to HongChenTW/opentelemetry-collector-contrib that referenced this issue Sep 10, 2024
HongChenTW added a commit to HongChenTW/opentelemetry-collector-contrib that referenced this issue Sep 20, 2024
HongChenTW added a commit to HongChenTW/opentelemetry-collector-contrib that referenced this issue Sep 24, 2024
@chepati
Copy link
Author

chepati commented Oct 7, 2024

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 role to assume role and specify region to locate the stream region.

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.

@chepati chepati changed the title [awskinesisexporter] Cross account support [awskinesisexporter] [RESOLVED] Cross account support Oct 7, 2024
HongChenTW added a commit to HongChenTW/opentelemetry-collector-contrib that referenced this issue Oct 10, 2024
@chepati chepati closed this as completed Oct 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request exporter/awskinesis good first issue Good for newcomers
Projects
None yet
4 participants