Bamboo plan for AWS build part 4


Swap URL: This is for blue/green deployment. The idea is to update the floating DNS to point to different stack's ELB CNAME. It allows us to easily divert the traffics to different backend stack, but keep it transparent to users. Cloudformation snippet "Resources": { "Route53DNSRecord": { "Properties": { "Comment": "Floating DNS Record", "HostedZoneName": { "Fn::Join": … Continue reading Bamboo plan for AWS build part 4

Bamboo plan for AWS build part 3


Continue with the Bamboo plan for AWS build, now it is time to look into the deployment plan. For each environment, I got 4 sub plans: Create Stack, Deploy Config, Swap URL and Delete Stack. Create Stack: As explained in the part 1, Stack means the infrastructure. e.g A Nginx stack has those components: ELB, Autoscaling … Continue reading Bamboo plan for AWS build part 3

Error response from daemon: Get https://index.docker.io/v1/…: x509: certificate signed by unknown authority


Error response from daemon: Get https://index.docker.io/v1/...: x509: certificate signed by unknown authority You have probably seen similar errors as above when trying to access dockerhub registry behind a corp proxy. I have the same issue here. And I think the issue may be caused by two reasons: 1) index.docker.io now is redirected to registry.hub.docker.com 2) Your … Continue reading Error response from daemon: Get https://index.docker.io/v1/…: x509: certificate signed by unknown authority

Check DNS Cache when deploy Multi-AZ RDS


It is a common practice to enable mutli-AZ when deploy RDS in AWS to provide high availability. That's not all. There is one more thing you need to check - DNS cache setting of your applications/codes. If you overlook it, the hight availability design may not work as you expect. Imagine that when RDS detects the failure … Continue reading Check DNS Cache when deploy Multi-AZ RDS