Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

ec2-instance-connect client does not use session profile credentials

See original GitHub issue

Describe the bug The ec2-instance-connect client uses the default aws profile, not the one specified in the session

Steps to reproduce

b3session = boto3.Session(profile_name='stage')
s3client = b3session.client('s3')
    for bucket in s3client.list_buckets():
        print(bucket.name) //Will list the stage profile

client = b3session.client('ec2-instance-connect', region_name=instance['region'])
client.send_ssh_public_key( //Will use "default profile"
    InstanceId=instance['instanceId'],
    SSHPublicKey=key,
    AvailabilityZone=instance['az'],
    InstanceOSUser=myuser
)

Expected behavior I am expecting ec2-instance-connect client to use the session profile

Issue Analytics

State:
Created 3 years ago
Comments:11 (5 by maintainers)

Top GitHub Comments

1reaction

stilrencommented, Apr 8, 2021

Hello @stobrien89! After some intense troubleshooting I found out that the error was me not specifying the correct profile when I then tried to connect to the instance (using aws ssm). This one is on me. Thanks for the attention.

0reactions

stobrien89commented, Apr 8, 2021

Hi @stilren,

Of course—Glad you were able to get it working. Let us know if anything else comes up!