Add ability equivalent to --parameter-overrides of aws cloudformation deploy to eb deploy command

[remi00]

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request. Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request. If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Tell us about your request

.ebextensions already support Parameters of AWS Cloudformation. However, currently it seems to be just a way to tidy up shared configuration and nothing else. It is not possible to keep using .ebextensions with configurable Parameters and eb deploy.

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?

Flexible way to combine configuration management around EB, AWS SSM/SecretsManager and AWS CFN without switching from EB CLI to AWS SDK or AWS CLI. This is needed to be able to deploy more than just staging and production envs of the system but also easily scale out to deploy other ad-hoc or deverlopers instances of the system I collaborate to.

Are you currently working around this issue?

How are you currently solving this problem?

Most probably I will convert .ebextensions into some kind of templates with external ability to resolve tokens like ${TARGET} into actual string values.

[Palakpatel67]

@remi00 thanks for reaching out. We will look into this and post any updates to this feature request here.

[k-hasan-19]

Hi, is there any update on this? Need to deploy EB stack reosurces based on different param values base on deployment env.

[PraveenKumarPalai]

I am also looking for something similar, need to deploy to two different envs. using parameterized values for the cloud formation stacks.