DevOps in AWS Radio: Parameter Store with AWS CodePipeline (Episode 6)
In this episode, Paul Duvall and Brian Jakovich are joined by Trey McElhattan from Stelligent to cover recent DevOps in AWS news and speak about Using Parameter Store with AWS CodePipeline.
Here are the show notes:
DevOps in AWS News
- Continuous Delivery
- AWS CodePipeline Adds Support for AWS CodeBuild as a Test Action – “Now, unit tests can be performed easily, without the need for a build artifact.”
- How to Do Continuous Integration and Continuous Deployment with AWS Lambda and AWS CodePipeline – Video and https://github.com/awslabs/aws-serverless-samfarm
- Automated Compliance and Remediation
- Automatic Remediation with Observable and AWS – “A proof-of-concept approach to automate IP blocking using alerts from our Observable Cloud service.”
- Announcing the AWS Health Tools Repository – “a community-based source of tools to automate remediation actions and customize Health alerts.”
- AWS Config PutEvaluations TestMode – Test AWS Config without paying for resource usage
- How to Audit Your AWS Resources for Security Compliance by Using Custom AWS Config Rules
- Creating AWS Config Managed rules with AWS CloudFormation templates
- What is Parameter Store? What are its key features?
- Which AWS tools does it use?
- What are the alternatives to Parameter store?
- Benefits of using Parameter Store along versus alternatives?
- Can you use Parameter Store if you’re not using AWS services and tools?
- Which are supported: SDKs, CLI, Console, CloudFormation, etc.?
- What are the different ways to store string using Parameter Store?
- What’s the pricing model for Parameter Store?
- How do you use Parameter Store in the context of a deployment pipeline – and, specifically, with AWS CodePipeline?
Related Blog Posts
- Using Parameter Store with AWS CodePipeline
- Managing Secrets for Amazon ECS Applications Using Parameter Store and IAM Roles for Tasks
- Overview of Parameter Store
About DevOps in AWS Radio
On DevOps in AWS Radio, we cover topics around applying DevOps principles and practices such as Continuous Delivery in the Amazon Web Services cloud. This is what we do at Stelligent for our customers. We’ll bring listeners into our roundtables and speak with engineers who’ve recently published on our blog and we’ll also be reaching out to the wider DevOps in AWS community to get their thoughts and insights.
The overall vision of this podcast is to describe how listeners can create a one-click (or “no click”) implementation of their software systems and infrastructure in the Amazon Web Services cloud so that teams can deliver software to users whenever there’s a business need to do so. The podcast will delve into the cultural, process, tooling, and organizational changes that can make this possible including:
- Automation of
- Networks (e.g. VPC)
- Compute (EC2, Containers, Serverless, etc.)
- Storage (e.g. S3, EBS, etc.)
- Database and Data (RDS, DynamoDB, etc.)
- Organizational and Team Structures and Practices
- Team and Organization Communication and Collaboration
- Cultural Indicators
- Version control systems and processes
- Deployment Pipelines
- Orchestration of software delivery workflows
- Execution of these workflows
- Application/service Architectures – e.g. Microservices
- Automation of Build and deployment processes
- Automation of testing and other verification approaches, tools and systems
- Automation of security practices and approaches
- Continuous Feedback systems
- Many other Topics…
Stelligent Amazon Pollycast