Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🐛 Fix username bug for dev-env-tunnel #50

Merged
merged 1 commit into from
Sep 19, 2024

Conversation

devbyaccident
Copy link
Member

@devbyaccident devbyaccident commented Sep 18, 2024

Currently, when running in the chopd3bPrd account, the ssm-user is being used to login to the bastion instances after initial lookup, no matter who is opening the tunnel.

Running in AWS account: 684194535433
Opening Connection
getting info
Found instance i-0745968dfe012e78c. Connecting
ec2-ssh
INFO: Resolved instance name 'i-0745968dfe012e78c' to 'i-0745968dfe012e78c'
INFO: Using SSH key from SSH Agent, should be as good as any.
The authenticity of host 'i-0745968dfe012e78c (<no hostip for proxy command>)' can't be established.
ED25519 key fingerprint is SHA256:xzfSGQMR45GnYDkrlDCulT8qGuJXjUrjpuOQrr4nULk.
This key is not known by any other names
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added 'i-0745968dfe012e78c' (ED25519) to the list of known hosts.
ssm-user@i-0745968dfe012e78c: Permission denied (publickey,gssapi-keyex,gssapi-with-mic).

@devbyaccident devbyaccident self-assigned this Sep 18, 2024
@devbyaccident devbyaccident merged commit 1323e58 into main Sep 19, 2024
@devbyaccident devbyaccident deleted the bugfix/cbl/ssm-user-identity branch September 19, 2024 18:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants