In a nutshell: if you're using a version of GATK older than 2.7, you need to request a key to disable Phone Home (if you don't already have one). See below for a full explanation.


As you may know, the GATK includes a reporting mechanism called Phone Home that sends us runtime statistics about usage and bugs. These statistics (which you can read more about here) help us make development decisions, e.g. prioritize bug fixes and new features, as well as track adoption of new versions and tools.

The system uses an AWS cloud service as a data repository, called a "bucket", which GATK accesses using an encryption key. We currently have two active AWS keys for the Phone Home bucket. GATK versions 2.6 and older use one AWS key, and versions 2.7 and later use another AWS key.

For practical reasons, we need to deactivate the old AWS key, which means that GATK jobs run using a version older than 2.7 may end with a Phone Home failure unless the system is deactivated. To be clear, the GATK analysis itself will complete successfully, but the GATK may exit with a fail code. This may cause issues in pipelines and potentially fill up error logs.

The best way to avoid these problems is to upgrade to the latest version of GATK, which you should seriously consider anyway in order to get the best possible results out of your analysis. However, if you are unable to upgrade to a recent version, we recommend that you disable the Phone Home system. To do so, you will need to follow these two simple steps:

  1. Request a GATK key using this online form. In the "justification" field, please write "AWS key deprecation", indicate which version of GATK you are using, and if possible let us know why you are unable to upgrade to a recent version. You can expect to receive your key within 1 business day.

  2. Once you have the key, apply it to all GATK jobs by adding -et NO_ET -K your.key (where your.key is the path to the key file you obtained from us) to every GATK command line.

We expect this workaround will suppress any issues EXCEPT in versions prior to 1.5, in which the Phone Home system cannot be deactivated. For versions 1.4 and older, there is nothing we can do, and you will have to either put up with the errors, or upgrade to a newer version (which you should really really do anyway!).

Let us know in the comments if you have any trouble or questions.


Return to topComment on this article in the forum




- Recent posts


- Upcoming events

See Events calendar for full list and dates


- Recent events

See Events calendar for full list and dates



- Follow us on Twitter

GATK Dev Team

@gatk_dev

Our thanks to @edgenome for hosting us! A pleasure as always! https://t.co/C9XgB34OBX
22 Jul 17
RT @vchris21: FireCloud. Something to watch out for while working with GATK variant discovery. Very interesting https://t.co/oo8zzbG41f #ga…
19 Jul 17
RT @dr_gabry: Another great GATK workshop in Cambridge @BioInfoCambs @gatk_dev. Looking forward to see you in 2018!!!!!! https://t.co/v55zR
14 Jul 17
@tai_pach @wordpressdotcom The first beta is actually out already :) https://t.co/ILiFifpdcG Formal announcement coming next week.
8 Jul 17
RT @geoffjentry: @BGI_Genomics adopts GATK, @WDL_dev and Cromwell. Cromwell to get AliCloud support. New GATK & WDL outreach effort in Chin…
2 Jul 17

- Our favorite tweets from others

The @gatk_dev team, that delivered an excellent "GATK Best Practices for Variant Discovery" workshop this week, on… https://t.co/Z8GNduuDeJ
20 Jul 17
Amazing session @edgenome with @gatk_dev comes to an end. Enriched learning! Thx #gatk #gatk2017 #Genomics #Edinburgh #Bioinformatics
19 Jul 17
Great day of lectures on GATK Best Practices yesterday. Very clear and useful. Thanks! @gatk_dev @edgenome
18 Jul 17
Another great GATK workshop in Cambridge @BioInfoCambs @gatk_dev. Looking forward to see you in 2018!!!!!! https://t.co/v55zRztpHL
14 Jul 17
Getting started with #GoogleCloud and learnt that #Cromwell + #WDL by @broadinstitute is just awesome. Go #GATK
13 Jun 17
See more of our favorite tweets...