Frequently Asked Questions

Identifying the Opportunity

What problem are We solving for you?

If you’re anticipating significant business growth and your systems are not ready for it, your company is going to experience problems. Our responsibility is to secure that your AWS infrastructure doesn’t put your projects and growth plans at risk.

How do you know if this is for you?

You want to assure your AWS infrastructure doesn't become an impediment to your growth. For example, you need your AWS hosted applications to handle 20x the amount of requests they handle today, without any degradation to the customer experience or AWS costs going through the roof whilst keeping it secure at the same time.

What type of organizations Is this for?

We work with companies and leaders who can drive and encourage change quickly within their organization. Ideally, you’re a company with 5-50 employees, and you can make decisions without going through various layers of approval. You are the decision-maker that can quickly hire service providers (like me), hire developers (if needed), update internal processes, approve AWS costs, etc.

When should you consider improving your Infrastructure on AWS?

"As early as possible", even when your applications still don't get much usage. When an application grows, so do its inefficiencies adding up to your technical debt. And some inefficiencies are structural, meaning they require some fundamental changes to correct them. You want to avoid this situation as much as possible; therefore, you should think about how you're going to grow your applications from day 1.

Execution and Delivery

What deliverables should be expected as part of our implementation?

The following are some examples of technical deliverables and tasks: architecting the infrastructure, writing automation scripts, assessing AWS components, setting up and updating AWS components (i.e. EC2 instances, VPCs, CloudWatch Dashboards, tags, etc.), creating Infrastructure as a code templates (Cloudformation or Terraform), running and analyzing load tests.

How do we deliver it?

There is a project plan, where we will disclosure timeframes,  costs and risks associated with the project which is updated collaboratively. We use collaboration tools, such as Jira, Slack, e-mail and video conferencing, but we can also fit into your team's communication flow to avoid any disruption on your side.  If required, we can schedule the initial iterations at your location to get started and meet your team in person.

What if you are still building a new application, or migrating to AWS?

As long as you’re using or planning to use AWS, our implementation methods will secure that your application can handle any expected growth. Evaluating and preparing it on early stages will benefit you and your team in your AWS adoption journey.

How do we ensure we don’t over-engineer everything?

To have enough visibility, we identify and quantify which activities are critical for your business growth at the very beginning. It will avoid the risk of over-thinking and over-engineering the infrastructure and its components on AWS, making sure we only invest our time and your money on essential features.

How about tunning your application source?

In most cases, we can achieve significant improvements by using the right AWS components. However, there might be cases where fine-tuning your application code could help. If this is the case, while we have extensive experience in the major frameworks and development languages like JAVA, PYTHON, PHP, Ruby on Rails, your development team should be in a better position to implement optimizations at the code level. Our implementation covers setting up the right monitoring tools and test procedures, which will give your team the ability to uncover issues that need application tuning.

Maintaining and Improving

What happens after we finish with a project?

We work based on optimization iterations and goals. Like any service provider, we will eventually move on. But we’re not your typical consultant or freelancer. A BIG difference is that in the end, you will have a process with valuable templates and documented steps. Your team will know how to implement future iterations and will have the processes and documents to do it. If you want AWS Assembly to help you with multiple iterations, we will be happy to do so. But when you’re ready to do them on your own, we will leave behind the necessary tools and knowledge. We want you to be successful in the short and long term.