cool-glass-6301402/21/2022, 12:28 PM
even though I have several profiles, and for the stack I have the proper AWS profile configured in the yaml file. And it seems like it can build and push the docker image but it cannot edit the Fargate task definition or something? I am not savvy with either AWS or Pulumi and this is something I've inherited, but I can't wrap my head around this. I also followed the linked and repeated the setup and yet nothing. EDIT: I can't seem to restore the state of whatever it is I've managed to bork up at all? I haven't changed any credentials or keys to begin with so this feels like such a weird curve ball? 🤔 Any ideas?
aws:ecs:Service (backend): error: unable to discover AWS AccessKeyID and/or SecretAccessKey - see <https://pulumi.io/install/aws.html> for details on configuration
little-cartoon-1056902/21/2022, 8:09 PM
or `AWS_ACCESS_KEY_ID`/`AWS_SECRET_ACCESS_KEY` in your environment to configure the backend.
cool-glass-6301402/22/2022, 12:48 PM
didn't work anymore so I eventually set
instead. But this will make managing envs more problematic
now, or something? Is this related to the problem?
little-cartoon-1056902/22/2022, 8:20 PM
cool-glass-6301402/24/2022, 9:11 AM
, so the GitHub Action also works without the env variables. So I'm confused as to what you mean with "aws:profile won't ever work with backends". 🤔 If I've declared something weird in my rewrite of the stack that causes this I'd like to identify it. Other than that the config should be the same regarding AWS itself.
little-cartoon-1056902/24/2022, 9:08 PM
refers to our service called
in pulumi, and part of what I'm up to right now is implementing a naming convention for all Pulumi resources so as to not be able to confuse them between envs, if one were to accidentally run this with incorrect AWS credentials.
used to be the name for our ECS Cluster, Fargate Service, Docker Image and much more. Now it's going to follow
files. Or using
, which is a different CLI altogether, or the env variables as mentioned earlier.
little-cartoon-1056902/27/2022, 9:15 PM
was set correctly, but they were working when
was set correctly. It turns out that
isn't used by default when you're creating your own AWS provider. Are you doing that? If you are, then can you try setting
profile: new pulumi.Config("aws").require("profile")
cool-glass-6301403/07/2022, 2:04 PM