Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Deployment Scripts fail in AWS region ap-south-1 #29627

Closed
ChetanBhasin opened this issue Jul 26, 2016 · 3 comments
Closed

Deployment Scripts fail in AWS region ap-south-1 #29627

ChetanBhasin opened this issue Jul 26, 2016 · 3 comments
Assignees
@justinsb
Labels
area/kubectl

Comments

@ChetanBhasin
Copy link

While using the deployment script, we get the following trace:

cluster/kube-up.sh 
... Starting cluster in ap-south-1a using provider aws
... calling verify-prereqs
... calling kube-up
Starting cluster using os distro: jessie
Uploading to Amazon S3
Creating kubernetes-staging-644ab343278c61ddae0ca23171f5546e
make_bucket failed: s3://kubernetes-staging-644ab343278c61ddae0ca23171f5546e/ An error occurred (InvalidRequest) when calling the CreateBucket operation: You are attempting to operate on a bucket in a region that requires Signature Version 4.  You can fix this issue by explicitly providing the correct region location using the --region argument, the AWS_DEFAULT_REGION environment variable, or the region variable in the AWS CLI configuration file.  You can get the bucket's location by running "aws s3api get-bucket-location --bucket BUCKET".

It looks like the AMIs are not available for this region. I got this trace after I copied the Kubernetes default AMI and to this region and setting AWS_IMAGE environment variable.
@oba11
Copy link

oba11 commented Aug 28, 2016

Also option --cloud-provider="aws" doesnt work for ap-south-1 as well. Not sure if the aws-sdk needs to be updated to reflect the new region

@oba11
Copy link

oba11 commented Aug 29, 2016

For my issue, #28428 fixes it but need to wait till v1.4

@justinsb justinsb self-assigned this Nov 17, 2016
@justinsb
Copy link
Member

I believe this is now fixed - please reopen if not

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@justinsb justinsb

Labels
area/kubectl
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@justinsb @oba11 @ChetanBhasin @k8s-github-robot