What are the solution stack requirements? How is the documentation about it?.What are my "cloud" options? How hard is it to deploy and how cheap does it get?.How many companies have expertise and proficiency in hosting this CMS?.How much does it typically cost per month per instance for professional on-site hosting.What are the minimum hardware requirements for each CMS?.echo "$(curl -s ).com:/ /var/www/html/efs-mount-point nfs4 nfsvers=4. chown ec2-user:ec2-user /var/www/html/efs-mount-point/ mkdir -p /var/www/html/efs-mount-point/ So basic Drupal core files on the EC2 AMI image i created, plus sites folder on EFS, with auto enabling that on each loaded instance by adding the below script: #cloud-config Luckily Amazon have another service called Elastic File System used for such cases! I now moved the sites folder of drupal to EFS. In that case those files for example images will be saved on the one particular EC2 and during a scale down the instance could go down, or may not be available in the newly booted up instance. Later realized that we might have user generated content/content added by admin via the Drupal CMS backened. This was taken considering we update the files. Youtube said in Auto-scale Drupal site: AWS or Azure: When CPU goes down for around 2 minutes, it will terminate 1 instance, to keep the minimal back to 1. Set threshold alarms: start with 1 server, when CPU reaches 80% and stays for a minute, boot up another instance. (It starts from our internal gitlab server, once all files are committed, we will zip that solution and a gitlab runner will initiate a docker instance which then uses aws cli to push this zip file to S3, code deploy picks it up from there and deploy to the selected auto scale group) Code deploy takes care of deploying the code to all new servers as it boot us on the autoscale group. When you jump all the hoops and get past the issues, the things work relatively well.ĮC2- Compute instances: Used Amazon AMI, installed Apache, PHP and checked out drupal core files, converted to an image.Īutoscaling Group: Launch config & Auto Scaling Group, using the custom image created from EC2ĮLB: Frontend load balancer for web serversĬode Deploy: To deploy the update code files to the web servers. On the plus side, their ARM templates are richer and nicer to use than CloudFormation, however the lack of documentation for them kills all the advantages. Their services labelled Beta are really more like Alpha quality. you now have to have another VMSS just for load balancing/service discovery. You have a VMSS (=Auto Scaling Group) and have a Load Balancer in front of it, your microservice connections fail if the load balancer routes the connection back to the same VM. You have to store your osDisk image in the same storage account as your machine you are running (so you have to pay for your image the full SSD monthly price) You can have SSD's in 128/512/1024GB sizes and you pay for them in full, Spinning disks are billed per actual usage. Default Centos images are 30GB osDisk and you can't resize them, you have to create your own images if you do want to. But the lack of documentation compounds confusion.Īzure has a lot of very weird limitations that don't make any sense: Would be great if you can give some more insights which makes you end up in the conclusion that Azure is not a great choice.ĪWS documentation is excellent, Azure docs are weird and inconsistent and for some bits nonexistent.Īzure API's are inconsistent and weird, but once you figure out they work relatively well. Azure might be expensive (I need to take some time to actually compare the pricing) but i am interested to know why you consider Azure as unreliable.
0 Comments
Leave a Reply. |