When using quickstart.sh or startup.sh using default AWS region, the scripts fail when more than one properly line is present in ~/.aws/config - for example, I set my output format to 'table', which added a new config like to 'config'. The sed command "eval $(grep -v '^[' ~/.aws/config | sed 's/^(region)\s\?=\s\?/export AWS_DEFAULT_REGION=/')" does not properly filter for only the line beginning with region, but rather returns all lines in the file. Script fails with the following error "./quickstart.sh: line 84: export: `=': not a valid identifier".
Unfortunately, simply hardcoding the region with '-r' does not prevent this error, as the config files appears to be parsed regardless of the input value.
Removing the format config line from the files resolves this issue.
When using quickstart.sh or startup.sh using default AWS region, the scripts fail when more than one properly line is present in ~/.aws/config - for example, I set my output format to 'table', which added a new config like to 'config'. The sed command "eval $(grep -v '^[' ~/.aws/config | sed 's/^(region)\s\?=\s\?/export AWS_DEFAULT_REGION=/')" does not properly filter for only the line beginning with region, but rather returns all lines in the file. Script fails with the following error "./quickstart.sh: line 84: export: `=': not a valid identifier".
Unfortunately, simply hardcoding the region with '-r' does not prevent this error, as the config files appears to be parsed regardless of the input value.
Removing the format config line from the files resolves this issue.