# Deploy Mender on AWS using managed services

**URL:** <https://hub.mender.io/t/deploy-mender-on-aws-using-managed-services/1728>\
**Category:** General Discussions\
**Created:** [April 1, 2020, 1:23pm UTC](https://hub.mender.io/t/deploy-mender-on-aws-using-managed-services/1728 "2020-04-01T13:23:58Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![J-Mx](https://avatars.discourse-cdn.com/v4/letter/j/ee59a6/32.png) [@J-Mx](https://hub.mender.io/u/J-Mx)\
**Post date:** [April 1, 2020, 1:23pm UTC](https://hub.mender.io/t/deploy-mender-on-aws-using-managed-services/1728/1 "2020-04-01T13:23:58Z")

</div>

Hi everyone,

I’m trying to deploy Mender for testing purpose on AWS with the following components :

- ECS (for containers)
- Elasticache (Redis)
- Managed Elasticsearch
- DocumentDB (with mongo 3.6 compatibility)

While trying to launch mender-deployments container 1.8.0 (mender 2.2), I have the following message :

```auto
time="2020-04-01T13:14:14Z" level=info msg="Deployments Service, version unknown starting up"
time="2020-04-01T13:14:14Z" level=info msg="automigrate is ON, will apply migrations" file=migrations.go func=mongo.Migrate line=48
time="2020-04-01T13:14:14Z" level=info msg="migrating deployment_service" file=migrations.go func=mongo.MigrateSingle line=70
time="2020-04-01T13:14:14Z" level=info msg="applying migration from version 0.0.0 to 1.2.1" db=deployment_service file=migrator_simple.go func="migrate.(*SimpleMigrator).Apply" line=101
time="2020-04-01T13:14:14Z" level=error msg="migration from 0.0.0 to 1.2.1 failed: Index type not supported : text" db=deployment_service file=migrator_simple.go func="migrate.(*SimpleMigrator).Apply" line=106
failed to run migrations: failed to apply migrations: failed to apply migration from 0.0.0 to 1.2.1: Index type not supported : text

```

with mender-deployments container 1.9.0 (mender 2.3)

```auto
time="2020-04-01T11:48:44Z" level=info msg="Deployments Service, version unknown starting up"
time="2020-04-01T11:48:44Z" level=info msg="automigrate is ON, will apply migrations" file=migrations.go func=mongo.Migrate line=48
time="2020-04-01T11:48:44Z" level=info msg="migrating deployment_service" file=migrations.go func=mongo.MigrateSingle line=70
time="2020-04-01T11:48:44Z" level=info msg="applying migration from version 0.0.0 to 1.2.1" db=deployment_service file=migrator_simple.go func="migrate.(*SimpleMigrator).Apply" line=101
time="2020-04-01T11:48:44Z" level=error msg="migration from 0.0.0 to 1.2.1 failed: ns not found" db=deployment_service file=migrator_simple.go func="migrate.(*SimpleMigrator).Apply" line=106
failed to run migrations: failed to apply migrations: failed to apply migration from 0.0.0 to 1.2.1: ns not found

```

Did you ever experienced this kind of problem ? Or is there any workaround ?

Thanks for your help 🙂

---

<div class="post-metadata">

**Author:** ![J-Mx](https://avatars.discourse-cdn.com/v4/letter/j/ee59a6/32.png) [@J-Mx](https://hub.mender.io/u/J-Mx)\
**Post date:** [April 1, 2020, 7:42pm UTC](https://hub.mender.io/t/deploy-mender-on-aws-using-managed-services/1728/2 "2020-04-01T19:42:57Z")

</div>

I did not mention that in my previous message but DocumentDB on AWS does not support Text Index (cf [https://docs.aws.amazon.com/documentdb/latest/developerguide/mongo-apis.html#mongo-apis-index](https://docs.aws.amazon.com/documentdb/latest/developerguide/mongo-apis.html#mongo-apis-index)).

Is there any possibilities to boostrap the data structure of deployment without this index ?