https://pulumi.com
Join Slack
This message was deleted.
s

Slackbot

about 4 years ago
This message was deleted.
s
t
+4
  • 6
  • 8
  • 214
This message was deleted.
s

Slackbot

about 3 years ago
This message was deleted.
s
r
+3
  • 5
  • 7
  • 212
This message was deleted.
s

Slackbot

over 4 years ago
This message was deleted.
s
p
+3
  • 5
  • 12
  • 212
This message was deleted.
s

Slackbot

over 6 years ago
This message was deleted.
s
l
s
  • 3
  • 8
  • 212
Is there a way to update an IAM role's `assume_role_policy`? Basically instead of defining `assume_...
z

Zhuming Pan

over 1 year ago
Is there a way to update an IAM role's
assume_role_policy
? Basically instead of defining
assume_role_policy
at the creation of the role, we want to take an existing role then add additional statements in its
assume_role_policy
z
k
  • 2
  • 4
  • 211
This message was deleted.
s

Slackbot

about 4 years ago
This message was deleted.
s
n
j
  • 3
  • 33
  • 211
good afternoon! i've got a weird issue that i hope might pique somebody's curiosity. i have a projec...
f

Fotios Lindiakos

about 1 year ago
good afternoon! i've got a weird issue that i hope might pique somebody's curiosity. i have a project (all AWS provider and configured to use OIDC) that's working just fine in
us-east-1
. i added a second stack to use
aws:region: eu-central-2
and then the preview fails with
Diagnostics:
  pulumi:pulumi:Stack (networking-xxx-stg.eu-central-2):
    error: awsx:ec2:Vpc resource 'xxx' has a problem: grpc: the client connection is closing
 
  pulumi:providers:aws (default_6_47_0):
    error: pulumi:providers:aws resource 'default_6_47_0' has a problem: Invalid credentials configured.
so here's the fun part. i set
AWS_REGION=eu-central-2
for that stack and it worked. looking into the cloudtrail logs, it looks the one that failed was issued an access key from
us-east-1
. the one that succeeded was issued from
eu-central-2
. this leads me to believe that the ENV var is influencing whatever you run initially to do the
AssumeRoleWithWebIdentity
(from the deployment logs, it looks like its calling
pulumi-deploy-executor oidc ...
) considering this isn't documented anywhere when talking about configuring the regions, i'm assuming this is not expected?
f
  • 1
  • 2
  • 209
This message was deleted.
s

Slackbot

about 4 years ago
This message was deleted.
s
j
a
  • 3
  • 37
  • 209
This message was deleted.
s

Slackbot

almost 5 years ago
This message was deleted.
s
p
+2
  • 4
  • 13
  • 208
This message was deleted.
s

Slackbot

almost 5 years ago
This message was deleted.
s
d
+2
  • 4
  • 18
  • 208
Previous202122Next

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Powered by