- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
Hello,
Yes, it's the default CloudFormation template used by Elastic Beanstalk to create an associated RDS that seems to be the problem. I think this is a bug that should be fixed on the aws side, right? I mean we should be able to attach an RDS to the environment without having to fix the default CloudFormation template.
Thanks
Did you face the same issue?
Yes, unfortunately :/
Please let me know if you have any solution for this
I think you are dealing with key value pair data within your CloudFormation template. Since I do not have your template, I advise you to go through this blog post - which talks about several tweaks which can be used inside a CloudFormation template, specifically Ctrl + F
for Use Dictionaries as Stack Parameter
this might help you.
Actually, I didn't define or build any template in CloudFormation. I've just used Elastic Beanstalk Console. However, I've searched the generated template but everything seems okay about the link that you sent
Contenuto pertinente
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 7 mesi fa
Can you share how you define SecurityGroupIngress in CloudFormation?
@alatech I didn't define anything in the CloudFormation, I've only used the Elastic Beanstalk UI but here is the definition and also it seems there is no RDS related definition at all. https://prnt.sc/YLgeCwt-lNHa