Dynamically generated AWS CLI command doesn't run in bash script but it works if manually copy/paste run

It seems like the issue you're experiencing is related to how the AWS CLI command is being constructed and executed within your bash script. Here are a few potential reasons and solutions for your problem:

1. Command Construction: Ensure that your script is correctly constructing the AWS CLI command. The error message suggests that the options are not being recognized, which could mean they're not being passed correctly to the AWS CLI.

2. Quoting: In bash scripts, it's important to properly quote your variables, especially when they contain spaces or special characters. Try enclosing your dynamically generated command in double quotes when executing it.

3. IFS (Internal Field Separator): If you're using ':' as a field separator in your .conf file, make sure you're setting the IFS appropriately in your script when reading the file.

4. Command Execution: Instead of trying to execute the entire command as a string, consider using an array to store the command and its arguments, then use the array to execute the command.

Here's an example of how you might modify your script:

while IFS=':' read -r group_name direction params; do
cmd=(aws ec2 authorize-security-group-ingress --group-id "$group_id" $params --region us-east-2)
"${cmd[@]}"
done < your_config.conf

This approach constructs the command as an array and then executes it, which can help avoid issues with spaces and special characters.

5. Error Handling: Add error checking after each AWS CLI command to catch and display any errors that occur.

6. AWS CLI Version: Ensure you're using a recent version of the AWS CLI that supports all the options you're trying to use.

7. Permissions: Verify that you have the necessary permissions to execute these AWS CLI commands.

If the issue persists, you might want to add some debug output to your script to see exactly what command is being constructed before it's executed. This can help identify any malformed commands.

Remember to always be cautious when dynamically generating and executing commands, especially ones that modify your AWS resources. Ensure your input is properly sanitized and validated.
Sources
Use CreateSecurityGroup with an AWS SDK or CLI - AWS SDK Code Examples
create-security-group — AWS CLI 2.18.3 Command Reference