- Newest
- Most votes
- Most comments
Best approach is to implement Continuous Deployment on Amazon EKS using GitOps approach. Then CodeBuild would be restricted to the Continuous Integration phase (tests, scans, builds and pushes). There are many GitOps controllers out there, but Flux and ArgoCD are the most used.
https://aws.amazon.com/blogs/containers/automating-amazon-eks-with-gitops/
Hi,
I see no issues with the approach you have mentioned. It's convenient to manage a single repository and allow cross account read access to it since you need to build and upload to ECR just once.
Another alternative is to setup cross account replication if you want maintain separation between test and production account. But in this case lifecycle rules and IAM policies are not replicated. You can also upload to each account separately. For me it just comes down to preference
--Syd
Relevant content
- asked 7 days ago
- Accepted Answerasked 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago