Instance type at Bioconductor - Cloud AMI
1
0
Entering edit mode
@rohmatul-fajriyah-5675
Last seen 10.2 years ago
Dear All, After sometimes I did not use Cloud AMI. Today I started to use it again. But I was failed and got this message: Error Template validation error: Parameter InstanceType failed to satisfy constraint: Choose a valid EC2 instance type from http://aws.amazon.com/ec2/instance-types/ I chose m3.2xlarge. I tried it several times and still I was failed and got the message above. When I tried with the t1.micro, it worked perfectly. But t1.micro is not what I need currently. I followed the steps from here Bioconductor - Cloud AMI. Is there anything that I might have missed on it, please? Many thanks in advance. With kind regards, R Fajriyah [[alternative HTML version deleted]]
• 1.3k views
ADD COMMENT •
0
Entering edit mode
Dan Tenenbaum ★ 8.2k
@dan-tenenbaum-4256
Last seen 5 months ago
United States
Hi, ----- Original Message ----- > From: "Rohmatul Fajriyah" <rfajriyah at="" yahoo.com=""> > To: bioconductor at r-project.org > Sent: Saturday, May 3, 2014 8:36:25 PM > Subject: [BioC] Instance type at Bioconductor - Cloud AMI > > Dear All, > > After sometimes I did not use Cloud AMI. > Today I started to use it again. > > But I was failed and got this message: > Error > Template validation error: Parameter InstanceType failed to satisfy > constraint: Choose a valid EC2 instance type from > http://aws.amazon.com/ec2/instance-types/ > > I chose m3.2xlarge. > I tried it several times and still I was failed and got the message > above. > When I tried with the t1.micro, it worked perfectly. But t1.micro is > not what I need currently. > > I followed the steps from here?Bioconductor - Cloud AMI. > Is there anything that I might have missed on it, please? > The m3 instance types are new since those CloudFormation templates were created. I just updated the templates to add them so try again and it should work. Dan > Many thanks in advance. > > With kind regards, > R Fajriyah > [[alternative HTML version deleted]] > > > _______________________________________________ > Bioconductor mailing list > Bioconductor at r-project.org > https://stat.ethz.ch/mailman/listinfo/bioconductor > Search the archives: > http://news.gmane.org/gmane.science.biology.informatics.conductor
ADD COMMENT •
0
Entering edit mode
Dear Dr. Dan, I just tried it and still got an error as follows: Error Template validation error: Parameter BiocVersion failed to satisfy constraint: Must be 2.8, 2.9, 2.10, 2.11, 2.12, or 2.13 Perhaps, I missed something? Thank you very much. With kind regards, R Fajriyah On Sunday, May 4, 2014 8:53 AM, Dan Tenenbaum <dtenenba@fhcrc.org> wrote: Hi, ----- Original Message ----- > From: "Rohmatul Fajriyah" <rfajriyah@yahoo.com> > To: bioconductor@r-project.org > Sent: Saturday, May 3, 2014 8:36:25 PM > Subject: [BioC] Instance type at Bioconductor - Cloud AMI > > Dear All, > > After sometimes I did not use Cloud AMI. > Today I started to use it again. > > But I was failed and got this message: > Error > Template validation error: Parameter InstanceType failed to satisfy > constraint: Choose a valid EC2 instance type from > http://aws.amazon.com/ec2/instance-types/ > > I chose m3.2xlarge. > I tried it several times and still I was failed and got the message > above. > When I tried with the t1.micro, it worked perfectly. But t1.micro is > not what I need currently. > > I followed the steps from here Bioconductor - Cloud AMI. > Is there anything that I might have missed on it, please? > The m3 instance types are new since those CloudFormation templates were created. I just updated the templates to add them so try again and it should work. Dan > Many thanks in advance. > > With kind regards, > R Fajriyah >     [[alternative HTML version deleted]] > > > _______________________________________________ > Bioconductor mailing list > Bioconductor@r-project.org > https://stat.ethz.ch/mailman/listinfo/bioconductor > Search the archives: > http://news.gmane.org/gmane.science.biology.informatics.conductor [[alternative HTML version deleted]]
ADD REPLY •
0
Entering edit mode
----- Original Message ----- > From: "Rohmatul Fajriyah" <rfajriyah at="" yahoo.com=""> > To: "Dan Tenenbaum" <dtenenba at="" fhcrc.org=""> > Cc: bioconductor at r-project.org > Sent: Sunday, May 4, 2014 5:37:28 AM > Subject: Re: [BioC] Instance type at Bioconductor - Cloud AMI > > > > Dear Dr. Dan, > > > I just tried it and still got an error as follows: Error > > Template validation error: Parameter BiocVersion failed to satisfy > constraint: Must be 2.8, 2.9, 2.10, 2.11, 2.12, or 2.13 > > > Perhaps, I missed something? > > This should also be fixed now. BTW, which template are you using and which BioC version do you want to use it with? Dan > Thank you very much. > > > With kind regards, > R Fajriyah > > > > > > On Sunday, May 4, 2014 8:53 AM, Dan Tenenbaum <dtenenba at="" fhcrc.org=""> > wrote: > > Hi, > > ----- Original Message ----- > > From: "Rohmatul Fajriyah" < rfajriyah at yahoo.com > > > To: bioconductor at r-project.org > > Sent: Saturday, May 3, 2014 8:36:25 PM > > Subject: [BioC] Instance type at Bioconductor - Cloud AMI > > > > Dear All, > > > > After sometimes I did not use Cloud AMI. > > Today I started to use it again. > > > > But I was failed and got this message: > > Error > > Template validation error: Parameter InstanceType failed to satisfy > > constraint: Choose a valid EC2 instance type from > > http://aws.amazon.com/ec2/instance-types/ > > > > I chose m3.2xlarge. > > I tried it several times and still I was failed and got the message > > above. > > When I tried with the t1.micro, it worked perfectly. But t1.micro > > is > > not what I need currently. > > > > I followed the steps from here Bioconductor - Cloud AMI. > > Is there anything that I might have missed on it, please? > > > > > The m3 instance types are new since those CloudFormation templates > were created. > > I just updated the templates to add them so try again and it should > work. > > Dan > > > > Many thanks in advance. > > > > With kind regards, > > R Fajriyah > > [[alternative HTML version deleted]] > > > > > > _______________________________________________ > > Bioconductor mailing list > > Bioconductor at r-project.org > > https://stat.ethz.ch/mailman/listinfo/bioconductor > > Search the archives: > > http://news.gmane.org/gmane.science.biology.informatics.conductor > >
ADD REPLY •
0
Entering edit mode
Dear Dr. Dan, Apologise for late reply. I still get the same error as in the previous email. I use the template as Bioconductor-AMI suggestion: Specify an Amazon S3 template URL. About BioC version, I think 2.12 or 2.13 is fine. Thank you very much. With kind regards, R Fajriyah On Sunday, May 4, 2014 5:24 PM, Dan Tenenbaum <dtenenba@fhcrc.org> wrote: ----- Original Message ----- > From: "Rohmatul Fajriyah" <rfajriyah@yahoo.com> > To: "Dan Tenenbaum" <dtenenba@fhcrc.org> > Cc: bioconductor@r-project.org > Sent: Sunday, May 4, 2014 5:37:28 AM > Subject: Re: [BioC] Instance type at Bioconductor - Cloud AMI > > > > Dear Dr. Dan, > > > I just tried it and still got an error as follows: Error > > Template validation error: Parameter BiocVersion failed to satisfy > constraint: Must be 2.8, 2.9, 2.10, 2.11, 2.12, or 2.13 > > > Perhaps, I missed something? > > This should also be fixed now. BTW, which template are you using and which BioC version do you want to use it with? Dan > Thank you very much. > > > With kind regards, > R Fajriyah > > > > > > On Sunday, May 4, 2014 8:53 AM, Dan Tenenbaum <dtenenba@fhcrc.org> > wrote: > > Hi, > > ----- Original Message ----- > > From: "Rohmatul Fajriyah" < rfajriyah@yahoo.com > > > To: bioconductor@r-project.org > > Sent: Saturday, May 3, 2014 8:36:25 PM > > Subject: [BioC] Instance type at Bioconductor - Cloud AMI > > > > Dear All, > > > > After sometimes I did not use Cloud AMI. > > Today I started to use it again. > > > > But I was failed and got this message: > > Error > > Template validation error: Parameter InstanceType failed to satisfy > > constraint: Choose a valid EC2 instance type from > > http://aws.amazon.com/ec2/instance-types/ > > > > I chose m3.2xlarge. > > I tried it several times and still I was failed and got the message > > above. > > When I tried with the t1.micro, it worked perfectly. But t1.micro > > is > > not what I need currently. > > > > I followed the steps from here Bioconductor - Cloud AMI. > > Is there anything that I might have missed on it, please? > > > > > The m3 instance types are new since those CloudFormation templates > were created. > > I just updated the templates to add them so try again and it should > work. > > Dan > > > > Many thanks in advance. > > > > With kind regards, > > R Fajriyah > > [[alternative HTML version deleted]] > > > > > > _______________________________________________ > > Bioconductor mailing list > > Bioconductor@r-project.org > > https://stat.ethz.ch/mailman/listinfo/bioconductor > > Search the archives: > > http://news.gmane.org/gmane.science.biology.informatics.conductor > > [[alternative HTML version deleted]]
ADD REPLY •
0
Entering edit mode
----- Original Message ----- > From: "Rohmatul Fajriyah" <rfajriyah at="" yahoo.com=""> > To: "Dan Tenenbaum" <dtenenba at="" fhcrc.org=""> > Cc: bioconductor at r-project.org > Sent: Sunday, May 4, 2014 11:34:43 AM > Subject: Re: [BioC] Instance type at Bioconductor - Cloud AMI > > > > Dear Dr. Dan, > > > Apologise for late reply. > I still get the same error as in the previous email. > I use the template as Bioconductor-AMI suggestion: Specify an Amazon > S3 template URL. > About BioC version, I think 2.12 or 2.13 is fine. > I apologize for the inconvenience. It is working now. Dan > > Thank you very much. > > > With kind regards, > R Fajriyah > > > > > > > > > > > > > > > > On Sunday, May 4, 2014 5:24 PM, Dan Tenenbaum <dtenenba at="" fhcrc.org=""> > wrote: > > > > ----- Original Message ----- > > From: "Rohmatul Fajriyah" < rfajriyah at yahoo.com > > > To: "Dan Tenenbaum" < dtenenba at fhcrc.org > > > Cc: bioconductor at r-project.org > > Sent: Sunday, May 4, 2014 5:37:28 AM > > Subject: Re: [BioC] Instance type at Bioconductor - Cloud AMI > > > > > > > > Dear Dr. Dan, > > > > > > I just tried it and still got an error as follows: Error > > > > Template validation error: Parameter BiocVersion failed to satisfy > > constraint: Must be 2.8, 2.9, 2.10, 2.11, 2.12, or 2.13 > > > > > > Perhaps, I missed something? > > > > > > > This should also be fixed now. BTW, which template are you using and > which BioC version do you want to use it with? > > > > Dan > > > > Thank you very much. > > > > > > With kind regards, > > R Fajriyah > > > > > > > > > > > > On Sunday, May 4, 2014 8:53 AM, Dan Tenenbaum < dtenenba at fhcrc.org > > > > > wrote: > > > > Hi, > > > > ----- Original Message ----- > > > From: "Rohmatul Fajriyah" < rfajriyah at yahoo.com > > > > To: bioconductor at r-project.org > > > Sent: Saturday, May 3, 2014 8:36:25 PM > > > Subject: [BioC] Instance type at Bioconductor - Cloud AMI > > > > > > Dear All, > > > > > > After sometimes I did not use Cloud AMI. > > > Today I started to use it again. > > > > > > But I was failed and got this message: > > > Error > > > Template validation error: Parameter InstanceType failed to > > > satisfy > > > constraint: Choose a valid EC2 instance type from > > > http://aws.amazon.com/ec2/instance-types/ > > > > > > I chose m3.2xlarge. > > > I tried it several times and still I was failed and got the > > > message > > > above. > > > When I tried with the t1.micro, it worked perfectly. But t1.micro > > > is > > > not what I need currently. > > > > > > I followed the steps from here Bioconductor - Cloud AMI. > > > Is there anything that I might have missed on it, please? > > > > > > > > > The m3 instance types are new since those CloudFormation templates > > were created. > > > > I just updated the templates to add them so try again and it should > > work. > > > > Dan > > > > > > > Many thanks in advance. > > > > > > With kind regards, > > > R Fajriyah > > > [[alternative HTML version deleted]] > > > > > > > > > _______________________________________________ > > > Bioconductor mailing list > > > Bioconductor at r-project.org > > > https://stat.ethz.ch/mailman/listinfo/bioconductor > > > Search the archives: > > > http://news.gmane.org/gmane.science.biology.informatics.conductor > > > > > > >
ADD REPLY •
0
Entering edit mode
Dear Dr. Dan, No need to apologise, it really helped me a lot. yes, now it is working perfectly. But I have another question, if it is ok, because I got another error: Error Stack creation error: Stack [StartBioconductorAMI] already exists As far as I am concerned, I created it previously and have deleted it. Also I have checked that I don't have it now. Is there thing that I missed it again? Thank you very much. With kind regards, R Fajriyah On Sunday, May 4, 2014 8:42 PM, Dan Tenenbaum <dtenenba@fhcrc.org> wrote: ----- Original Message ----- > From: "Rohmatul Fajriyah" <rfajriyah@yahoo.com> > To: "Dan Tenenbaum" <dtenenba@fhcrc.org> > Cc: bioconductor@r-project.org > Sent: Sunday, May 4, 2014 11:34:43 AM > Subject: Re: [BioC] Instance type at Bioconductor - Cloud AMI > > > > Dear Dr. Dan, > > > Apologise for late reply. > I still get the same error as in the previous email. > I use the template as Bioconductor-AMI suggestion: Specify an Amazon > S3 template URL. > About BioC version, I think 2.12 or 2.13 is fine. > I apologize for the inconvenience. It is working now. Dan > > Thank you very much. > > > With kind regards, > R Fajriyah > > > > > > > > > > > > > > > > On Sunday, May 4, 2014 5:24 PM, Dan Tenenbaum <dtenenba@fhcrc.org> > wrote: > > > > ----- Original Message ----- > > From: "Rohmatul Fajriyah" < rfajriyah@yahoo.com > > > To: "Dan Tenenbaum" < dtenenba@fhcrc.org > > > Cc: bioconductor@r-project.org > > Sent: Sunday, May 4, 2014 5:37:28 AM > > Subject: Re: [BioC] Instance type at Bioconductor - Cloud AMI > > > > > > > > Dear Dr. Dan, > > > > > > I just tried it and still got an error as follows: Error > > > > Template validation error: Parameter BiocVersion failed to satisfy > > constraint: Must be 2.8, 2.9, 2.10, 2.11, 2.12, or 2.13 > > > > > > Perhaps, I missed something? > > > > > > > This should also be fixed now. BTW, which template are you using and > which BioC version do you want to use it with? > > > > Dan > > > > Thank you very much. > > > > > > With kind regards, > > R Fajriyah > > > > > > > > > > > > On Sunday, May 4, 2014 8:53 AM, Dan Tenenbaum < dtenenba@fhcrc.org > > > > > wrote: > > > > Hi, > > > > ----- Original Message ----- > > > From: "Rohmatul Fajriyah" < rfajriyah@yahoo.com > > > > To: bioconductor@r-project.org > > > Sent: Saturday, May 3, 2014 8:36:25 PM > > > Subject: [BioC] Instance type at Bioconductor - Cloud AMI > > > > > > Dear All, > > > > > > After sometimes I did not use Cloud AMI. > > > Today I started to use it again. > > > > > > But I was failed and got this message: > > > Error > > > Template validation error: Parameter InstanceType failed to > > > satisfy > > > constraint: Choose a valid EC2 instance type from > > > http://aws.amazon.com/ec2/instance-types/ > > > > > > I chose m3.2xlarge. > > > I tried it several times and still I was failed and got the > > > message > > > above. > > > When I tried with the t1.micro, it worked perfectly. But t1.micro > > > is > > > not what I need currently. > > > > > > I followed the steps from here Bioconductor - Cloud AMI. > > > Is there anything that I might have missed on it, please? > > > > > > > > > The m3 instance types are new since those CloudFormation templates > > were created. > > > > I just updated the templates to add them so try again and it should > > work. > > > > Dan > > > > > > > Many thanks in advance. > > > > > > With kind regards, > > > R Fajriyah > > > [[alternative HTML version deleted]] > > > > > > > > > _______________________________________________ > > > Bioconductor mailing list > > > Bioconductor@r-project.org > > > https://stat.ethz.ch/mailman/listinfo/bioconductor > > > Search the archives: > > > http://news.gmane.org/gmane.science.biology.informatics.conductor > > > > > > > [[alternative HTML version deleted]]
ADD REPLY •
0
Entering edit mode
----- Original Message ----- > From: "Rohmatul Fajriyah" <rfajriyah at="" yahoo.com=""> > To: "Dan Tenenbaum" <dtenenba at="" fhcrc.org=""> > Cc: bioconductor at r-project.org > Sent: Sunday, May 4, 2014 11:54:36 AM > Subject: Re: [BioC] Instance type at Bioconductor - Cloud AMI > > > > Dear Dr. Dan, > > > No need to apologise, it really helped me a lot. > yes, now it is working perfectly. > But I have another question, if it is ok, because I got another > error: Error > > > Stack creation error: Stack [StartBioconductorAMI] already exists > > > As far as I am concerned, I created it previously and have deleted > it. > Also I have checked that I don't have it now. > > > Is there thing that I missed it again? > Double and triple check that you really deleted it because if you haven't you will be charged money. When you are satisfied that it is really deleted, You can click on the "Start the AMI" link again on the page at http://bioconductor.org/help/bioconductor-cloud-ami/ And where it suggests "StartBioconductorAMI" as the Stack Name, you can change that to something else, like "StartBioconductorAMI2". Dan > > Thank you very much. > > > With kind regards, > R Fajriyah > > > > > > On Sunday, May 4, 2014 8:42 PM, Dan Tenenbaum <dtenenba at="" fhcrc.org=""> > wrote: > > > > ----- Original Message ----- > > From: "Rohmatul Fajriyah" < rfajriyah at yahoo.com > > > To: "Dan Tenenbaum" < dtenenba at fhcrc.org > > > Cc: bioconductor at r-project.org > > Sent: Sunday, May 4, 2014 11:34:43 AM > > Subject: Re: [BioC] Instance type at Bioconductor - Cloud AMI > > > > > > > > Dear Dr. Dan, > > > > > > Apologise for late reply. > > I still get the same error as in the previous email. > > I use the template as Bioconductor-AMI suggestion: Specify an > > Amazon > > S3 template URL. > > About BioC version, I think 2.12 or 2.13 is fine. > > > > I apologize for the inconvenience. It is working now. > > Dan > > > > > > Thank you very much. > > > > > > With kind regards, > > R Fajriyah > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Sunday, May 4, 2014 5:24 PM, Dan Tenenbaum < dtenenba at fhcrc.org > > > > > wrote: > > > > > > > > ----- Original Message ----- > > > From: "Rohmatul Fajriyah" < rfajriyah at yahoo.com > > > > To: "Dan Tenenbaum" < dtenenba at fhcrc.org > > > > Cc: bioconductor at r-project.org > > > Sent: Sunday, May 4, 2014 5:37:28 AM > > > Subject: Re: [BioC] Instance type at Bioconductor - Cloud AMI > > > > > > > > > > > > Dear Dr. Dan, > > > > > > > > > I just tried it and still got an error as follows: Error > > > > > > Template validation error: Parameter BiocVersion failed to > > > satisfy > > > constraint: Must be 2.8, 2.9, 2.10, 2.11, 2.12, or 2.13 > > > > > > > > > Perhaps, I missed something? > > > > > > > > > > > > This should also be fixed now. BTW, which template are you using > > and > > which BioC version do you want to use it with? > > > > > > > > Dan > > > > > > > Thank you very much. > > > > > > > > > With kind regards, > > > R Fajriyah > > > > > > > > > > > > > > > > > > On Sunday, May 4, 2014 8:53 AM, Dan Tenenbaum < > > > dtenenba at fhcrc.org > > > > > > > wrote: > > > > > > Hi, > > > > > > ----- Original Message ----- > > > > From: "Rohmatul Fajriyah" < rfajriyah at yahoo.com > > > > > To: bioconductor at r-project.org > > > > Sent: Saturday, May 3, 2014 8:36:25 PM > > > > Subject: [BioC] Instance type at Bioconductor - Cloud AMI > > > > > > > > Dear All, > > > > > > > > After sometimes I did not use Cloud AMI. > > > > Today I started to use it again. > > > > > > > > But I was failed and got this message: > > > > Error > > > > Template validation error: Parameter InstanceType failed to > > > > satisfy > > > > constraint: Choose a valid EC2 instance type from > > > > http://aws.amazon.com/ec2/instance-types/ > > > > > > > > I chose m3.2xlarge. > > > > I tried it several times and still I was failed and got the > > > > message > > > > above. > > > > When I tried with the t1.micro, it worked perfectly. But > > > > t1.micro > > > > is > > > > not what I need currently. > > > > > > > > I followed the steps from here Bioconductor - Cloud AMI. > > > > Is there anything that I might have missed on it, please? > > > > > > > > > > > > > The m3 instance types are new since those CloudFormation > > > templates > > > were created. > > > > > > I just updated the templates to add them so try again and it > > > should > > > work. > > > > > > Dan > > > > > > > > > > Many thanks in advance. > > > > > > > > With kind regards, > > > > R Fajriyah > > > > [[alternative HTML version deleted]] > > > > > > > > > > > > _______________________________________________ > > > > Bioconductor mailing list > > > > Bioconductor at r-project.org > > > > https://stat.ethz.ch/mailman/listinfo/bioconductor > > > > Search the archives: > > > > http://news.gmane.org/gmane.science.biology.informatics.conductor > > > > > > > > > > > > > > >
ADD REPLY •
0
Entering edit mode
Dear Dr. Dan, yes, I created different name and then I discovered that the StartBioconductorAMI is still there. No wonder I got that error. I did not delete it properly, I supposed. Now everything is ok. Many thanks for the help. With kind regards, R Fajriyah On Sunday, May 4, 2014 8:58 PM, Dan Tenenbaum <dtenenba@fhcrc.org> wrote: ----- Original Message ----- > From: "Rohmatul Fajriyah" <rfajriyah@yahoo.com> > To: "Dan Tenenbaum" <dtenenba@fhcrc.org> > Cc: bioconductor@r-project.org > Sent: Sunday, May 4, 2014 11:54:36 AM > Subject: Re: [BioC] Instance type at Bioconductor - Cloud AMI > > > > Dear Dr. Dan, > > > No need to apologise, it really helped me a lot. > yes, now it is working perfectly. > But I have another question, if it is ok, because I got another > error: Error > > > Stack creation error: Stack [StartBioconductorAMI] already exists > > > As far as I am concerned, I created it previously and have deleted > it. > Also I have checked that I don't have it now. > > > Is there thing that I missed it again? > Double and triple check that you really deleted it because if you haven't you will be charged money. When you are satisfied that it is really deleted, You can click on the "Start the AMI" link again on the page at http://bioconductor.org/help/bioconductor-cloud-ami/ And where it suggests "StartBioconductorAMI" as the Stack Name, you can change that to something else, like "StartBioconductorAMI2". Dan > > Thank you very much. > > > With kind regards, > R Fajriyah > > > > > > On Sunday, May 4, 2014 8:42 PM, Dan Tenenbaum <dtenenba@fhcrc.org> > wrote: > > > > ----- Original Message ----- > > From: "Rohmatul Fajriyah" < rfajriyah@yahoo.com > > > To: "Dan Tenenbaum" < dtenenba@fhcrc.org > > > Cc: bioconductor@r-project.org > > Sent: Sunday, May 4, 2014 11:34:43 AM > > Subject: Re: [BioC] Instance type at Bioconductor - Cloud AMI > > > > > > > > Dear Dr. Dan, > > > > > > Apologise for late reply. > > I still get the same error as in the previous email. > > I use the template as Bioconductor-AMI suggestion: Specify an > > Amazon > > S3 template URL. > > About BioC version, I think 2.12 or 2.13 is fine. > > > > I apologize for the inconvenience. It is working now. > > Dan > > > > > > Thank you very much. > > > > > > With kind regards, > > R Fajriyah > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Sunday, May 4, 2014 5:24 PM, Dan Tenenbaum < dtenenba@fhcrc.org > > > > > wrote: > > > > > > > > ----- Original Message ----- > > > From: "Rohmatul Fajriyah" < rfajriyah@yahoo.com > > > > To: "Dan Tenenbaum" < dtenenba@fhcrc.org > > > > Cc: bioconductor@r-project.org > > > Sent: Sunday, May 4, 2014 5:37:28 AM > > > Subject: Re: [BioC] Instance type at Bioconductor - Cloud AMI > > > > > > > > > > > > Dear Dr. Dan, > > > > > > > > > I just tried it and still got an error as follows: Error > > > > > > Template validation error: Parameter BiocVersion failed to > > > satisfy > > > constraint: Must be 2.8, 2.9, 2.10, 2.11, 2.12, or 2.13 > > > > > > > > > Perhaps, I missed something? > > > > > > > > > > > > This should also be fixed now. BTW, which template are you using > > and > > which BioC version do you want to use it with? > > > > > > > > Dan > > > > > > > Thank you very much. > > > > > > > > > With kind regards, > > > R Fajriyah > > > > > > > > > > > > > > > > > > On Sunday, May 4, 2014 8:53 AM, Dan Tenenbaum < > > > dtenenba@fhcrc.org > > > > > > > wrote: > > > > > > Hi, > > > > > > ----- Original Message ----- > > > > From: "Rohmatul Fajriyah" < rfajriyah@yahoo.com > > > > > To: bioconductor@r-project.org > > > > Sent: Saturday, May 3, 2014 8:36:25 PM > > > > Subject: [BioC] Instance type at Bioconductor - Cloud AMI > > > > > > > > Dear All, > > > > > > > > After sometimes I did not use Cloud AMI. > > > > Today I started to use it again. > > > > > > > > But I was failed and got this message: > > > > Error > > > > Template validation error: Parameter InstanceType failed to > > > > satisfy > > > > constraint: Choose a valid EC2 instance type from > > > > http://aws.amazon.com/ec2/instance-types/ > > > > > > > > I chose m3.2xlarge. > > > > I tried it several times and still I was failed and got the > > > > message > > > > above. > > > > When I tried with the t1.micro, it worked perfectly. But > > > > t1.micro > > > > is > > > > not what I need currently. > > > > > > > > I followed the steps from here Bioconductor - Cloud AMI. > > > > Is there anything that I might have missed on it, please? > > > > > > > > > > > > > The m3 instance types are new since those CloudFormation > > > templates > > > were created. > > > > > > I just updated the templates to add them so try again and it > > > should > > > work. > > > > > > Dan > > > > > > > > > > Many thanks in advance. > > > > > > > > With kind regards, > > > > R Fajriyah > > > > [[alternative HTML version deleted]] > > > > > > > > > > > > _______________________________________________ > > > > Bioconductor mailing list > > > > Bioconductor@r-project.org > > > > https://stat.ethz.ch/mailman/listinfo/bioconductor > > > > Search the archives: > > > > http://news.gmane.org/gmane.science.biology.informatics.conductor > > > > > > > > > > > > > > > [[alternative HTML version deleted]]
ADD REPLY •

Login before adding your answer.

Similar Posts
Loading Similar Posts
Traffic: 569 users visited in the last hour
Content Search
Users
Tags
Badges
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6