Tips, Expertise, Articles and Advice from the Pro's for Your Website or Blog to Succeed
First off, happy new year!
After facing a few patches of public registry downtime at the end of the year (both Docker Hub and ECR), one of our first goals of 2022 was to implement pull-through caching of public images. This would allow Shipyard users to continue building, testing, and reviewing their applications, even when outages happen.
AWS cloud architecture solutions require infrastructure to run your platform solutions. Infrastructure includes compute technologies, databases, queues, and more. Each needs to be specified and built before turning on your platform solution.
There are many different ways you can choose to build your AWS infrastructure. Each method has its benefits and drawbacks that should be known before choosing how to create your production platform.
The introduction of Cloud Development Kit (CDK) by AWS has been a valuable addition to its bouquet of services. CDK is an Infrastructure as Code (IAC) service from AWS. Yes, you could create cloudformation scripts in json or yaml and use it to provision your infrastructure. But who likes to write json files? I have always been averse to developing large json scripts to provision and maintain my infrastructure on AWS. I always wondered why isn’t there a simpler way of doing this – like developing deployment scripts on my favourite programming language.
AWS heard me alright and came up with CDK last year. CDK helps to define infrastructure in code and provision them through Cloudformation. With CDK it’s so much easier to build reusable deployment scripts. Moreover, it facilitates the use of the core features of a programming language in structuring and generating Cloudformation scripts. I decided to take it out for a spin to ascertain whether it really keeps up to its promises. Here, I’ll provide a sneak peek - an example to create a static website on S3.