-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
(aws-elasticsearch): Domain.fromDomainEndpoint
returning incorrect ARN
#13380
Comments
@justindra Thanks for reporting this. Looks like we neglected to consider the
|
Linking #10841 since I believe a solution here would need to address it. |
…earch- prefix from domainEndpoint fixes: aws#13380
+1 Spotted this issue - the permissions given by Although I have some concerns about the possible clashes of the prefixes we should take into account ( Someone could have a look on this one (and the linked pull request?) |
…earch- prefix from domainEndpoint fixes: aws#13380
I'm in agreement with @iliapolo above (#13380 (comment)); we should not attempt to parse the domain name from the endpoint, ever. Instead of expanding the current extraction logic, we should instead deprecate |
Found the same issue in May I suggest to add a method |
It also doesn't extract the region, instead assuming it exists in the same region as the stack |
This is still not fixed as of 2.162.1 |
When using the
Domain.fromDomainEndpoint
function to retrieve an ES Instance and reference in the rest of the Stack, it returns an incorrect ARN. When I output the ARN, it gives the following results:Reproduction Steps
What did you expect to happen?
The provided ARN should be the correct ARN
What actually happened?
The provided ARN was incorrect
Environment
Other
This is 🐛 Bug Report
The text was updated successfully, but these errors were encountered: