Is it possible to allow a VPC in one AWS account to access an opensearch serverless collection in a different AWS account?
The docs for managed opensearch seem to support this: https://docs.aws.amazon.com/opensearch-service/latest/developerguide/vpc-interface-endpoints.html but not serverless: https://docs.aws.amazon.com/opensearch-service/latest/developerguide/serverless-vpc.html
Also the UI in the AWS console is different for both (https://us-west-2.console.aws.amazon.com/aos/home?region=us-west-2#opensearch/vpc-endpoints vs. https://us-west-2.console.aws.amazon.com/aos/home?region=us-west-2#opensearch/vpcEndpoint):
- Le plus récent
- Le plus de votes
- La plupart des commentaires
Hi,
It does not seem that OS serverless supports cross domain. It seems cross-account domain access for OpenSearch was recently releases for the non-serverless version in November 2022. (https://aws.amazon.com/about-aws/whats-new/2022/11/amazon-opensearch-cross-vpc-connectivity-aws-privatelink/).
OpenSearch serverless was released in preview at reinvent 2022 and made generally available in January 2023 (https://aws.amazon.com/blogs/big-data/amazon-opensearch-serverless-is-now-generally-available/).
It could easily be that cross domain is not a supported feature for time being.
Hopefully feature parity will be reached soon.
Hope it clarifies.
Contenus pertinents
- demandé il y a un an
- demandé il y a 2 mois
- demandé il y a un an
AWS OFFICIELA mis à jour il y a un an- AWS OFFICIELA mis à jour il y a un an
yea that's what I figured, could someone from AWS chime in about if this is in the works/when it would be released?
With the min cost of $700 a month per AWS account for serverless (https://repost.aws/questions/QUAc9Mg6avRCy3e5kOF8v5fQ/pricing-strategy-for-open-search-serverless) I was hoping to share one serverless setup in one AWS account, that multiple other AWS accounts (in the same region) could use via VPC connections to maximize cost savings.
But if this is not supported, I wouldn't be able to do that and opensearch serverless probably wouldn't be feasible for my organization
I see. If above helped anyway to make clear that is not possible, I d appreciate if answer could be accepted, to benefit clarity in community. Thanks