As an AWS solution architect, your job involves just that: architectural solutions. So spend most of your days meeting with sales and / or customers. These can be in-person meetings or as part of conference calls to learn about problems and needs. This depends on the company you work for and your location in the company. Some AWS solution architects focus more on the product, not the customer. While most people work to find solutions to customer problems.
The
work you do for customers will also depend on where you work and what your
activities are, as well as where the customer is in their AWS adoption stage.
They could be at an early stage until you have high-level conversations, or
later or even in implementation. That's all about it.
As
we mentioned earlier, a key part of your job will be to design solutions to
meet customer needs and business goals, develop technical solutions and
pre-sale products in support of customer goals. Therefore, you will spend part
of your day doing what we call "problem solving." As in the US, you
develop solution plans and provide guidance on AWS architectural best
practices. You will estimate costs and identify cost control methods, as well
as select an appropriate AWS service based on data, computing, database, or
security requirements.
You
can spend part of your days designing and configuring scalable, accessible, and
resilient systems on AWS. Identify the elevation and transfer of the existing
application to AWS. Along with this, you need to enter and export data to and
from AWS. You may be asked to provide guidance on issues such as performance,
cost, disaster recovery, or security issues.
No comments:
Post a Comment