Repositório para o Live Coding DIO do dia 24/11/2021

• Amazon RDS
• AWS Lambda
• MySQL Workbench

• AWS Console -> Amazon RDS -> Create database -> Standard create -> MySQL -> Versão padrão -> Free Tier -> DB instance identifier [dio-live-db] -> Master username [admin] -> Master password [sua_senha_forte] -> DB instance size - padrão -> Storage - configurações padrão -> Connectivity - vpc padrão -> Publicly accessible [yes] -> VPC Security - padrão -> Database authentication [password authentication] -> Create database
• Selecionar o DB criado -> Connectivity & security -> Copiar endpoint.

• MySQL Connections -> New -> Connection name [DioLive] -> Hostname - colar o endpoint copiado no passo anterior -> Username [admin] -> Teste Connection -> Password [sua_senha]

• Security -> VPC security groups -> Acessar o SG criado -> Inbound -> Edit -> Add rule -> type [All traffic] -> Source [Anywhere] -> Save

• Selecionar a conexão criada -> Password [sua_senha_forte]

• Criar um database:

  CREATE DATABASE PERMISSIONS_DB;

• Acessar o db criado

  USE PERMISSIONS_DB;

• Criar uma tabela de usuários

  CREATE TABLE user (
    id bigint(20) NOT NULL, 
    email varchar(40) NOT NULL,
    username varchar(15) NOT NULL,
    password varchar(100) NOT NULL,
    PRIMARY KEY (id)
  );
  

• Criar uma tabela de carrinho de compras

  CREATE TABLE role (
    id bigint(20) NOT NULL,
    name varchar(60) NOT NULL, 
    PRIMARY KEY (id)
  );
  

• Criar uma tabela associativa de itens em um carrinho de compras

  CREATE TABLE ITEMS (
    cart_id INT NOT NULL,
    product_id INT NOT NULL,
    quantity DECIMAL(15,2) NOT NULL,
    FOREIGN KEY (cart_id) REFERENCES CARTS (id),
    FOREIGN KEY (product_id) REFERENCES PRODUCTS (id)
  );
  

• Descrevendo o esquema de uma tabela

  CREATE TABLE user_roles (
    user_id bigint(20) NOT NULL,
    role_id bigint(20) NOT NULL,
    FOREIGN KEY (user_id) REFERENCES user (id) ON DELETE RESTRICT ON UPDATE CASCADE,
    FOREIGN KEY (role_id) REFERENCES role (id) ON DELETE RESTRICT ON UPDATE CASCADE,
    PRIMARY KEY (user_id, role_id)
  );
  

• Inserindo dados em tabelas

  INSERT INTO user VALUES (1, 'cassiano@dio.me', 'Cassiano', 'strongpasswd');
  INSERT INTO user VALUES (2, 'joao@dio.me', 'Joao', 'strongpasswd');
  
  INSERT INTO role VALUES (3, 'ADMIN');
  INSERT INTO role VALUES (4, 'USER');
  
  INSERT INTO user_roles VALUES (1, 3);
  INSERT INTO user_roles VALUES (1, 4);
  INSERT INTO user_roles VALUES (2, 4);
  

• Selecionando todos os registros de uma tabela

  SELECT * FROM [table_name];
  

• Selecionando dados da tabela associativa

  SELECT user.id, user.email, user.username, role.id AS role_id, role.name AS role_name
  FROM user 
  JOIN user_roles on (user.id=user_roles.user_id)
  JOIN role on (role.id=user_roles.role_id);
  

• Acessar o AWS Lambda console -> Create function -> Author from scratch -> Function name [RDSQuery] -> Runtime - Python3.9 -> Create new role from AWS policy template -> Role name [RDSQueryFromLambdaRole] -> Create function

• Selecionar a função criada -> Configuration -> Permissions -> Selecionar a função criada e abrir no console do AWS IAM
• Attach policies -> Pesquisar pela policy AWSLambdaVPCAccessExecutionRole -> Attach policy

• Editor de código da função criada -> Inserir o código disponível na pasta src deste projeto

• Lambda Dashboard -> Layers -> Create layer -> Name [pymysql_layer] -> Upload a .zip file - o arquivo pyton.zip está disponível na pasta src do projeto -> Compatible architectures x86_64 -> Compatible runtimes - Python 3.9 -> Create
• Lambda Dashboard -> selecionar a função criada -> Layers -> Add a layer -> Custom layers -> selecionar o layer criado anteriormente -> Add

• Test -> New event -> Template -> Hello World -> Name [test] -> Save changes -> Test