This one can be confusing at first but the most probable reason is you put your programmatic ACCESS KEY in the SSH config (~/.ssh/config) instead of the ACCESS KEY associated with your public key.
It seems it is not possible to scale down redis-clusters. I always end up with an error: Cannot scale from cache.t2.medium to cache.t2.micro So the only solution i found was to create another cluster, update references to it in my launch templates and then run another update after that to delete the old one.
One of the biggest hurdles i have faced in my recent tests with CloudFormation was that i can take a lot of time to test your CloudFormation scripts. The online designer works but is quirky so what's left if you want to test our your infrastructure script? The answer is simple, just test it out … Continue reading CloudFormation development tips
So i hit this small roadbump the other day. I am pretty much discovering CloudFormation, what an awesome tool, but somethings are inconsistent here and there depending on your approach. The error So i had this error ... for parameter iamInstanceProfile.name is invalid. Invalid IAM Instance Profile name (Service: AmazonEC2; Status Code: 400; Error Code: … Continue reading IamInstanceRole and CloudFormation
Context In the last few days, i had to setup a complete AWS infrastructure for a startup. The objective was to have different ec2 machines that are auto-scaled into existence access an s3 bucket on initialization to get some configuration that shouldn't be baked into a snapshot. The script was working fine when i was … Continue reading S3 access on an ec2 instance in a private subnet