You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When an AWS region isn't specified, the behaviour is correct but the error message is unclear;
$ PARAMETER_STORE_EXEC_PATH=/foo parameter-store-exec true
2017/12/06 15:47:08 MissingRegion: could not find region configuration
It would be nice if the error made it clear how to configure the region. This might mean linking to AWS SDK documentation, since the logic isn't implemented in parameter-store-exec. Or it might mean suggesting setting AWS_DEFAULT_REGION.
(I don't think there's any strong reason to support non-environment flags like --region; that would complicate the argument processing)
The text was updated successfully, but these errors were encountered:
I have the same problem, I'm trying to execute this within a docker container based on the dotnet core images from microsoft https://hub.docker.com/r/microsoft/dotnet/
I have attached a role to the task definition within AWS ECS, which should allow parameter-store-exec to get the parameters from the parameter store. I have also tried to set up config and credentials in a .aws folder in both the /app and /root folder, but I don't see any difference. I keep getting the error message: MissingRegion: could not find region configuration
You need to set AWS_DEFAULT_REGION and/or AWS_REGION in your environment. (I'm not entirely clear on which one to use when — it's all implemented in https://github.com/aws/aws-sdk-go .
Here's an example from an ECS TaskDefinition CloudFormation that works for me:
When an AWS region isn't specified, the behaviour is correct but the error message is unclear;
It would be nice if the error made it clear how to configure the region. This might mean linking to AWS SDK documentation, since the logic isn't implemented in
parameter-store-exec
. Or it might mean suggesting settingAWS_DEFAULT_REGION
.(I don't think there's any strong reason to support non-environment flags like
--region
; that would complicate the argument processing)The text was updated successfully, but these errors were encountered: