shall I prevent using default Elastic Bamboo Image on the OS level (ie. executing shutdown from within start scripts), or
shall I simply prevent starting Elastic Agent when given metadata is missing?

We should do this @ the OS level (with appropriate logging) since it's the instance that we need protect.

how do I access that metadata from Java program and OS level (bash script)?

There's a /opt/bamboo-elastic-agent/bin/getCustomData.sh shell script that allows you to write the result of a meta data call to disk, so you can use that directly or use it as inspiration.

Let me describe how I understand that:

Bamboo server passes a 'started-by-bamboo' marker to starting EC2 instance using metadata (as it is shown in class RemoteElasticAgentImpl).

Now the receiving side:

• shall I prevent using default Elastic Bamboo Image on the OS level (ie. executing shutdown from within start scripts), or
• shall I simply prevent starting Elastic Agent when given metadata is missing?

• how do I access that metadata from Java program and OS level (bash script)?

updated from M4 planning

• approach is to check if there is valid user data during instance startup