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

Ability to set the awsSigV4 to use API Gateway as the Service Scope #207

Open
hv-rruiz opened this issue Aug 12, 2022 · 2 comments
Open
Labels
enhancement New feature or request

Comments

@hv-rruiz
Copy link
Contributor

Hi all!

I wanted to ask if it's possible to scope the awsSigV4 object w/in the DataPlaneClient to something other than rum. The service attribute only allows rum.

I've noticed in the documentation it's possible to set an endpoint to an API gateway proxy. However the permissions won't quite work with the client to only give the client the ability to call the API because this signature is scoped to rum.

We wanted to set the guest role arn to have execute-api permissions to our API. Then from there we can forward it along to RUM.

Thank you!

@hv-rruiz hv-rruiz changed the title Ability to set the awsSigV4 to scope to API Gateway Ability to set the awsSigV4 to use API Gateway as the Service Scope Aug 12, 2022
@qhanam
Copy link
Member

qhanam commented Aug 23, 2022

Hi! The service argument for sigv4 isn't configurable in the web client right now. You could fork the web client and change it and we could potentially upstream it later if it's useful.

Do you need the data between the web client and API gateway to be signed? If you don't, you could provide dummy credentials via setAwsCredentials and strip the sigv4 header in API gateway.

@qhanam qhanam added the enhancement New feature or request label Jul 17, 2023
@nikevp
Copy link

nikevp commented Apr 30, 2024

+1, signing with execute-api would make life easier.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants