This message was deleted.
# awss
sparse-intern-71089
01/23/2024, 12:32 AMThis message was deleted.
l
little-cartoon-10569
01/23/2024, 1:15 AMThe answer depends on the cloud. I'm guessing it's AWS, since you mention CodeBuild?
The account you're running from isn't relevant. You need an AWS provider for the account you are deploying to, and its credentials are acquired in the normal ways you do from the command line.
There are many features to help manage credentials, but the first place to start is the documentation for the AWS provider: https://www.pulumi.com/registry/packages/aws/api-docs/provider/
little-cartoon-10569
01/23/2024, 1:19 AMProviders can be defined to be implicitly available to resources ("default" provider), or you can pass a provider to each resource as you construct it. This is how a single stack can create resources in multiple accounts: have a provider for each account/region combination, and pass the providers around.
m
mysterious-raincoat-41852
01/23/2024, 4:18 PMThank you!
👍 1
l
little-cartoon-10569
01/23/2024, 6:52 PMThere are many places on the Pulumi site and in their GitHub repos with more docs and good examples, but since it's such a wide area with lots of right answers, depending on your goal, use case and preferences, it's a bit risky to point at specific docs without knowing more. Search the Pulumi site, use google, and come back with more questions 🙂
little-cartoon-10569
01/23/2024, 6:53 PMThere's plenty of links from this page, maybe this would be another good place to start? https://leebriggs.co.uk/blog/2022/09/05/authenticating-to-aws-the-right-way
m
mysterious-raincoat-41852
01/23/2024, 9:10 PMPassed to SA and checking they can solve\solved it, thank you again! And sharing the secret of community slack and value! 🙂
👍 1