[ 
https://issues.apache.org/jira/browse/JCLOUDS-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16474406#comment-16474406
 ] 

Aled Sage commented on JCLOUDS-1132:
------------------------------------

This still seems to be a problem for me with jclouds 2.1.0. I set 
{{volumeOptions.isEncrypted(true)}}, and it failed with:
{noformat}
org.jclouds.aws.AWSResponseException: request POST 
https://ec2.eu-west-1.amazonaws.com/ HTTP/1.1 failed with code 400, error: 
AWSError{requestId='xxxxxxxx-xxxx-xxxx-xxxx-67dc264118f0', requestToken='null', 
code='UnknownParameter', message='The parameter Encrypted is not recognized', 
context='{Response=, Errors=}'}{noformat}
---

The {{volumeType}} works for me with {{gp2}} and {{io1}}.

> Amazon AWS - Create Volume - query params reported as unrecognized
> ------------------------------------------------------------------
>
>                 Key: JCLOUDS-1132
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-1132
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-compute
>    Affects Versions: 1.9.0, 1.9.2
>         Environment: Amazon AWS EC2 management console
>            Reporter: Tusa Mihail Cristian
>            Priority: Major
>
> Let say that I want to create a Volume that is encrypted. So, I set the 
> encrypted on "true"... in request query params apear "&Encrypted=true". In 
> this case the error that I got is: 
> <Response><Errors><Error><Code>UnknownParameter</Code><Message>The parameter 
> Encrypted is not 
> recognized</Message></Error></Errors><RequestID>c874434a-b00e-425d-baf4-18087441603a</RequestID></Response>
>  
> instead it should be: "&Encrypted=1" as it is shown in Amazon docs: 
> http://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_CreateVolume.html 
> in Example/Sample request. The problems are also related with Volume Type. If 
> not specified than creates a standard volume but if anything specified (any 
> of valid Values: standard | io1 | gp2 | sc1 | st1 ) the same error with 
> unrecognized param is received.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to