Elastic block store and hooks missing after scheduled AMI update

0

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

FacetAu
已提問 4 年前檢視次數 173 次
2 個答案
0

are the hookes in your Application version source code?

Chad777
已回答 4 年前
0

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

FacetAu
已回答 4 年前

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南