-
Notifications
You must be signed in to change notification settings - Fork 25
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
Cannot get gMSA krb ticket #137
Comments
Since you are using ECS, you can set DHCP option set in your VPC. This works in the previous release. Please try and let us know. |
Not having much luck on the compile
I will continue on with DHCP option set. Thanks |
@vaujo6y Feel free to email me at samiull at amazon dot com, I can setup a chime meeting to screen share with you, |
Changes and RPM are at https://github.com/aws/credentials-fetcher/tree/fixes_for_DNS_and_distinguishedName/rpm |
Any ETA on when this will be released into the Fargate baselines? |
We are planning to release in the first quarter of 2025 |
I have setup gMSA domained-joined and domainless without an issue on Windows. I started to repeat the same process for a Linux instance in the same way, but everything I do I can't get passed the following ecs task error
Rpc error: code = Internal desc = ERROR: Cannot get gMSA krb ticket
The logging looks like:
cat credentials-fetcher.log
cat credentials-fetcher.log
cat: credentials_fetcher.sock: No such device or address
journalctl -u credentials-fetcher
host:
amazon/al2023-ami-ecs-hvm-2023.0.20240905-kernel-6.1-x86_64
If you could provide me with a better way to troubleshoot this issue, it would be much appreciated.
Thanks
The text was updated successfully, but these errors were encountered: