You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe
Currently when NetworkPolicy includes AllowFromPublic=false, calls to the opensearch data plane to create indexes from developer workstations (outside of the VPC) where the IaC is coded, get Unauthorized Errors, which is expected behavior. Security would be enhanced by providing the requested API so there is no need to set AllowFromPublic=true, just for developer ease of workload to create indexes from their dev env.
Describe the solution you'd like
Support creating indexes via AWS SDK to enable IaC tools (like Terraform) to create indexes while network policies (such as in AOSS) where AllowFromPublic=false
Related component
No response
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Thanks @FireballDWF. This request looks pretty AWS-specific, so I don't think this is the right place. I recommend reaching out to AWS to help with this. Please reopen with more details if you think there is something missing in the open-source code base that can help here.
Is your feature request related to a problem? Please describe
Currently when NetworkPolicy includes AllowFromPublic=false, calls to the opensearch data plane to create indexes from developer workstations (outside of the VPC) where the IaC is coded, get Unauthorized Errors, which is expected behavior. Security would be enhanced by providing the requested API so there is no need to set AllowFromPublic=true, just for developer ease of workload to create indexes from their dev env.
Describe the solution you'd like
Support creating indexes via AWS SDK to enable IaC tools (like Terraform) to create indexes while network policies (such as in AOSS) where AllowFromPublic=false
Related component
No response
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: