123-456-7890
contactus@cloudifyops.com
Reach Us

Automating Creation of Cloud Compute Instances with AWS CloudFormation

ABOUT THE CLIENT

Our customer offers mobile solutions enabling providers to better measure, monitor, and manage wound care. Their mission is to raise the standard of wound care by equipping healthcare providers with modern tools, enabling better wound care with better data and collaboration.

Wound care today lacks the level of technology and resources compared to other areas of healthcare. As a result, the tools available to wound care professionals are outdated and cumbersome. The customer is changing this by bringing technology and innovation to the forefront of wound care.

THE CHALLENGE

  • AMI creation and versioning for ease of spinning up instances
  • Better Package and Artifact management
  • Packaging Linux OS and applications as a standard golden AMI
  • Better maintenance, ease of deploying/spinning an instance, error fixing, versioning
  • Security and supportability
  • There was no formal release process for application development
  • Need for automated pre-release acceptance testing and deployment AMIs

THE SOLUTION

Our team developed CloudFormation templates for AMI automation

AMI Builder template

  • We added the necessary stages for the 3 AMI – Wazuh, GVM and Nessus automation in the AMI builder CloudFormation template
  • The changes will create a Code Pipeline for each of the AMIs. The pipeline included Code Commit repository and Code Build for each of the AMIs, similar to other pipeline stages already present in the template

Infrastructure Automation Templates

Initially, there were 6 CloudFormation templates in the Customer repo for infrastructure automation/server (AMI) deployment. We added templates for Wazuh and GVM AMIs and made some changes to the existing templates as per the AMI requirements. As CloudifyOps team did not have access to the customer GovCloud account, we created/modified all the templates for the commercial AWS account and minor changes like region name were needed. Other common changes are the ssh key, SSL ARN and AMI IDs. 

BENEFITS DELIVERED

  • Services Integration – Manage the deployment of individual services or resources and multiple resources like IAM, ALB, VPC, S3, Autoscaling groups, SG groups
  • Ensured customer services and applications are consistent and identical
  • Reducing manual overhead once AMIs are launched
  • Simplified infrastructure management by defining parameters, resources and their properties
  • Customer was able to reuse the CloudFormation templates to ensure multiple resources can be set up using a single design
  • Benefits of higher stability, no unintentional changes to the setting or resource provisioning

Services

Solutions

Recent Blogs

Privacy Settings
We use cookies to enhance your experience while using our website. If you are using our Services via a browser you can restrict, block or remove cookies through your web browser settings. We also use content and scripts from third parties that may use tracking technologies. You can selectively provide your consent below to allow such third party embeds. For complete information about the cookies we use, data we collect and how we process them, please check our Privacy Policy
Youtube
Consent to display content from - Youtube
Vimeo
Consent to display content from - Vimeo
Google Maps
Consent to display content from - Google
Spotify
Consent to display content from - Spotify
Sound Cloud
Consent to display content from - Sound
Save
Contact Us