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

get service account setup for graphite/sparql api access #1288

Closed
sheridancbio opened this issue Apr 26, 2024 · 1 comment
Closed

get service account setup for graphite/sparql api access #1288

sheridancbio opened this issue Apr 26, 2024 · 1 comment
Labels
backend-scrum items centered around engineering activities Oncotree

Comments

@sheridancbio
Copy link
Collaborator

Done Condition (What do we need? Why do we need it? Keep this is small as possible!)

request and test service account access

Technical Description (How are we going to achieve the above)

Potential Issues

Dependencies

Technical Requirements

Outside People/Teams

Changes

@sheridancbio sheridancbio added backend-scrum items centered around engineering activities Oncotree labels Apr 26, 2024
@sheridancbio
Copy link
Collaborator Author

We have had several exchanges with the OMOP/Extract team and with synaptica. Our understanding is now that there is a bastion server to ssh tunnel through. However, despite the claim that they have set us up there, we have been unable to connect with any of the ssh keypairs we created. It is possible that our source IP (pipielines3) is coming from an IP address which is not permitted by the bastion server (because this machine is in the AWS cloud). We are not sure and Manda has been emailing them for further guidance.

@sheridancbio sheridancbio changed the title get service account setup for graphite api access get service account setup for graphite/sparql api access May 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend-scrum items centered around engineering activities Oncotree
Projects
None yet
Development

No branches or pull requests

2 participants