AWS Technical Professional Certificate

AWS Technical Professional Certificate of Completion For Tim Layton @

Just a quick note to share that I took the AWS Partner Network AWS Technical Professional Training today along with the exam and I passed.

AWS Technical Professional Certificate of Completion For Tim Layton @

The AWS Technical Professional Training is a 3 hour training course along with a 30 question final exam requiring a minimum of 80% to pass. This training confirms the person passing the exam possess the fundamental technical knowledge of AWS cloud computing, AWS global infrastructure, services, solutions, migration, and security.

Get My Free Cloud Security Risk Management Journal

Course Objectives

  • Identify core AWS services and relate them to common architectures and use cases
  • Model a typical technical customer pre-engagement cycle
  • Recognize common discovery concerns and architectural challenges
  • Design a basic three-tier architectural solution using AWS services
  • Provide a visual representation of a Proof of Concept
  • Identify modern solutions and cost optimization needed for digital transformation

Course Outline

  • Module 1: Introduction
    This module covers course objectives and course overview.
  • Module 2: AWS Core Technologies
    This module covers cloud computing fundamentals, the benefits of using the AWS Cloud, why AWS products and services are the right choice for customers, and the value of AWS core services to your customers.
  • Module 3: From Services to Solutions
    This module covers architectural best practices, migration strategies, use cases and the Well-Architected Framework.
  • Module 4: Presenting AWS Solutions to Customers
    This module covers discovery questioning and whiteboarding skills used in a mock presentation, also Proof of Concepts (PoC) and customer meeting best practices.
  • Module 5: Looking Ahead
    This module covers implementation and modernization solutions, cost of the working solution, and optimizations made to be cost conscious for the customer.
    Module 6: AWS Partner Network (APN) Resources
    This module covers resources needed to experiment, build, and innovate.
  • Module 7: End of Course Assessment
    Complete this 30-question assessment to earn Accreditation as an AWS Technical Professional.

Tim Layton specializes in demystifying the complexities and technical jargon associated with cloud computing security and risk management for business stakeholders across the enterprise. Tim is a cloud security thought leader defining actionable and defensible strategies to help enterprise stakeholders make risk-based decisions and prioritize investments in the new digital frontier.

Stay Connected With Tim Layton



Get My Free Cloud Security Risk Management Journal


Threat: Any circumstance or event with the potential to adversely impact organizational operations (including mission, functions, image, or reputation), organizational assets, individuals, other organizations, or the Nation through an information system via unauthorized access, destruction, disclosure, or modification of information, and/or denial of service. (NIST 800–30)

Threat: potential cause of an unwanted incident, which can result in harm to a system or organization. (ISO 27001)

Vulnerability: Weakness in an information system, system security procedures, internal controls, or implementation that could be exploited by a threat source. (NIST 800–30)

Vulnerability: weakness of an asset or control that can be exploited by one or more threats. (ISO 27001)

Likelihood: A weighted factor based on a subjective analysis of the probability that a given threat is capable of exploiting a given vulnerability or a set of vulnerabilities. (NIST 800–30)

Likelihood: chance of something happening. (ISO 27001)

Risk: A measure of the extent to which an entity is threatened by a potential circumstance or event, and typically a function of (i) the adverse impacts that would arise if the circumstance or event occurs; and (ii) the likelihood of occurrence. (NIST 800–30)

Risk: effect of uncertainty on objectives. (ISO 27001)

Security Controls: The management, operational, and technical controls (i.e., safeguards or countermeasures) prescribed for an information system to protect the confidentiality, integrity, and availability of the system and its information. (NIST 800–30)

Compensating Security Control: A management, operational, and/or technical control (i.e., safeguard or countermeasure) employed by an organization in lieu of a recommended security control in the low, moderate, or high baselines that provides equivalent or comparable protection for an information system. (NIST 800–30)

Impact Level: The magnitude of harm that can be expected to result from the consequences of unauthorized disclosure of information, unauthorized modification of information, unauthorized destruction of information, or loss of information or information system availability. (NIST 800–30)

Residual Risk: Portion of risk remaining after security measures have been applied. (NIST 800–30)

Security Posture: The security status of an enterprise’s networks, information, and systems based on information assurance resources (e.g., people, hardware, software, policies) and capabilities in place to manage the defense of the enterprise and to react as the situation changes. (NIST 800–30)

Get My Free Cloud Security Risk Management Journal

Tim Layton

Tim Layton

Get Tim Layton's Free Cloud Security Journal so you can remain current with the latest cloud security trends and updates. Tim is a cloud security thought leader defining actionable and defensible strategies to help organization's make risk-based decisions and prioritize investments.

Recommended Articles

Leave a Reply

Your email address will not be published.