gistfile1.txt

--> ok so I do this: 
aws s3 sync s3://one.region s3://to.another --dryrun --profile pms-east --source-region us-east-1 --region us-west-1 --sse-c AES256 --sse-c-key '496ea1ea1b35561e2342342474db682692a8bbf03f3e22aasdasd1c9fed1a9b605a69137'

--> and on the dry run it says:
"Completed 56 part(s) with ... file(s) remaining
(dryrun) copy: s3://blah to s3://blah2  etc..."

--> when I take off the dryrun I get this on every single file copy when using --sse-c in tandem with --sse-c-key:
"A client error (InvalidArgument) occurred when calling the CreateMultipartUpload operation: 
The secret key was invalid for the specified algorithm."

--> I've used various key lengths.  the only thing I've not done is successfully generate a key using aws cli kms generate-data-key or any other amazon provisioned device

aws cli version is up-to-date
  # aws --version
  aws-cli/1.10.1 Python/2.6.6 Linux/2.6.32-504.23.4.el6.x86_64 botocore/1.3.23
  centos
  
I have yet to find an example that shows what they key looks like or how to generate it.
it's supposed to be a base64 encoded string, which is what I have tried multiple times at 192, 256, and other bit-lengths.
I wish there were examples of how to generate the key and what it looks like.