8/9/2023 0 Comments Spring venture group news![]() Using AWS CloudFormation and AWS Service CatalogĪfter Logicworks designed the architecture for Spring Venture Group, we built an AWS CloudFormation template that launched their hub-spoke VPC model and Amazon ECS clusters.Ī key aspect of our approach is to selectively create nested stacks for larger recurring concepts. This is a crucial step in any environment, allowing for easy detection of unusual or unexpected activity in other regions, and forensics that aid in resolution of complex security issues. This provides Spring Venture Group with a separation of concerns, network isolation, and a basis for comparison of security groups.Īdditionally, all Logicworks customers are subject to a background process that ensures AWS CloudTrail and AWS Config recording are properly enabled in all regions. Rather than replicating standard features in each VPC, Logicworks created a central hub VPC that is peered to spoke VPCs. ![]() To maintain HIPAA standards, several key security features (intrusion detection, logging, bastion hosts, and centralized authentication) should be present in each Virtual Private Cloud (VPC). On an ongoing basis, Spring Venture Group would be responsible for building and deploying container images, while Logicworks would be responsible for maintaining their AWS account and the Amazon ECS clusters themselves. Spring Venture Group ultimately chose Amazon ECS over Kubernetes due to the overhead of managing their own Kubernetes master nodes and the simplicity of the Amazon ECS platform. Amazon ECS has deep integration with other AWS services like AWS CodeBuild, AWS CodeDeploy, and Amazon Elastic Container Registry (Amazon ECR), making it the most robust and integrated container orchestration platform for AWS.Īlthough Spring Venture Group’s environment was built prior to the release of Amazon Elastic Container Service for Kubernetes (Amazon EKS), many of the environment’s strengths are also part of the Amazon EKS service. We discussed Kubernetes, Docker Swarm, and the AWS orchestration platform, Amazon Elastic Container Service (Amazon ECS). One of the key parts of the architecting process was choosing the right container orchestration platform. They faced severe availability issues running containers on-premises. Spring Venture Group’s developers were comfortable building and deploying containers in their on-premises environment, but were eager to get greater agility and flexibility on AWS. Spring Venture Group reached out to our team at Logicworks, an AWS Partner Network (APN) Premier Consulting Partner and Managed Service Provider with the AWS Healthcare Competency, to architect and manage their AWS deployment. Architecting a Containerized HIPAA-Compliant AWS Environment Manual approaches can result in “snowflake” environments, which create new organizational risks such as improperly configured security controls. However, they did not want developers to manually build each new AWS environment in the AWS Management Console. Spring Venture Group saw the power of providing developers with self-service access to AWS resources. Spring Venture Group is a group of insurance brokerages that’s expecting double or triple digit growth in the next three years, in large part due to their innovative approach to providing data analytics and other software services to sellers and customers.Īs a health insurance sales organization, Spring Venture Group needs to maintain HIPAA compliance, so the potential impact of even a single misconfigured AWS resource is high. On AWS, developers can test and deploy in minutes or hours, resulting in more frequent product releases–and better products. ![]() Long gone are the days when developers had to wait two to three months for IT to provision new servers. When developers have the power to rapidly launch new Amazon Web Services (AWS) resources, organizations can reduce time-to-market for new products. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |