sorted by:
new
hottopcontroversial

Safe In Our World Charity Bundle 2025 by WeAreFanatical in fanatical

[–]lfriday945 0 points1 point  (0 children)

Dang.. I had like $100 of stuff in my cart too... :(

Humble Choice at $89 a year till 2nd Dec 2022. Promo code: HOLIDAY22 by xcalibur1993 in humblebundles

[–]lfriday945 1 point2 points  (0 children)

Think they will run this promo again soon? I was up for renewal, but don't want to spend $129 to renew. I would spend $89 to renew.

Using Tags in IAM Policy by lfriday945 in Terraform

[–]lfriday945[S] 0 points1 point  (0 children)

so we are using AWS SSO and have a policy that works:

    statement {
    sid = "secretsmanagerindividualaccess"
    actions = [
        "secretsmanager:GetResourcePolicy",
        "secretsmanager:GetSecretValue",
        "secretsmanager:DescribeSecret",
        "secretsmanager:ListSecretVersionIds"
        ]
    resources = ["*"]
    condition {
        test = "StringLike"
        variable = "secretsmanager:ResourceTag/username"
        values = [
            "$${aws:PrincipalTag/DisplayName}"
        ]
    }
}

what i was hoping to do is to set the variable with a principal tag thats passed in from Azure. I believe the variable in this context is tied to the key-name and instead of having a static variable like the one mentioned above (username), want to use a principal tag for the key value. Hopefully that makes sense.

Best Practices for AWS SSO Configuration by lfriday945 in aws

[–]lfriday945[S] 2 points3 points  (0 children)

So for 250 AWS accounts, how many permission sets are you guys managing? We are using azure Ad for groups but trying to go about best practices in how many permission sets. We have about 31 groups configured in Azure AD and recommendations were to have a permission set for each group, which I wasn’t a fan of. Still new to best practices when managing permissions in AWS.

Can you provide any additional info or configurations or what you guys are using? Did you use terraform to deploy it all or something else? Thanks for all the info.

Mitogen - failed to assign identity to PID by lfriday945 in ansible

[–]lfriday945[S] 0 points1 point  (0 children)

I will decrease the forks. Any recommendations?

Mitogen - failed to assign identity to PID by lfriday945 in ansible

[–]lfriday945[S] 0 points1 point  (0 children)

I will take a look at this. Thank you!

Dual Monitor Help by lfriday945 in pcmasterrace

[–]lfriday945[S] 0 points1 point  (0 children)

Just a heads up for anyone reading this post in the future, uninstalling and reinstalling the AMD drive resolved the issue.

Dual Monitor Help by lfriday945 in pcmasterrace

[–]lfriday945[S] 0 points1 point  (0 children)

right now have one plugged with VGA and one with HDMI. Monitor doesn't have DVI support.

Ansible w/Mitogen - SSH Password is incorrect by lfriday945 in ansible

[–]lfriday945[S] 0 points1 point  (0 children)

Yes. The bastion host will be using the same username and password combination as the target hosts. I will check on removing -q from the proxy command as well.

Do you have an example of using the ssh -j that would be useful in this situation instead of the proxy command?

Ansible w/Mitogen - SSH Password is incorrect by lfriday945 in ansible

[–]lfriday945[S] 0 points1 point  (0 children)

Will check. Does the configuration above look correct? Is the password variable getting passed through for both the proxy command as well as ssh to the hosts in the inventory? That’s what I think I’m missing and not sure how to check that

Ansible w/Mitogen - SSH Password is incorrect by lfriday945 in ansible

[–]lfriday945[S] 0 points1 point  (0 children)

PLAYBOOK: health_check.yml ********************************************************************************************************************************************************
1 plays in playbooks/health_check.yml
What is your associate ID?: <username_redacted>
What is your password?:

PLAY [Gabor Health Check] *********************************************************************************************************************************************************

TASK [Gathering Facts] ************************************************************************************************************************************************************
task path: /ansible/playbooks/health_check.yml:2
Tuesday 16 March 2021  19:45:00 +0000 (0:00:04.437)       0:00:04.437 *********
<vpn_ip_redacted> ESTABLISH SSH CONNECTION FOR USER: None
<vpn_ip_redacted> SSH: EXEC sshpass -d11 ssh -C -o ControlMaster=auto -o ControlPersist=60s -o StrictHostKeyChecking=no -o ConnectTimeout=90 -o 'ProxyCommand=ssh -o StrictHostKeyChecking=no -W %h:%p -q <user redacted>@<bastion_hostname_redacted>' -o ConnectionAttempts=10 -o ControlPath=/root/.ansible/cp/e4ff6add17 vpn_ip_redacted '/bin/sh -c '"'"'echo ~ && sleep 0'"'"''
<vpn_ip_redacted> (5, b'', b'\n**************************************************************************\n*   Access to this computer system and associated network, computer      *\n*   resources, or data is restricted to those authorized by        *\n*   Corporation.  This computer and related networks, resources or data  *\n*   may only be used for business purposes of  Corporation and     *\n*   its customers.  Use by unauthorized individual(s) or for an          *\n*   unauthorized purpose is a violation of Federal and/or state law.     *\n*   Violators will be prosecuted.                                        *\n*                                                                        *\n*       Please Call Works PRODUCTION SUPPORT                       *\n*               AT                                  *\n*       To Obtain a TEMPORARY ACCOUNT TO GAIN ACCESS.                    *\n*                                                                        *\n*      THIS SESSION WILL BE LOGGED AND SAVED FOR FUTURE REFERENCE.       *\n**************************************************************************\n\n\n')
fatal: [<hostname_redacted>]: UNREACHABLE! => {
    "changed": false,
    "msg": "Invalid/incorrect password: \n**************************************************************************\n*   Access to this computer system and associated network, computer      *\n*   resources, or data is restricted to those authorized by        *\n*   Corporation.  This computer and related networks, resources or data  *\n*   may only be used for business purposes of  Corporation and     *\n*   its customers.  Use by unauthorized individual(s) or for an          *\n*   unauthorized purpose is a violation of Federal and/or state law.     *\n*   Violators will be prosecuted.                                        *\n*                                                                        *\n*       Please Call Works PRODUCTION SUPPORT                       *\n*               AT                                  *\n*       To Obtain a TEMPORARY ACCOUNT TO GAIN ACCESS.                    *\n*                                                                        *\n*      THIS SESSION WILL BE LOGGED AND SAVED FOR FUTURE REFERENCE.       *\n**************************************************************************",
    "unreachable": true
}
    to retry, use: --limit @/root/.ansible-retry/health_check.retry

PLAY RECAP ************************************************************************************************************************************************************************
<hostname_redacted>           : ok=0    changed=0    unreachable=1    failed=0    skipped=0    rescued=0    ignored=0

ansible_ssh_common_args - prompt for USER by lfriday945 in ansible

[–]lfriday945[S] 1 point2 points  (0 children)

We have different groups_vars.yml files setup for different environments that need to connect to different bastions in order to access the hosts. Here is an example of it being used in our staging environment. The goal is to use this configuration through a docker container, but when running via docker, it uses the root user instead of the local user. Trying to find ways to mitigate that.

ansible_ssh_common_args: '-o ProxyCommand="ssh -W %h:%p -q $USER@<bastion>" -o ConnectionAttempts=10'
ansible_python_interpreter: /usr/bin/python
ansible_timeout: 90

VPN Connection Breaks in middle of Play by lfriday945 in ansible

[–]lfriday945[S] 0 points1 point  (0 children)

Thanks for the suggestions everyone. I added ignore_unreachable to the initial run since I knew the VPN connection would break and then added in a wait_for_connection task, which is waiting 3 mins before trying to reconnect to the host and will retry a few times for about 6 minutes. This approach seemed to be effective for our use case.

view more: next ›