- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
I would suggest using the concept of Canary Deployment https://catalog.us-east-1.prod.workshops.aws/workshops/de171c43-64b4-45f7-a5fe-a28e62a3bfbe/en-US/introduction (hope you have access here). Where you define a Canary Fleet for deployment testing. The Canary Fleet is used to verify that the application is work as expected before the change is pushed to the deployment of the Main Fleet. I hope it helps.
Thanks for that link. It appears to be for GG V1 but the concept still applies for V2. For now I've settled for a similar approach where I use IoT Thing groups to group the canary fleet. The pipeline will deploy to a test-fleet which just contains smoke-test devices . Then the deployment can be applied to the canary fleet group and subsequently to the group containing the rest of the fleet.
The above will allow me to limit the max devices the deployment goes to, and only continue to the rest of the fleet if smoke tests and monitoring are good. Maintaining the fleets will be quite straight forward too and allows for future automation.
I see the benefit for a pipeline for each group but this can be added later when this becomes more important.
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 3 Jahren
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 10 Monaten
If the answer helped, do you mind accepting the answer? Thank you!