-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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.
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
Our IAM policies do not work in cn-north-1 #27
Labels
Comments
justinsb
changed the title
IAM policies do not work in cn-north-1
Our IAM policies do not work in cn-north-1
Jul 5, 2016
justinsb
added a commit
to justinsb/kops
that referenced
this issue
Jul 14, 2016
justinsb
added a commit
to justinsb/kops
that referenced
this issue
Jul 14, 2016
justinsb
added a commit
to justinsb/kops
that referenced
this issue
Jul 14, 2016
justinsb
added a commit
to justinsb/kops
that referenced
this issue
Jul 14, 2016
justinsb
added a commit
to justinsb/kops
that referenced
this issue
Jul 22, 2016
justinsb
added a commit
to justinsb/kops
that referenced
this issue
Jul 22, 2016
cloudbow
pushed a commit
to cloudbow/kops
that referenced
this issue
Jun 8, 2018
…re/kubernetes-helm-jenkins to develop * commit '5f53e8fbba8107d194ded85cd51d84d2c4002720': Make Ingress resources ready Make all kube objects exposed for ingress to use default namespace Enable Jenkins for Kubernetes Make all kube objects exposed for ingress to use default namespace Make application work on Kubernetes cluster
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I believe the IAM service name should be
ec2.amazonaws.com.cn
The text was updated successfully, but these errors were encountered: