Cloud Academy – AWS Config an Introduction

Cloud Academy – AWS Config an Introduction-STM
English | Size: 1.04 GB
Category: CBTs

With the ever-changing nature of Cloud Computing in AWS, through the use of Auto Scaling, and self-healing architecture mechanisms, having visibility and awareness of your AWS resources is invaluable. It can be difficult to understand what your resources within your infrastructure looks like, for example:

Cloud Academy – AWS Identity Federation

Cloud Academy – AWS Identity Federation-STM
English | Size: 611.00 MB
Category: CBTs

AWS Identity Federation is the concept of using external authorization sources to permit access to AWS Console and AWS Resources. Identity Federation comes is multiple levels that enables the use of existing directories or SAML to ensure users are accredited and authenticated to access AWS Intended audience:

Cloud Academy – AWS Config An Introduction

Cloud Academy – AWS Config An Introduction
English | Size: 1.03 GB
Category: Tutorial

With the ever-changing nature of Cloud Computing in AWS, through the use of Auto Scaling, and self-healing architecture mechanisms, having visibility and awareness of your AWS resources is invaluable. It can be difficult to understand what your resources within your infrastructure looks like, for example:

Cloud Academy – AWS Compute Services 2019 Reinvent Reminders

Cloud Academy – AWS Compute Services 2019 Reinvent Reminders-STM
English | Size: 306.09 MB
Category: Tutorial

It aims to provide an awareness of what each of the Compute services is used for and the benefit that they can bring to you within your organization

Cloud Academy – AWS Security Best Practices Abstract and Container Services-STM

Cloud Academy – AWS Security Best Practices Abstract and Container Services-STM
English | Size: 891.65 MB
Category: Tutorial

When implementing different AWS services and architecting them within your environments, whether it be production test or dev, do you know your security responsibilities for these services? It is very likely that you are using services from three different classifications, which each have very different boundaries for enforcing security between the customer and AWS