This message was deleted.

I think you can try to connect up with people at Ancestry.com. They are a AWS-native shop and seem to have done a good job from my understanding. I don't really know how you give engineers a great developer experience with ECS/Fargate, though. Would be curious what the best tooling is there.

Hi Troy & Gyan, Ancestery is a big Harness shop. They compliment the AWS stack with Harness to orchestrate anything artifact forward while still ensuring - to your point Gyan - developer experience. Here is a case study on the topic https://harness.io/customers/case-studies/governance-and-pipeline-management/ DM me if you want me to connect you @Troy Marshall!

Hi @Troy Marshall We are also (devopsbox.io) implementing our platform on top of AWS services using for example ECS Fargate, CodeBuild, CodePipeline and of course we are focused on developer experience. If you have any specific questions, I will be happy to answer.

We’re in the process of migrating from EKS to ECS, AppRunner and Lambda. Also using some Beanstalk here and there, but not that much anymore. Based on Terraform and some teams use Pulumi. Feel free to reach out if you have questions!

I am very interested in the AWS-native tooling organizations are using. We are using CDK heavily to express our IaC, including our CICD pipelines built around Code*. We are a highly distributed AWS account environment so I am looking at ways to offer standardized CDK constructs as part of our platform and how we would distribute those. AWS Proton is one option we are considering. I am curious, are any teams using AWS Proton as the basis for their platform?