Articles
** At high level, im responsible for all technical aspects of bringing the new client onto Amazon’s cloud platform instill confidence, build andmaintain trust to make transiton as graceful and seamless as possible so that their decision to invest in and adopt Amazon as their critical services provider never wavers. ** Specific role is to act in capacity of liaison with client and amazon’s intermal teams to customize a solution based on using a proper synthesis of amazon cloud services. i effectively work to build a trust-based relationship with client foremost client needs to have implicit trust of your confidence in Amazon’s offerings and in my ability to bring ideas for relevant solutions to the discussion my role broadens to that of a liaision between the client and Amazon teams use available internal teams and partners collaboratively to determine most appropriate, effective, reliable, fault tolerant solution segway to Amazon points of Leadership im not necessarily tasked with doing the buildout. other teams and partners for that. ill work with Amazon internal teams and partners. they’ll provide leverage in terms of deep, low-level knowledge of Amazon’s component products, their appropriate uses, nuances and potential complications or incompatibilities that may be problematic when used in integration with other products or within a particular architecture. what are other, various types of teams? enterprise teams smb teams project leads business analysts data specialists security specialists, etc. — how does solutions architect allocate their time day-to-day? 1. 1/2 time spent engaging with customers. do architectural review with client, at same time building trust) while concurrently formulating solutions to help customers address their business pains, be it to improve on their own internal systems architecture or migrate to cloud (less reliance on internal staff by taking advantage of amazon’s large, skilled resource pool) and develop custom software solutions to meet their particular business challenges build out proof of concepts 2. other 1/2 internal meetings (sales funnel, current customer progress, backlog funnel/burndown log, etc.), self-education (product updates, new products) presentations, writing articles, leading tech workshops, mentoring scope creep – “the extent of what a project will produce and the resources needed to produce it.” — What’s It Like to Be a Solution Architect at AWS? https://www.youtube.com/watch?v=IBqqYWr4t94 —
where to start? what is my approach to architecture? “do not try to boil the ocean.” dont think of everything at once. dont try to solve it at once. start high-level what is your business? what do you do? audience – who are customers? what are thy getting from you? how are they hoping to benefit by using your services? customer consumption – how are customers consuming or accessing info from your system? technical: ingestion- how is data ingested processing- how is processing occurring? storage- how is customer ready being stored need to understand pillars and their priorities pillars are: operational excellence security reliability performance efficiecy cost design will change based on prioritization of “pillars” e.g. high security system possible components: web app firewall, tokenization, encryption, cust managed keys, IP traffic monitoring and constraints — Stream processing example: 1. Kinesis – to load in social media stream real time, then trigger lambda to generate hastag trend data 2. Dynamo DB – store hashtag data, trend data for compilation of analytics reports — Weather service web app example: 1. S3 – to host front end code 2. Amazon API Gateway – make REST API call to endpopint 3. trigger lambda to retrieve weather info 4. dynamodb – store weather data used by application — IOT: 1. a farm tractor sends data to amazon through amazon API? 3. Kinesis – captures data and streams itr to lambda for processing 3. lambda runs code to detect trends in sensor data, identify anomalies, order replacement parts 4. dynamodb – to store raw signals then sends to kinesis for processing amazon examples: three tier retail/ecommerce analytics — retail site possible architectural components- 1. consumption – use APIs and front end (possibly EC2 for front end server) 2. processing front and backend storage – 1 EC2 instance for back end, then multiple databases, 1 for product info (1 amazon aurora db) 1 for trans info (1 amazon aurora db) 3. ingestion – some batch processes, real-time product loading (API) 4. if is public retail product specs perhaps heavy security not needed —
video on AWS architecture
