The Amazon configuration IT process usually takes a couple of hours. If the requirements are clear and there are no additional requests from the customer's side, it's just a matter of a couple of hours to set up the new components for straightforward and simple requirements.

We can handle the setup ourselves. It's very easy.

My first Amazon API Gateway deployment took five to ten minutes. My boss requested me to expose the Lambda for internal use cases. I didn't have any experience with Amazon API Gateway at that moment, but I was able to expose the API, which was very, very easy.

In my previous company, they had a lot of people responsible for the solution's maintenance. Developers are responsible for personalizing the configurations inside Amazon API Gateway. They need to understand the requirements of the API and maximize site API. At that moment, I was responsible for having the permissions and putting the information in Amazon API Gateway. We need two or three people responsible for around 30 APIs and some developers.

My company sought an integrator's help to carry out the product's installation process.

The deployment time is contingent on the other services we provide, the features we utilize, and the consultants involved. The duration of this process is influenced by the integration aspects, typically spanning just a few weeks. We deploy using the POC process, adapting specifics to client preferences and performance needs. Clients can choose Docker, Kubernetes, or Amazon API Gateway based on their interests and infrastructure requirements.

API Gateway is an Amazon service that doesn't require deployment on the local workstation. Using WebUI, you configure settings, click "deploy," and the changes are stored on Amazon's storage, taking only a few seconds for the changes to take effect. Unlike traditional deployment, you're not creating binary files. Instead, you're adjusting configuration settings.

There is no team needed for deployment, however, a software architect is needed for the configuration.

The deployment was done in-house. One DevOps engineer is enough for the process. 

We don't need to maintain the solution. It just works. It does not require any maintenance. 

We did not use a consultant or an integrator. We handled all the work in-house, including authenticating and setting up the architecture. 

Deployment time for API Gateway is notably swift. When initiating a new creation within API Gateway, the integration with the DevOps pipeline, especially if all components reside within AWS, ensures a seamless and rapid deployment process. It swiftly establishes the API, sets up the necessary infrastructure, configures the API Gateway, and identifies the requisite DNS for the Gateway endpoints.

We did the implementation in-house. We did not need outside assistance from consultants or integrators. We had people on our team that could do it.

A consultant facilitated the setup.

We completed the installation ourselves.

I took care of the deployment myself.

We used an in-house resource. In terms of maintenance, we have a team that supervises not only this product but also other products. I think the product itself doesn't require much monitoring or maintenance. It is really managed by the cloud.

We are an integrator, so we did the implementation ourselves.

We did the implementation of the solution in-house.

We implemented this in-house. 

The deployment has taken us around eighteen minutes to complete.

We have a good team to handle the implemenation and deployment. Most of our people are pretty technical.