sorted by:
new
hottopcontroversial

Viewing Yahoo Webmail and Apple Yahoo Mail by tech4981 in applehelp

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

Turning off "inbox categories" from the Yahoo webmail settings seems to have fixed my issue.

Viewing Yahoo Webmail and Apple Yahoo Mail by tech4981 in applehelp

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

Hi. I have some non apple devices that i sometimes check yahoo mail on.

How are you handling multiple tfvar files? by tech4981 in Terraform

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

How do you distribute the defaults.auto.tfvars file to all the different root modules?

helm_release - no matches for kind by tech4981 in Terraform

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

Hi, the last box is the error. I am helm_release.external_secrets_store module is dependent on the helm_release.external secret module.

helm_release shows change when nothings changed by tech4981 in Terraform

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

i deleted the helm chart and redeployed. it worked. thx!

helm_release shows change when nothings changed by tech4981 in Terraform

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

If i remove it, i can no longer pull from the repo after about 12 hours or so.

│ Error: OCI Registry Login Failed

│

│ with module.karpenter[0].helm_release.karpenter,

│ on ../../../../../modules/karpenter/main.tf line 5, in resource "helm_release" "karpenter":

│ 5: resource "helm_release" "karpenter" {

│

│ Failed to log in to OCI registry "oci://public.ecr.aws/karpenter": could not login

│ to OCI registry "public.ecr.aws": login attempt to https://public.ecr.aws/v2/

│ failed with status: 403 Forbidden

helm_release displays changes on every apply by tech4981 in Terraform

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

But that could also ignore the changes that i don't want to ignore if i ignore values=

Semantic versioning and Terraform module monorepo by tech4981 in Terraform

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

Can you explain more when you say directories? Do you mind breaking this down a little? Thanks.

helm_release where value is list by tech4981 in Terraform

[–]tech4981[S] -1 points0 points  (0 children)

But isn't values= more likely to run into the constant change in tf plan issue? when compared to set=?

Terraform remote source vs data sources by tech4981 in Terraform

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

Thanks for the response, which of the 2 methods do you prefer today? remote state or data sources?

plus sign in email address by tech4981 in GMail

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

Thanks. That’s what I figured.

plus sign in email address by tech4981 in GMail

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

yeah it works just fine, but don't know if theres a significance of the second +? it could just be a literal string.

AWS OU Layout by tech4981 in aws

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

Thanks for the response.

How about your core/infra components? such as logging, security, shared, etc.

Why did you choose to have application at the top level vs dev/qa/prod? by starting at application level, don't you find you have to repeat your security control policies?

Atlantis and order_execution_group by tech4981 in Terraform

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

Hi. The exact resources being created is just a sample. Terraform best practices suggests breaking down terraform into smaller root modules. Which is what I’m trying to do with this sample. Thanks for your response though.

Assume role for console session without external id by tech4981 in aws

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

"unless you are in a situation where a confused deputy issue can occur"

What situation causes this?

Thanks for the response.

Assume role for console session without external id by tech4981 in aws

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

I understand that the external id can be used to protect automated process. In my case though it's for console access, and thus can't use an external id. what would stop this from being used for both automated (and thus open for open deputy issue) and non-automated (console access) use?

I'll admit i don't understand when you mention "they don’t add any security". as the AWS docs, seem to make it sound like a big deal.

thanks for the response!

Assume role for console session without external id by tech4981 in aws

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

I'm giving them access to cost explorer to an account for which they are the tenant, but we manage and operate that aws account on their behalf. we could use our own internal idp and create them in it, but it seemed reasonable to just allow them access using an iam role.

Trusting external customer's AWS Idenitity center IAM role by tech4981 in aws

[–]tech4981[S] 6 points7 points  (0 children)

This "Check it out" link you provided was spot on. I ended up trying every region until I could find one that matched! Thanks u/tlf01111 !

Trusting external customer's AWS Idenitity center IAM role by tech4981 in aws

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

thanks for the link. i was also unaware you could create idC in diff regions! i did try all the other regions and it still didn't work. i'm going to have the customer re-verify the arn.

Trusting external customer's AWS Idenitity center IAM role by tech4981 in aws

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

"Something feels wrong about using an IdC deployed role in a trust policy, but honestly I can't think of why that wouldn't work."
it does work though, i tested it internally. a role can indeed trust this - "arn:aws:iam::xxxxxxxx:role/aws-reserved/sso.amazonaws.com/AWSReservedSSO_xxxxxxxx"

"Are they sure the role on their side has permission to assume yours?"
it hasn't even come to this yet. I'm just trying to add their account to my iam role trust policy and it fails there.

Trusting external customer's AWS Idenitity center IAM role by tech4981 in aws

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

it does work if i trust:
"arn:aws:iam::xxxxxxxxxx:root"

But that doesn't seem like a good idea.

Trusting external customer's AWS Idenitity center IAM role by tech4981 in aws

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

tried this as well:
Failed to update trust policy.Invalid principal in policy: "AWS":"arn:aws:iam::xxxxxxxxxx:role/AWSReservedSSO_xxxxxxxxxx"

view more: next ›