AWS Architecting & Ecosystem

Question 1

AWS Knowledge Center

Answer 1

Contains the most frequent & common questions and requests

Question 2

APN Technology Partners

Answer 2

providing hardware, connectivity, and software

Question 3

APN Consulting Partners

Answer 3

professional services firm to help build on AWS

Question 4

APN Training Partners

Answer 4

find who can help you learn AWS

Question 5

AWS Competency Program

Answer 5

AWS Competencies are granted to APN
Partners who have demonstrated technical proficiency and proven
customer success in specialized solution areas

Question 6

AWS Navigate Program

Answer 6

help Partners become better Partners

Question 7

AWS Marketplace

Answer 7

• Digital catalog with thousands of software listings from
independent software vendors (3rd party)

• Example:
Custom AMI (custom OS, firewalls, technical solutions…)
CloudFormation templates
Software as a Service
Containers

• If you buy through the AWS Marketplace, it goes into your AWS bill
• You can sell your own solutions on the AWS Marketplace

Question 8

Developer Plan

Answer 8

• Business hours email access to Cloud Support Associates
• General guidance: < 24 business hours
• System impaired: < 12 business hours

Question 9

Business Plan

Answer 9

• 24x7 phone, email, and chat access to Cloud Support Engineers
• Production system impaired: < 4 hours
• Production system down: < 1 hour

Question 10

Enterprise Plan

Answer 10

• Access to a Technical Account Manager (TAM)
• Concierge Support Team (for billing and account best practices)
• Business-critical system down: < 15 minutes

Question 11

AWS Quick Starts

Answer 11

• Automated, gold-standard deployments in the AWS Cloud
• Build your production environment quickly with templates
• Example: WordPress on AWS
• Leverages CloudFormation

Question 12

AWS Solutions

Answer 12

• Vetted Technology Solutions for the AWS Cloud

* Example - AWS Landing Zone: secure, multi-account AWS environment, “Replaced” by AWS Control Tower

Question 13

AWS Well Architected Tool

Answer 13

Free tool to review your architectures against the 5 pillars Well-Architected
Framework and adopt architectural best practices

Question 14

Cost Optimization

Answer 14

Includes the ability to run systems to deliver business value at the lowest
price point

Design Principles:
• Adopt a consumption mode - Pay only for what you use
• Measure overall efficiency - Use CloudWatch
• Stop spending money on data center operations - AWS does the infrastructure
part and enables customer to focus on organization projects
• Analyze and attribute expenditure - Accurate identification of system usage and
costs, helps measure return on investment (ROI) - Make sure to use tags
• Use managed and application level services to reduce cost of ownership - As
managed services operate at cloud scale, they can offer a lower cost per
transaction or service

Question 15

Performance Efficiency

Answer 15

Includes the ability to use computing resources efficiently to meet
system requirements, and to maintain that efficiency as demand changes
and technologies evolve

Design Principles:
• Democratize advanced technologies - Advance technologies become services
and hence you can focus more on product development
• Go global in minutes - Easy deployment in multiple regions
• Use serverless architectures - Avoid burden of managing servers
• Experiment more often - Easy to carry out comparative testing
• Mechanical sympathy - Be aware of all AWS services

Question 16

Reliability

Answer 16

Ability of a system to recover from infrastructure or service disruptions,
dynamically acquire computing resources to meet demand, and mitigate
disruptions such as misconfigurations or transient network issues

Design Principles:
• Test recovery procedures - Use automation to simulate different failures or to recreate
scenarios that led to failures before
• Automatically recover from failure - Anticipate and remediate failures before they occur
• Scale horizontally to increase aggregate system availability - Distribute requests across
multiple, smaller resources to ensure that they don’t share a common point of failure
• Stop guessing capacity - Maintain the optimal level to satisfy demand without over or
under provisioning - Use Auto Scaling
• Manage change in automation - Use automation to make changes to infrastructure

Question 17

Security

Answer 17

Includes the ability to protect information, systems, and assets while delivering
business value through risk assessments and mitigation strategies

Design Principles:
• Implement a strong identity foundation - Centralize privilege management and reduce (or even eliminate) reliance on long-term credentials - Principle of least privilege - IAM
• Enable traceability - Integrate logs and metrics with systems to automatically respond and take action
• Apply security at all layers - Like edge network, VPC, subnet, load balancer, every instance, operating system, and application
• Automate security best practices
• Protect data in transit and at rest - Encryption, tokenization, and access control
• Keep people away from data - Reduce or eliminate the need for direct access or manual
processing of data
• Prepare for security events - Run incident response simulations and use tools with automation to increase your speed for detection, investigation, and recovery

Question 18

Operational Excellence

Answer 18

Includes the ability to run and monitor systems to deliver business value
and to continually improve supporting processes and procedures

Design Principles:
• Perform operations as code - Infrastructure as code
• Annotate documentation - Automate the creation of annotated documentation
after every build
• Make frequent, small, reversible changes - So that in case of any failure, you can
reverse it
• Refine operations procedures frequently - And ensure that team members are
familiar with it
• Anticipate failure
• Learn from all operational failures