Importancia de la Infraestructura como c贸digo

1

Paso a paso para infraestructura c贸mo c贸digo

2

C贸mo desplegar infraestructura en Cloud

3

Herramientas para desplegar infraestructura como c贸digo

4

Introducci贸n y ventajas de usar Cloudformation

5

Laboratorio # 1: explorando la consola de Cloudformation

Funcionalidades y caracter铆sticas en Cloudformation

6

Anatom铆a de un template en Cloudformation

7

Clase pr谩ctica creaci贸n de un template

8

Despliegue del template en Cloudformation

9

Caracterist铆cas finales del template en Cloudformation

10

Stacks: caracter铆sticas y despliegue

11

Bonus: ejemplo de stack

12

Stack Sets: despliegues multicuenta

13

Laboratorio # 2: desplegando un Stack Set en un esquema multi-cuenta

14

Nested Stacks: composici贸n y ejemplos

15

Laboratorio # 3: creaci贸n de recursos del Stack

16

Laboratorio #3: pruebas de funcionamiento del stack

17

Laboratorio # 4: crear nuestro primer Nested Stack

18

Laboratorio #4: pruebas de funcionamiento del Nested Stack

19

Laboratorio # 5: c贸mo crear un stack de forma gr谩fica con Designer

Funciones en Cloudformation

20

Funciones intr铆nsecas: GetAtt, FindInMap, Join, Split y Select

21

Funciones intr铆nsecas: Sub, Ref y ImportValue.

22

Funciones condicionales: If, Not, And y Equals

Automatizaci贸n y despliegues de infraestructura como c贸digo

23

Importancia de la automatizaci贸n de infraestructura

24

C贸mo automatizar despliegues de infraestructura

25

Creaci贸n de pipelines para despliegue de infraestructura

26

Laboratorio #6: Estructura de repositorio para despliegue de funci贸n lambda

27

Laboratorio #6: prerequisitos para creaci贸n del pipeline

28

Laboratorio #6: despliegue de pre requisitos

29

Laboratorio #6: creaci贸n del pipeline para el despliegue de una funci贸n lambda

30

Laboratorio #6: verificaci贸n de recursos creados en el pipeline

Diagnostico de errores y seguridad en infraestructura como c贸digo.

31

Seguridad en templates

32

Troubleshooting

33

Seguridad en despliegues

34

Laboratorio # 7: identificaci贸n de errores en despliegues

Funciones lambda en Cloudformation

35

C贸mo desplegar lambda como funci贸n

36

C贸mo desplegar lambda como funci贸n serverless

37

Laboratorio # 8: puesta en producci贸n de nuestra funci贸n lambda

Conclusiones

38

Conclusiones finales

You don't have access to this class

Keep learning! Join and start boosting your career

Aprovecha el precio especial y haz tu profesi贸n a prueba de IA

Antes: $249

Currency
$209
Suscr铆bete

Termina en:

0 D铆as
13 Hrs
5 Min
54 Seg
Curso de Infraestructura Como C贸digo en AWS

Curso de Infraestructura Como C贸digo en AWS

Carlos Andr茅s Zambrano Barrera

Carlos Andr茅s Zambrano Barrera

Bonus: ejemplo de stack

11/38
Resources

How are the resources in a Stack composed?

In this article we will unravel how the various components of a Stack are organized and work in the context of AWS development. It is critical to understand the role that each resource plays, from databases to Lambda functions, and how they are integrated to form a robust and efficient system. This not only prepares you to manage stacks on AWS but extends your cloud development capabilities.

What is a metadata interface?

When implementing a stack, one of the first elements we encounter is the metadata interface. This interface is used to organize critical parameters that will be entered later in the resource configuration.

  • Parameter properties: For efficient organization, it is recommended to distinguish between DynamoDB parameters and Lambda functions.
  • Examples of parameters: Table name, primary key, and Lambda function name.
  • Purpose: Simplifies management and avoids errors by displaying only allowed items using drop-down lists.

What resources make up the Stack?

An effective Stack gathers multiple resources and here we show you some of the most common and necessary ones:

  1. DynamoDB: Highly flexible database that works with the parameters defined for its correct creation.
  2. API Gateway: Tool that handles the requests made to the databases.
  3. Lambda Function: Function that offers serverless computing allowing to execute code in response to events.

Each of these resources is configured with specific parameters that have been previously loaded, thus guaranteeing a robust construction of the service.

How are policies and roles handled?

Policies and roles are essential within a stack to define permissions and give security to each resource.

  • Lambda Role: Contains policies that allow the Lambda function to interact with different services.
  • Associated policies:
    • Permissions for S3 when extracting code.
    • Permissions to access logs in CloudWatch.
    • Permissions to query DynamoDB.

Proper role and policy mapping ensures that the Lambda function can operate frictionlessly within AWS.

Additional details on policies and permissions

In addition to basic roles and policies, it is essential to understand how the following aspects are handled:

  • Execution permissions- Defined so that a service (e.g. API Gateway) can trigger a Lambda function.
  • Specific restrictions: Determined according to the services that the Lambda function will need to query or log events.

Each resource within a stack has specific configurations that must be taken into account to ensure a secure and efficient operation of the infrastructure.

Why are nested stacks important?

Understanding nested stacks is essential for larger scale and more complex projects. They allow a large stack to be broken down into smaller, more manageable components, making it easier to maintain, upgrade and reuse certain components.

Get on the path of continuous learning and discover how these tools and frameworks can simplify your cloud projects. The AWS infrastructure adventure is just beginning!

Contributions 8

Questions 1

Sort by:

Want to see more contributions, questions and answers from the community?

una pregunta, y porque no solo trabajamos con un api gateway en vez d usar lambda?

隆Excelente explicaci贸n.!

馃槂

interesante 馃槂

interante plantilla para desplegar un stack.

Stack: No es un Stack anidado, es un solo un Stack que contiene m煤ltiples recursos. 1. Funci贸n Lambda. 2. Rol de la Funci贸n Lambda. 3. La pol铆ticas del rol de la Funci贸n Lambda. 4. Tabla de DynamoDB.
Grandiosa Explicacion y Clase, sobre Stacks .@CarlosZambrano si que sabe explicar AWS. Sus Lecciones son Muy Buenas.

Roles para asociar las politicas a la ejecucion de las lambdas