简体繁体 English

尝试使用Ubuntu AMI启动AWS Elastic beantalk实例

[英]Trying to launch AWS Elastic beanstalk instance with Ubuntu AMI

原文 2015-12-04 01:47:03 1 1 mongodb/ amazon-web-services/ amazon-ec2/ ubuntu-14.04/ elastic-beanstalk

I am trying to create an elastic beanstalk instance in AWS with an Ubuntu AMI (Ubuntu Server 14.04 LTS (HVM), SSD Volume Type - ami-d05e75b8) and MongoDB. 我正在尝试使用Ubuntu AMI（Ubuntu Server 14.04 LTS（HVM），SSD卷类型-ami-d05e75b8）和MongoDB在AWS中创建一个弹性beantalk实例。 To change the AMI I am following these steps . 要更改AMI，请按照以下步骤操作。 And I have a few questions. 我有几个问题。

1) I have gotten the impression that I cannot change the AMI to Ubuntu in elastic beanstalk without hacking away at it. 1）我得到的印象是，我无法在不破坏它的情况下通过弹性beantalk将AMI更改为Ubuntu。 Is this true? 这是真的？

If number 1) is False then .... 如果数字1）为False，则....

2) In the steps link: What is Number 7, under To create a custom AMI , referring to by repository version number . 2）在步骤链接中： 要创建自定义AMI下的编号7，是按存储库版本号引用的。 I do not see a date in the AMI for ubuntu (ami-d05e75b8) 我在AMI中看不到ubuntu的日期（ami-d05e75b8）

3) I have gotten the impression that I cannot incorporate MongoDB in elastic beanstalk without hacking away at it. 3）我得到的印象是，如果不修改它，就无法将MongoDB合并到弹性beantalk中。 Is this true? 这是真的？

Thank you for your help! 谢谢您的帮助！ I would also be very appreciative with any other insight you can provide. 对于您可以提供的其他任何见解，我也将非常感激。

1 个解决方案

Not sure what you mean by "hacking away at it", but in general I wouldn't recommend taking that path. 不知道“破解”是什么意思，但总的来说，我不建议您采用这种方式。 Using a custom AMI deprives you of future Beanstalk upgrades, so you'll have to recreate your AMI every couple of months just to keep up with the latest Beanstalk changes. 使用自定义AMI会使您无法进行将来的Beanstalk升级，因此您必须每隔几个月重新创建一次AMI，以跟上最新的Beanstalk更改。

Instead, I'd vote to use the Docker version of Elastic beanstalk . 相反，我将投票使用Docker版本的Elastic beanstalk 。 It allows you to create a custom contain (eg Ubunto with Mongo) and let Elastic Beanstalk launch it. 它允许您创建自定义包含（例如，Ubunto和Mongo），并让Elastic Beanstalk启动它。 This way you focus on your container instead of the Beanstalk scripting. 这样，您就可以专注于容器而不是Beanstalk脚本。

If you're unfamiliar with Docker, here's a nice place to start: https://training.docker.com/self-paced-training 如果您不熟悉Docker，那么这里是一个不错的起点： https ： //training.docker.com/self-paced-training