Summary

When an elastic instance startup-

1. it first download agent binaries from Atlassian S3 bucket.
2. executes the agent jar execution

In random cases, Elastic IP may not be assigned at the time the elastic agent startup script executes, this will cause a timeout trying to connect to Atlassian S3.

Suggestion 

The script should run multiple retries before timing out, possible log the retries

Workaround

1. Modify the startup script to perform a test connection to S3 before running the script
2. sleep 180 before execution