One person can do the deployment. The service itself doesn't require maintenance. It's the content that needs attention. It's like any data store or any form. If you put garbage or corrupt data in it, you will get a corrupted result. So, the service itself is flawless. It works exactly as advertised. 

But if you store the wrong data in it, with the wrong key and the wrong values, you will get the wrong results. So, the maintenance is not so much in DynamoDB itself. The maintenance is in your data stream.

We have a cloud engineer who takes care of running, upgrading, and supporting about 60 to 70 DynamoDBs in the physical sense, although that might be a bad term to use with cloud services. And he does it all by himself. So, one person can, in the current state of affairs with cloud services, oversee quite a large number of services.

We can deploy Amazon DynamoDB in one to two hours.

The deployment was done in-house.

I got myself involved in the process.

It is a service from Amazon. So that's one of the benefits; you just use it. There is no maintenance required. 

An in-house team implemented it.

It took a couple of minutes to deploy it. 

We always use Terraform or another EAC tool to create a resource. We never deploy a resource using the console.

One person is enough for the deployment and maintenance of the solution. 

We implement the product in-house.

It is being done in-house, but as our client base grows, we might end up switching to a consultant.

I implemented the solution myself.