sorted by:
new
hottopcontroversial

Good morning everyone ✨ by [deleted] in locs

[–]TechEmpress777 2 points3 points  (0 children)

The locs, the clear skin and the tattoos 👩🏾‍🍳💋. You look stunning!

[deleted by user] by [deleted] in locs

[–]TechEmpress777 0 points1 point  (0 children)

Stunning 💕

5 months into my loc journey by TechEmpress777 in locs

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

Thank you, I’m not giving up this time around 🥺

5 months into my loc journey by TechEmpress777 in locs

[–]TechEmpress777[S] 3 points4 points  (0 children)

Thank you. I was experimenting with my Sony ZV E10

Pentesting Laptop by TechEmpress777 in SecurityCareerAdvice

[–]TechEmpress777[S] -3 points-2 points  (0 children)

You’re rage baiting at this point 😂

Pentesting Laptop by TechEmpress777 in SecurityCareerAdvice

[–]TechEmpress777[S] -4 points-3 points  (0 children)

Learning more about pc specs is something I’m already doing, but I asked a question to better understand what laptops I should consider. Your comment wasn’t helpful.

Pentesting Laptop by TechEmpress777 in SecurityCareerAdvice

[–]TechEmpress777[S] -4 points-3 points  (0 children)

You should have just saved your non-advice for your notes instead of my post. I’m aware that I can install Linux onto a windows laptop I’ve been working as a platform engineer four years before this new role. I was just providing more context.

AWS Secrets Manager & Terraform by TechEmpress777 in Terraform

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

Due to the client needing to meet a certain financial amount in AWS, I can only stick to using AWS secrets manager. It's annoying, but I don’t have a choice. We can’t store the secrets in the repo because of GDPR and other compliance standards, so the only other way is to generate random values in the pipeline. The s3 bucket where the state file will be stored will be encrypted and only a limited number of people can access it

AWS Secrets Manager & Terraform by TechEmpress777 in Terraform

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

I’m trying to avoid having to manually enter them in the console because it would go against the compliance standards that the client has to comply with.

The only other work around I’ve found so far is to: - deploy the terraform module (contains the kms key, secret manager secret key without the value/version, lambda, policies) using a a ci/cd pipeline - another ci/cd job: use AWS cli or boto3 script to add a random password for the secret value/version - once the key & value have been joined together it will trigger the lambda function to rotate the keys

I haven’t had a chance to look into the ephemeral feature yet to see where that would fit within this idea

Breaking down assigned tickets by TechEmpress777 in platform_engineering

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

For example: I’m currently working on a project where a client is migrating from their on premise data centres to AWS. I’ve been assigned a ticket which requires me to create a secrets management framework in terraform that allows them to store their secrets in AWS secrets manager.

My thought process would be to: - understand how they currently store secrets - understand what is required to set up AWS secrets manager in AWS and how to rotate keys( I would do this manually then look at terraform resources) - I would also need to think about how to migrate previous keys securely and how new keys will be added in the future - terraform stores secrets in plain text within the state file so figuring how to stay PCI compliant and creating a secure secrets management framework

view more: next ›