AWS CodeStar aws-akl-meetup-Sep2017-bp

Editor's Notes

• #2: Introduce myself. Hi, I am John Reilly Pospos, I work as a Cloud Solutions Consultant for Bulletproof New Zealand. My work involves ensuring clients follow AWS best-practices and security guidelines, Implementing AWS infrastructures using Infrastructure as Code tools, I also review existing IaC implementations. Implementing/Reviewing CI/CD pipelines and writing documents. I have worked as a Network Engineer for a BPO company, A Linux Admin for an E-Commerce company based in the US, A Systems Engineer for a crowdsourcing marketplace based in Australia, A Senior Operations Engineer for an Insurance Company.From time to time, I also help James, AWS Auckland Community Meetup’s main man.
• #4: Each check-in will be verified by an automated build, allowing teams to detect problems early.  The ability to detect errors quickly, and locate them more easily. 
• #5: CD is the natural extension of CI. The idea is to make releases boring, so that teams can deliver frequently and shorten the feedback cycle.
• #6: Ideally, it will look something like this.
• #7: Here is a list of a few popular CI/CD tools and services currently available.
• #8: Of course when we talk about CI/CD we always have to touch version control. So, here are a few popular ones.
• #9: Here are a few popular CI/CD tools and services currently available.
• #10: AWS attempts to simplify and unify this with their latest Developer Tools offering.
• #11: Together, these services help you to securely store and version control your application's source code and automatically build, test, and deploy your application to AWS or to your on-premises environment. This enables you and your team to start practicing Continuous Integration and Continuous Delivery The Developer Tool are based on Amazon’s in-house DevOps Practices and Tools 
• #12: We wont go deeper into all services available under the Developer Tools but here is list.
• #13: Let’s start talking about CodeStar.
• #14: AWS CodeStar provides a unified user interface, enabling you to easily manage your software development activities in one place. Setup your CI/CD toolchain in minutes.
• #15: In the days of yore, to have a fully functioning CI/CD you have to spend days, weeks or even months (depending on your mileage) to setup Jenkins and sometimes it doesn’t go well. Recently we see a lot of CI/CD offerings being peddled around and they make life easier. But you have to consider management of a separate service, billing, security. If you are a startup or just working on your next great idea and you want to get off the ground as fast as possible you might want to consider this.
• #16: Demo time.
• #17: Now that you have it working make sure that you take necessary steps to secure your resources. Using CodeBuild you can drop in a yaml file inside your code that tells codebuild how it would build and test your app.
• #18: If you are already using Infrastructure as code you can simply configure the developer tools to use resources provisioned by CloudFormation or Terraform. Start deploying on dev, staging and prod environments by simply modifying CodeStar. If you install the latest awscli you will see that it already has placeholders for interacting with the CodeStar api. Currently it doesn’t work, but the fact that its there means that AWS plans on having the API exposed via awscli or the SDK.
• #20: Currently you can deploy to Standalone EC2s, Elastic Beanstalk and Lambda. No need to open multiple apps/services on multiple windows or browser just to manage your whole toolchain. Like all AWS tools user access, management and security is done through IAM. Ready-made templates for Java, JavaScript, PHP, Ruby, C#, and Python.
• #21: CodeStar was publicly introduced on April 2017, yes it is quite new. The wizard just doesn’t give that much options to begin with.
• #22: Here are some useful links to get you started with your AWS Codestar journey. Slides and recordings will be uploaded as well.