On Windows EC2 build infrastructure, containers cannot reach the AWS metadata endpoint (169.254.169.254) because host networking is not supported, unlike Linux. As a result, built-in steps such as upload to S3 (configured with AWS connector with IRSA) fail when trying to assume IAM roles from within the container. We need an enhancement to allow Windows containers used by the built in steps to natively access the metadata/credentials endpoints or run the builtin steps directly on the VM instead of running inside another container, so that we can securely assume IAM roles.