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

OpenSearch substack and resource type #505

Open
tnh opened this issue Feb 6, 2024 · 2 comments
Open

OpenSearch substack and resource type #505

tnh opened this issue Feb 6, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@tnh
Copy link

tnh commented Feb 6, 2024

If your issue relates to the Discovery Process, please first follow the steps described in the implementation guide Debugging the Discovery Component


Describe the bug
A . opensearch stack supports wrong instances.

To Reproduce
Steps to reproduce the behavior:

in ap-southeast-2

2024-02-07 06:33:15 UTC+1100 | OpenSearchDomain | CREATE_FAILED | Resource handler returned message: "Invalid request provided: Invalid instance type: t2.micro.search (Service: OpenSearch, Status Code: 409, Request ID: 35c47295-674b-48a9-ac35-90a8d7372404)" (RequestToken: 9fc245d0-a586-9d23-638b-456a7aebec48, HandlerErrorCode: InvalidRequest)
-- | -- | -- | --

instance supports t2.micro for search, but clearly doesnt in ap-southeast-2.

Using version :v2.1.5

Description: Workload Discovery on AWS Main Template (SO0075a) - Solution - Main Template (uksb-1r0720e27) (version:v2.1.5)
@tnh tnh added the bug Something isn't working label Feb 6, 2024
@tnh
Copy link
Author

tnh commented Feb 6, 2024

@svozza
Copy link
Contributor

svozza commented Feb 6, 2024

That's very odd, according to the OpenSearch docs that instance type should be supported in ap-southeast-2.
Screenshot 2024-02-06 at 22 16 17

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants