https://dchua.com/tags/aws/ Recent content in aws on davidchua Hugo -- gohugo.io en-us Wed, 27 Jul 2016 00:00:00 +0000 https://dchua.com/posts/2016-07-27-how-to-change-instance-size-of-an-existing-kubernetes-cluster/ Wed, 27 Jul 2016 00:00:00 +0000 https://dchua.com/posts/2016-07-27-how-to-change-instance-size-of-an-existing-kubernetes-cluster/ Just recently, I was trying to reverse my poor decision of starting my Kubernetes Cluster on AWS with a very simple t2.micro nodes. If you’re on AWS, your nodes are probably created via an Auto-scaling group. To change your instance size, you’ll need to: Copy the launch configuration that Kubernetes is probably running. Change the instance size of the launch configuration Update the Kubernetes Auto Scaling Group to use the new launch configuration ? https://dchua.com/posts/2016-07-21-setting-up-amazon-vpc-to-vpc-peer-connection/ Thu, 21 Jul 2016 00:00:00 +0000 https://dchua.com/posts/2016-07-21-setting-up-amazon-vpc-to-vpc-peer-connection/ Need to communicate between 2 Amazon VPCs securely and privately? Here’s some of my notes on setting up a VPC Peer Connection. Prerequisite Ensure that your VPCs do not share the same CIDR block and can are in different subnets Link up Note, VPC Peering is one-way only so if you create a VPC peer connection from one VPC (lets call this A) and another VPC (B), only A will be able to communicate and access B. https://dchua.com/posts/2014-12-13-how-to-make-a-s3-bucket-publicly-accessible/ Sat, 13 Dec 2014 00:00:00 +0000 https://dchua.com/posts/2014-12-13-how-to-make-a-s3-bucket-publicly-accessible/ In your AWS Console, select the Bucket that you’re trying to make public. Under Permissions, add the following bucket policy: { "Version": "2008-10-17", "Id": "...", "Statement": [ { "Sid": "...", "Effect": "Allow", "Principal": { "AWS": "*" }, "Action": "s3:GetObject", "Resource": "arn:aws:s3:::<REPLACE_THIS_WITH_YOUR_BUCKET_NAME>/*" } ] } https://dchua.com/posts/2013-08-18-migrate-all-dns-zones-from-zerigo-over-to-aws-route-53/ Sun, 18 Aug 2013 00:00:00 +0000 https://dchua.com/posts/2013-08-18-migrate-all-dns-zones-from-zerigo-over-to-aws-route-53/ So yesterday there was another major downtime on Zerigo and its about the last straw I had with the service. Not only the service was down for most of the day, causing some of my domains to fail updating, not a single e-mail or communication was made on the part of the management team to inform us about what has happened. If I didn’t check zerigostatus.com, I wouldn’t have realized that the entire service was down. https://dchua.com/posts/2012-01-16-aws-to-include-windows-instances-into-its-free-usage-tier/ Mon, 16 Jan 2012 00:00:00 +0000 https://dchua.com/posts/2012-01-16-aws-to-include-windows-instances-into-its-free-usage-tier/ This is on-top of the existing 750 micro-instance hours a month for linux instances! Which means you can now run 2 micro-instances of Windows and Linux each under the Free Usage Tier! From AWS Blog The AWS Free Usage Tier now allows you to run Microsoft Windows Server 2008 R2 on an EC2 t1.micro instance for up to 750 hours per month. This benefit is open to new AWS customers and to those who are already participating in the Free Usage Tier, and is available in all AWS Regions with the exception of GovCloud.