Elastic block store and hooks missing after scheduled AMI update

Question

Hi,  
  
After creating a new Elastic beanstalk env, we've added a Volume to this instance and added hooks to update some perms post an appdeploy in "/opt/elasticbeanstalk/hooks/appdeploy/post".    
  
Now each time after an update to the AMI, our volumes and hooks go missing.  The platform is "PHP 7.3 running on 64bit Amazon Linux/2.9.4".  
  
Any known issues with this?  Anything extra details I can provide to help debug this?  
  
Thanks,  
John

Answer

are the hookes in your Application version source code?

Answer

Not in source control, they are on the instance under "/opt/elasticbeanstalk/hooks/"  
  
EDIT1:  I see these are discontinued, now under ".platform/hooks" in the repo.  
  
Still unsure as to why our volume goes missing.  
  
EDIT2:  
I assume we now add a volume in a .ebextensions conf file? e.g.:  
commands:  
  01mkfs:  
    command: "mkfs -t ext3 /dev/sdh"  
  02mkdir:  
    command: "mkdir /media/volume1"  
  04mount:  
    command: "mount /dev/sdh /media/volume1"  
  
option_settings:  
  - namespace: aws:autoscaling:launchconfiguration  
    option_name: BlockDeviceMappings  
    value: /dev/sdh=:8  
  
Edited by: FacetAu on Apr 16, 2020 8:40 PM  
  
Edited by: FacetAu on Apr 16, 2020 9:23 PM

Elastic block store and hooks missing after scheduled AMI update

Relevanter Inhalt