Currently, obtaining AWS credentials during the run step involves two separate calls: first, to retrieve a JWT token, and second, to use that token in an AWS STS API call to acquire temporary access and secret keys. Due to security concerns surrounding the exposure of the JWT token, we are requesting a feature enhancement to abstract the token issuance process. The goal is to inject AWS credentials directly into the step template, eliminating the need to handle the JWT token explicitly. Additionally, it is essential that the run step remains within the deploy stage to ensure that Harness recognizes the infrastructure initialized during deployment.