跨帐户复制Elastic Beanstalk配置 [英] Copy Elastic Beanstalk Configuration across accounts

查看:78
本文介绍了跨帐户复制Elastic Beanstalk配置的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

如果我使用 eb-cli eb config save保存我当前环境的配置,它可以使用eb create启动一个新环境.

If i use the eb-cli eb config save to save the configuration of my current environment it works to start a new one using eb create.

但是,如果我想使用不同的AWS账户创建相同的环境,显然以下行是毫无意义的:

But if i want to create the same environment with a different AWS account obviously lines like the following make no sence:

aws:ec2:vpc:
    Subnets: subnet-2d9a3c56
    VPCId: vpc-1dff4c74

那么我如何在多个帐户中构建相同的弹性beantalk环境?有什么办法告诉AWS?也许是帐户不可知"的配置保存?

So how can i build the same elastic beanstalk environment within multiple accounts? Is there any way to tell AWS? Maybe an "Account Agnostic" config-save?

推荐答案

不可能跨帐户构建完全相同的ElasticBeanstalk环境.该环境将具有不同的资源ID,例如VPC和子网.

It would not be possible to build the exact same ElasticBeanstalk environment across accounts. The environment is going to have resource IDs such as VPCs and Subnets that will be different.

在多个帐户中有效构建 相同ElasticBeanstalk应用程序的一种好方法是使用CloudFormation来配置环境.这需要使用不同的方法来创建环境,但也意味着可以更轻松地控制配置的版本.

A good way to build effectively the same ElasticBeanstalk application across multiple accounts would be to use CloudFormation to configure the environments. This requires a different approach to creating environments, but also means that the configuration can be more easily version controlled.

这篇关于跨帐户复制Elastic Beanstalk配置的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆