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

Allow identity blocks in sidecar_task blocks #24660

Open
seanamos opened this issue Dec 13, 2024 · 1 comment
Open

Allow identity blocks in sidecar_task blocks #24660

seanamos opened this issue Dec 13, 2024 · 1 comment

Comments

@seanamos
Copy link

seanamos commented Dec 13, 2024

Proposal

Allow the use of identity blocks in sidecar_task blocks.

This is similar in nature to #17987 .

Use-cases

Allow the injection of AWS identities into terminating gateways that invoke lambdas.

Attempted Solutions

It is possible the suggestion at #17987 (comment) would also work for this, that is to construct the job json in it's entirety manually and submit it. I have not tested this yet.

An easier to implement workaround is to add permissions to the EC2 IAM role/policy, but this is undesirable.

If #17987 were implemented and one has a Vault AWS secret backend, that could also work as an alternative solution.

@tgross
Copy link
Member

tgross commented Dec 13, 2024

Hi @seanamos! This seems like a reasonable idea. I'll mark it for roadmapping, but I'm not sure when we'd get to this. You may want to look into deploying the gateway job as a standalone task, similar to what we've demonstrated in https://github.com/hashicorp-guides/consul-api-gateway-on-nomad

@tgross tgross added the theme/consul/connect Consul Connect integration label Dec 13, 2024
@tgross tgross moved this from Needs Triage to Needs Roadmapping in Nomad - Community Issues Triage Dec 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Needs Roadmapping
Development

No branches or pull requests

2 participants