[Bug] G6 instances do not deploy in a Farm Stack in an available region

[david-blg]

Bug Description

When creating a Farm Stack, older accounts that have previously created a stack are unable to deploy G6 instance types due to an issue with the *CodeBuildServiceRole*.
If a stack is deployed with older configurations, the CodeBuildServiceRole is checked to see if it exists. If it does exist, it must always be updated when deploying a stack, as this is the permission required to describe the available instances in the region.

Steps to Reproduce

1. Create a Farm Stack.
2. Use an older account that has deployed a stack previously.
3. Attempt to deploy G6 instance types in an available region.
4. Check the CodeBuild logs to see the specific error related to the CodeBuildServiceRole.

Expected Behavior

The G6 instance types should be deployable in the Farm Stack without issues, and the Service Role should either be created or updated automatically as needed to allow proper interaction with the available instances in the region.

Screenshots

Note: These logs show the behavior when everything is functioning correctly. If the G6 deployment fails, it usually fails around this line.

Desktop OS

No response

Desktop Browser

No response

Desktop Browser Version

No response

Additional Logs

Check the CodeBuild logs for the specific error.

This issue affects older accounts that have previously created a stack. Updating the CodeBuildServiceRole during the deployment process seems to resolve the issue.