- Newest
- Most votes
- Most comments
Yes, you can access Amazon OpenSearch Service with your free tier account. The AWS Free Tier for OpenSearch Service provides up to 750 hours per month of a t2.small.search or t3.small.search instance, along with 10 GB per month of optional Amazon EBS storage.
Based on your situation, it sounds like there might be an issue with your account activation. Even though you mentioned your account setup is complete, being redirected to the "incomplete signup" page suggests there might be some activation steps that need to be finalized. To fully activate your AWS account and access OpenSearch, ensure you have:
- Added a valid payment method to your account
- Verified your phone number
- Chosen an AWS Support Plan (even the free Basic plan)
Once your account is fully activated, you should be able to access OpenSearch Service. When creating an OpenSearch domain, make sure to:
- Select "Domain without standby" as the deployment option
- Change the "Instance Family" to "General Purpose"
- Then select "t3.small.search" as your instance type to stay within the free tier
If you've already completed all activation steps and are still being redirected to the incomplete signup page, you may need to contact AWS Support for further assistance.
Sources
Free tier do not show any service when create new account | AWS re:Post
Is there anything resembling a "free tier" for OpenSearch? | AWS re:Post
No free tier visible | AWS re:Post
What is the equivalent of t2.small.elasticsearch instance type in Open Search | AWS re:Post
answered a year ago
Relevant content
asked 2 years ago
asked 5 months ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 2 years ago

I don't know what is wrong here, created a new AWS root+user account, and faced the same issue while deleting the OpenSearch Serverless Collection.
For now I am using CLI
aws opensearchserverless list-collections
aws opensearchserverless delete-collection --id <collection-id>
and just recheck if its deleted aws opensearchserverless list-collections
It works through CLI but not on console. @AWS_Support should look into it.