-
Notifications
You must be signed in to change notification settings - Fork 37
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
omics service error: could not resolve host #804
Comments
Hi sorry about that. I am able to replicate the issue. Not sure about what is causing this bug but will look into it :) |
The endpoint (omics.eu-west-1.amazonaws.com) looks correct https://docs.aws.amazon.com/general/latest/gr/healthomics-quotas.html. Will need to double check why it isn't being resolved correctly |
@DyfanJones thanks! I really appreciate that. I do not know at all what is going on there, I hope you can fix it! I really like the package. |
@DyfanJones The quoted documentation page is incorrect. HealthOmics is using multiple service endpoints: workflows-omics, tags-omics, storage-omics, control-storage-omics, analytics-omics. See AWS HealthOmics and interface VPC endpoints (AWS PrivateLink). |
@lyschoening I saw that too! But I do not know then how to provide the paws::omics() the correct endpoint. All my tries have given connection errors. |
I think I have found the issue (@lyschoening thanks for highlighting the issue with aws documentation). I believe the issue is coming down to hostPrefix not being picked up in Note: Botocore has takes this into account |
As this issue and issue in |
I can update this ticket once I have developed a possible solution |
This is to confirm the hostPrefix is missing from the endpoint: library(paws.storage)
client = omics(config(credentials(profile = "paws"), endpoint = "https://workflows-omics.us-east-1.amazonaws.com"))
client$list_workflows()
#> $items
#> list()
#>
#> $nextToken
#> character(0) Created on 2024-07-16 with reprex v2.1.1 |
Updated make.paws package to take into account host_prefix. Will have to regen the paws sdk before you guys can fully test it out on your own systems :) |
Whenever you tell me, I will try again. Just tell me what to do :) |
I have regenerated paws on r-universe: install.packages('paws', repos = c('https://paws-r.r-universe.dev', 'https://cloud.r-project.org'))
library(paws.storage)
client = omics(config(credentials(profile = "paws")))
client$list_workflows() Please have a go and tell me if this fully fixes the issue you have raised 😄 @lyschoening @joseale2310 |
Note: this should raise your |
Hi! I have reinstalled the packages as per your previous post, restarted my R session and tried to run the last two lines of code. I get this error now:
I can confirm that my paws packages are 0.7.0 and paws.common is 0.7.5 |
Interesting I am not sure why this is appearing. I haven't modified any classes. Are you able to provide a trace to help me debug? |
This is what i get from traceback. Something to do with date/time?
|
oh interesting, that part hasn't been modified 🤔 This might be a new bug I am not aware of. I might need to create a workflow to see why this is causing an error :) |
At least it changed from one error to another. Progress! On the mean time, I am running a custom function that calls the AWS CLI, writes the output in a json file then loads the json file in R. |
@joseale2310 can you try the dev version: remotes::install_github("dyfanjones/paws/paws.common", ref = "unix_time") I believe this should fix you issue |
That did seem to work! Now I do get the API response fine. Thanks! |
Perfect, this is going to be a fairly big release for paws. Are you ok using |
I will wait until the new release. The workaround is working fine for me so far! |
Paws 0.7.0 has been released. Closing issue |
Hi,
I am trying to use the omics service using the paws R package. When I try to use anything from the service I get:
I see the omics service is split into workflows, analytics and storage, and I can successfully access my workflows using the AWS CLI. I can also confirm that, for example, s3 works fine using paws::s3(). I guess it is because s3.eu-west-1.amazonaws.com is an actual endpoint in AWS (you can type that in the browser and it will redirect you to https://aws.amazon.com/s3/).
Do I need to provide some different endpoint? Trying to do the following also returns an error:
Session Info
The text was updated successfully, but these errors were encountered: