When I add amazonec2-iam-instance-profile to an existing config.toml file it has no effect
I updated an existing(working) config.toml file to include amazonec2-iam-instance-profile but when I run the CI job and sub sequentially verify that instance is deployed the defined IAM role is not being attached
Below is the machine options.
At first I thought that the file may not be getting picked up so I changed the instance type to a 2xlarge and that worked. Then I manually added the IAM profile to the running instance thinking that maybe there is something wrong with the role itself. After I successfully added the role and ran the CI job it succeeded.
Is there a conflict in the below config? If not, where else can I get logging to see what is happening when the instance is launched? I did try to ssh into the running instance but my creds are not set up yet.
Thanks ahead of time!
MachineOptions = [ "amazonec2-ami=ami-<redacted>", "amazonec2-subnet-id=subnet-<redacted>", "amazonec2-vpc-id=vpc-<redacted>", "amazonec2-security-group-id=sg-<redacted>", "amazonec2-tags=<redacted>", "amazonec2-ssh-user=ubuntu", "amazonec2-region=us-east-2", "amazonec2-instance-type=m5a.xlarge", "amazonec2-iam-instance-profile=gitlab-runner", "amazonec2-root-size=30", "amazonec2-zone=a", "amazonec2-use-ebs-optimized-instance=true", "amazonec2-keypair-name=<redacted>", "amazonec2-ssh-keypath=<redacted>", "amazonec2-device-name=/dev/sda1", "amazonec2-private-address-only=true", "amazonec2-userdata=/etc/gitlab-runner/user-data.sh" ]