By using AWS re:Post, you agree to the Terms of Use

Questions tagged with Security Group

Sort by most recent

Browse through the questions and answers listed below or filter and sort to narrow down your results.

Elastic Beanstalk: Unable to access environment's Configuration. Error: A problem occurred while loading your page: Configuration validation exception:

I rarely log into the AWS console. I deploy using the CLI. I logged in recently to see my EB configuration and was redirected back to the applications page "Elastic Beanstalk > Applications" with the error: ``` Error 
A problem occurred while loading your page: Configuration validation exception: Invalid option value: 'awseb-e-XXXXXXXX-stack-AWSEBSecurityGroup-XXXXXXXX’ (Namespace: 'aws:autoscaling:launchconfiguration', OptionName: 'SecurityGroups'): The security group 'awseb-e-XXXXXXXX-stack-AWSEBSecurityGroup-XXXXXXXX' does not exist ``` Prior to this error message I got a slightly different one referring to Launch Template referencing that security group. I created a version 2 of the launch template but used the UI to point to the correct security group. Now that error is gone and I see this new one in its place. I have since redeployed the app, thinking it needed the new template to take effect. I have tried using `eb config` to change/update the template name and then redeploy but it didn't work. Not sure what's changed or how to fix. Any help would be appreciated. **Update 1:** Just to be clear, the website is functioning correctly. Nothing is down. No errors, as far as I can tell, in the logs. This issue is only localized to "Elastic Beanstalk > Applications" page. **Update 2:** Per the suggestion to clone the environment, I tried but the error appears there too preventing me from proceeding. See image below. Interestingly, I was able to create a brand new, clean, Elastic Beanstalk environment from scratch, but then when I tried to view its completely unrelated configuration I also got this error. About the suggestion that perhaps I deleted something at some point, I think that's very doubtful because I don't tinker with my environment, I set it up once and then I leave it. I last touched it in January (6+ months ago) when I upgraded the Platform to AL2. There were no errors then and the only interaction with Elastic beanstalk prior to the upgrade and post upgrade is running my make file like so: `make deploy_aws_production` so I don't even work with the CLI really. ![Enter image description here](https://repost.aws/media/postImages/original/IMdqob0ct3QYGaJ2dEiB5l6w)
1
answers
0
votes
78
views
asked 2 months ago
3
answers
0
votes
122
views
asked 3 months ago