I asked this on the Orchard community forums and got crickets...
How does one deploy Orchard CMS into a proper cloud style deployment (ephemeral/stateless servers) on AWS using Elastic Beanstalk?
There is a standard and an Azure solution file for Visual Studio. I'm not a developer so I'm kinda lost in VS-2015. I would have thought I could deploy using the normal (not azure specific) solution and utilized S3 for storage and and RDS instance for database. However, I just keep running into walls. I would like to be able to utilize all the VPC infrustructure and investment we have in AWS for this if possible.
Related
I have a Spring Boot project that is running on an EC2 instance via Elastic Beanstalk. This project was created by AWS CodeStar and they also provided an out-of-the-box project template. You can see the template here: https://github.com/JanHorcicka/AWS-Codestar-Spring-Webapp-EBS-Template
The problem is that this project is automatically deployed to an EC2 instance running Amazon Linux 1. To project template is built to work on AL1. Unfortunately, some tools I want to install (Certbot) require Amazon Linux 2. There are ways to switch from AL1 to AL2. For example here: Create Amazon Linux 2 instance via CodeStar
The problem is that after I switch to AL2, the provided project template doesn't work.
I know there are some differences for Elastic Beanstalk for different version of AL. For example I read somewhere, that the AL2 is not using .ebextensions folder anymore. But I cannot find the full list of changes.
How do I have to modify the template to make it work also on AL2 instance?
I'm trying to migrate GCP instances to AWS, I have been searching for the solution but didn't find any references. Could you please help me with this.
The OS are customized differently in different cloud, so you can only migrate files and applications, by using Cloud Storage or AWS S3 as the bridge to migration files
While for the applications, you're recommended to build from scratch, but it highly depends on what exactly you want to migrate
I have to deploy my .NET web application in AWS. I am very new to AWS and I have very little time to complete this task.
Please help me by providing me some steps to be followed or any tutorials.
It is really easy. This can be done via AWS Elastic BeanStalk.
It very very simple and can be done in minutes.
You can follow the steps here:
http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/create_deploy_NET.quickstart.html
This should be helpful too: https://www.youtube.com/watch?v=z-N0z5K_WFI&t=606s
AWS Elastic BeanStalk is free but the EC2 instances running will incur charge. When setting up the application in Elastic BeanStalk console in AWS, choose single instance rather than load balanced/autoscaled etc. if it is not a production application.
Let me know if you get stuck anywhere.
I have looked in the Magento & AWS Documentation but that didn't really help.
I've installed Magento on Elastic Beanstalk with 1 instance, I proceeded to snapshot the volume and make an AMI and changed the AMI setting in Elastic Beanstalk. Then spun up 2 more instances in the other availability zones. They went back to the Magento installation pages.
How do I fix this? I thought the AMI made from the snapshot would of captured the DB and other files created on installation. Meaning they'd just connect the DB and run.
Cheers to anyone who helps!
You probably don't want your database installed on your EC2 inside the elastic beanstalk. Since elastic beanstalk just removes the instance when there is an error on it and spawns a new one. You then end up loosing data. Besides that you need 1 single database server, not a database server on each of the EC2 instances inside the elastic beanstalk.
You want a separate database server, I personally always use Amazon RDS for this since this is made for this purpose.
When you are getting the install page it probably means Magento cannot locate your app/etc/local.xml. Since AWS normally gets your files from git and it is best practice to not have your local.xml in version control you are probably missing this one?
Hope that I pointed you in the right direction.
Keep in mind that the database is just your first challange, next things you are going to need to handle is:
Sessions (database is a good option but I use AWS ElastiCache with
Redis)
Cache (again, AWS ElastiCache with Redis)
Media Storage (I use S3 with S3FS and CloudFront)
CDN (CloudFront)
Here are some sites that have helped me setting up my first elastic beanstalks with Magento:
http://www.aschroder.com/2013/04/actually-running-magento-on-amazons-elastic-beanstalk-cloud-platform/
http://www.slideshare.net/corleycloud/scale-your-magento-app-with-elastic-beanstalk
We're looking to move to amazon cloud using EC2 and RDS.
I'm looking at load balancing, which I would like to do, two servers, each in a different availability zone to protect against downtime.
My question is how to deploy web applications and updates to them? I assume there is a better way than individually updating the files on each EC2 server?
In systems past, I have used the vcs puppet module to ensure that the appropriate source code is installed on my system, in addition to using puppet to build the configuration files for the apache/nginx server that I'm using. Another possibility is to push your application in a deployable state (if you're not using a scripting language) to Amazon S3, and have your run-time scripts pull the latest build from your S3 bucket.