workload-discovery-on-aws icon indicating copy to clipboard operation
workload-discovery-on-aws copied to clipboard

OpenSearch substack and resource type

Open tnh opened this issue 1 year ago • 2 comments

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 avatar Feb 06 '24 19:02 tnh

think its just as simple as reducing this list: https://github.com/aws-solutions/workload-discovery-on-aws/blob/main/source/cfn/templates/main.template#L154

tnh avatar Feb 06 '24 21:02 tnh

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

svozza avatar Feb 06 '24 22:02 svozza