unable to set S3 for persistent storage in us-east-1 about spinnaker.github.io

[jervi]

I validated buckets in eu-west-1, so it shouldn't have to be us-west-1...

[ttomsu]

@lwander or @jervi, can you take a look at this?

[lwander]

quick fix - region for some reason needs to be us-west-1 (I don't know enough about the AWS support to say why). I have a fix for the error explaining this coming in the next halyard release (0.22.0)

[camilosantana]

So it's not a region issue? Is there a policy I need to write up that's implied in the instructions?

[jervi]

I just tested this in a fresh AWS instance, and it worked as expected. I provided eu-west-1 where you have $REGION above.

[camilosantana]

Thanks. I'll scrap this instance and related IAM objects then start again.

…

On Wed, 7 Jun 2017, 07:30 Jørgen Jervidalo, ***@***.***> wrote: I just tested this in a fresh AWS instance, and it worked as expected. I provided eu-west-1 where you have $REGION above. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#193 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AG67bnSRC9dYqEEZGP16C9ldfRcYwJlpks5sBrPvgaJpZM4NyLJn> .

[camilosantana]

@jervi

i'm still getting the same issue.

I deploy an Ubuntu 14 image from ami-ad4b33bb in us-east-1

i install halyard per instructions

curl -O https://raw.githubusercontent.com/spinnaker/halyard/master/install/stable/InstallHalyard.sh
sudo bash InstallHalyard.sh

i attempt to configure storage

$ echo $ACCESS_KEY | \
> hal config storage s3 edit --access-key-id $ACCESS_KEY_ID \
>   --region us-east-1 \
>   --bucket $BUCKET \
>   --root-folder d1c294e8_spinnaker_persistent_data \
>   --secret-access-key
+ Get current deployment
  Success
+ Get persistent store
  Success
- Edit persistent store
  Failure
Problems in Global:
! ERROR Unexpected exception: java.lang.RuntimeException: Failed to
  invoke validate() on "S3Validator" for node "S3PersistentStore

- Failed to edit persistent store "s3".

it fails.

I can configure, as @lwander stated, in us-west-1

$ echo $ACCESS_KEY | \
> hal config storage s3 edit --access-key-id $ACCESS_KEY_ID \
>   --region us-west-1 \
>   --bucket $BUCKET \
>   --root-folder d1c294e8_spinnaker_persistent_data \
>   --secret-access-key
+ Get current deployment
  Success
+ Get persistent store
  Success
+ Edit persistent store
  Success
Problems in default.persistentStorage:
- WARNING Your deployment will most likely fail until you configure
  and enable a persistent store.

Problems in default:
- WARNING You have not yet selected a version of Spinnaker to
  deploy.
? Options include:
  - 1.0.0

Conclusion: At this time, for US at least, it seems we have to create s3 bucket in us-west-1