Resource drift on deployed components

I've successfully deployed a container to ECS via the AWS toolkit in VS2022. Overtime I need to update some of the running services, e.g. update the load balancer to provide SSL endpoints, targets and redirects, or extend the role the ECS task(s) run under.

What is the best approach for managing this _drift_?

- Is it possible to edit the original configuration and deployment setup within Visual studio (ie on my local machine pre deploy)?
- Should I import the changes into the deployed Cloudformation stack?
- Should I simply ignore the manually made changes (done via the AWS console) and hope the next install doesn't remove them?

Many thanks

Start by reviewing the AWS Toolkit for Visual Studio deployment setup and the deployed ECS CloudFormation stack described in the issue. Compare how load balancer, target, redirect, and task-role changes are represented before and after deployment; done means identifying and documenting a supported drift-management workflow. No source file or test is named.

Written by the indexing model from the issue text.