This client is evolving its build, bundle, and deploy operations into a predictable, repeatable delivery model as it moves more of its operations into Amazon Web Services (AWS). As a result, more knowledge and experience is needed in the use of cloud operations tools, processes, and procedures as well as how to fully evolve the use of development behaviors, tools, processes, and procedures in the cloud.
Prior to this engagement, the client hired Trility to help pursue a secure, safe serverless environment across its enterprise, so they turned to our team again to help bootstrap the design, implementation, and operational evolution of AWS operations and implement a data storage solution using CloudFormation for a secured enterprise framework.
AWS CloudFormation was selected to automate the secure deployment of AWS resources across business units to help the client's teams adapt quickly and automate testing.
In order to scale using CloudFormation, Trility proposed an automated continuous delivery pipeline ecosystem using the client-chosen tools, Terraform and Jenkins, as well as RDS Aurora MySQL and S3 solutions to design, direct, and implement the cloud ecosystem architecture.
Created, implemented, and still evolving a build pipeline ecosystem where:
Created, implemented, and still evolving a repeatable database solution using automated deployments and provisioning, as well as static asset monitoring and scanning solutions for antivirus, malware, etc., detection in S3 buckets in the different environments.
Collaborating with identified vendors to assess information security aspects of their AWS solutions with respect to information exchanges and flows, ingress and egress needs, internal and external resource access requirements, and data protection requirements.
Trility builds a golden triangle of truth for version control, change management, and continuous delivery pipelines to ensure predictable, repeatable, and auditable results. Long-term, this client's teams have increased operational performance and reduced time to value by leveraging the power of CloudFormation’s reusable templates:
It was determined an ephemeral solution was desirable as the client did not want to patch EC2 instances due to the time and was not optimal for scaling. Trility provided recommendations to evolve the existing framework to Lambda and NodeJS in a serverless environment, as it was determined early the client would save 12 hours/month on new images and 24 hours/month for new deployments.
The client made the decision to no longer use AWS API Gateway and instead use Apigee as the API endpoint for service access and reverse proxy. As this application evolved, so did the framework in adjusting and scaling for even larger data sets.
Trility helps rethink your entire business strategy in the cloud. Learn how you can accelerate your next AWS initiative with us.