AWS CLI network error while invoking a lambda after 2 or 3 min

[rbasina]

Describe the issue

while running below AWS CLI command and its invoking lambda to trigger EMR step. AWS cli getting network error after 3 min and its triggering lambda again. due to this we are not getting proper logs/response from aws cli.

aws lambda invoke --debug --cli-read-timeout 0 --cli-connect-timeout 0 --function-name autosys-job-execution-lambda --region us-east-1 --cli-binary-format raw-in-base64-out --payload "{"env":"UAT","profile":"hrcore","jobType":"conformed","process":"scalaclassprocess","mode": "ONETIME"}"

error message:

Network Error

A communication error occurred: ""

Additional Information/Context

No response

CLI version used

aws-cli2.1.3.0

Environment details (OS name and version, etc.)

Unix

[Charles-dot-code]

Verify that you have the latest version of the AWS CLI installed. The AWS CLI is updated frequently. You can’t access new released features when running an older CLI version.
Use the --debug option. [Enable and review the AWS CLI command history logs.
Confirm that your AWS CLI is configured.

[Charles-dot-code]

But from the error code received it looks like it's a Network error message so you can try this Tips

Check your network connectivity and ensure that you have an active internet connection.
Ensure that your AWS CLI credentials are correct and that you have permission to invoke the Lambda function.
Ensure that you have set the correct region for your Lambda function.

[rbasina]

Lambda is invoking the glue/EMR job and in the backend Lambda and gle/emr job completing successfully but the CLI is terminating with network error after 3 min

[rbasina]

we are in US-EAST-1 region

[Charles-dot-code]

why do you ask?

[tim-finnigan]

Hi @rbasina thanks for reaching out. We recommend updating to a more recent version of the CLI. The latest version is 2.13.3 per the CHANGELOG. If you're still seeing the issue please share your debug logs (with sensitive info redacted) by adding --debug to the command for us to investigate further.

[Charles-dot-code]

we are in US-EAST-1 region

Actually, am from Nigeria.

[github-actions]

Greetings! It looks like this issue hasn’t been active in longer than five days. We encourage you to check if this is still an issue in the latest release. In the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment or upvote with a reaction on the initial post to prevent automatic closure. If the issue is already closed, please feel free to open a new one.