New answers tagged

1

The error message here is telling you that you are not allowed to enable MFADelete without having an authenticated token with mfa. Meaning the executing principal must have logged in with MFA. essentially the API call on the cli would be something like this aws --profile my_profile s3api put-bucket-versioning --bucket bucket-name --versioning configuration '...


0

I loaded the kubeconfig before and the error disappeared. $ export KUBECONFIG=~/workspace/myrepo/_kube/dev/kubeconfig $ AWS_ACCESS_KEY_ID=<my_legit_key> AWS_SECRET_ACCESS_KEY=<my_legit_secret_key> kops validate cluster --wait 10m --state="s3://<my_bucket_name>" --name=<my_cluster_name> ## And it worked If the kubeconfig ...


0

Try running the kops get command to see if kOps can read the configuration stored in the s3 bucket correctly. If you get an error then you probably have missed a required configuration in your environment. I had a similar issue but I was using Named profiles for AWS. I had to set an extra variable export AWS_SDK_LOAD_CONFIG=1 for kOps to pick up the settings ...


1

Set automountServiceAccountToken: true in your pod specification in both of the jobs and the deployment. Ref: https://discuss.kubernetes.io/t/nginx-ingress-install-failure/5379/4


3

There are many AWS services which requires a network interface such as AWS load balancers, Lambda, NAT gateway, VPC endpoints etc. For each AWS load balancer, it may use up to 2 IPs and 1 IP for 1 lambda function. I would recommend to check the network interface section under EC2 service which will show you all the IPs which are currently being used and ...


2

I figured it out. The stub resource has to have a provider that is configured with the proper AWS region. All these security groups were in us-west-2. You need this: resource "aws_security_group" "rds-launch-wizard-2" { provider = aws.us_west_2 } instead of this: resource "aws_security_group" "rds-launch-wizard-2" {} ...


1

AWS docs show what the reserved IP's in each subnet are: https://docs.aws.amazon.com/vpc/latest/userguide/VPC_Subnets.html The gist of it is, the first 4 IP's and the last IP of the subnet are off limits if your subnet starts with the same IP as the VPC. It's probably a good rule of thumb to avoid assuming these IPs are going to be available in any subnet ...


1

These are presumably proprietary tools for EC2 and GCE respectively. The need for predictive VM autoscaling is pretty strong for Virtual Machines since provisioning time can be measured in the 10's of minutes depending on the configuration. Conversely, application spin-up time in Kubernetes is typically measured in seconds. Predictive scaling for the ...


Top 50 recent answers are included