Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Elasticbeanstalk Health Endpoint fails with "InvalidServiceName" #481

Closed
Xaaris opened this issue Aug 5, 2020 · 1 comment
Closed

Elasticbeanstalk Health Endpoint fails with "InvalidServiceName" #481

Xaaris opened this issue Aug 5, 2020 · 1 comment

Comments

@Xaaris
Copy link
Contributor

Xaaris commented Aug 5, 2020

When trying to set enable_elasticbeanstalk_health_endpoint = true we always encounter a the following error:

InvalidServiceName: The Vpc Endpoint Service 'com.amazonaws.eu-central-1.elasticbeanstalk.health' does not exist

In the UI this endpoint exists, although as elasticbeanstalk-health (with a "-" in the name)

@github-actions
Copy link

github-actions bot commented Nov 1, 2022

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 1, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants