jeremyyeo

Overriding dbt Cloud default database / schema on CI runs

-!  🚨                                          WARNING                                          🚨  !-
You probably do not want to do this because dbt Cloud will not be able to drop the relevant schema 
upon PR merge / close so you will end up with clutter if you are not on top of this.

The following is the default behaviour of [dbt Cloud CI runs][1] when:

takemikami

terraform config for MWAA

Support Version

https://github.com/hashicorp/terraform-provider-aws/releases/tag/v3.36.0

Plan & Apply

terraform plan -var-file=vars.tfvars
terraform apply -var-file=vars.tfvars

ThePredators

⭐ Setup Mobile Development Environment

⚠️ The following configuration has been tested on Intel, M1 & M2 Ships ⚠️

Pre-requisit :

If you have any issues with macOS, or need anything related to it check this documentation

Install Xcode Command Line tools :

bogue1979

# SNS topic lifecycle hooks are sent to
resource "aws_sns_topic" "nomad_graceful_termination_topic" {
  name = "${local.instance_prefix}-nomad_graceful_termination_topic"
}
resource "aws_sns_topic_policy" "nomad_graceful_termination_topic" {
  arn = aws_sns_topic.nomad_graceful_termination_topic.arn
  policy = data.aws_iam_policy_document.nomad_graceful_termination_topic_policy.json
}
data "aws_iam_policy_document" "nomad_graceful_termination_topic_policy" {
  policy_id = "__default_policy_ID"

jehptes

# Create an IAM role

resource "aws_iam_role" "glue" {
  name = "AWSGlueServiceRoleDefault"

  assume_role_policy = <<EOF
{
  "Version": "2012-10-17",
  "Statement": [
    {

trodemaster

resource "vault_jwt_auth_backend" "oidc" {
  description        = "vault + OKTA + oidc"
  path               = "oidc"
  type               = "oidc"
  oidc_discovery_url = "${var.OKTA_URL}"
  oidc_client_id     = "${var.OKTA_CLIENT_ID}"
  oidc_client_secret = "${var.OKTA_CLIENT_SECRET}"
  bound_issuer       = "${var.OKTA_URL}"
  default_role       = "oidc"

nicolasdao

AWS SERVERLESS RECIPES

Table of contents

• Lambda
  • Scheduled Lambda
  • Invoking a Lambda from another Lambda
  • Websocket
  • Triggered by SQS > - VPC config

arodd

Lab 1: Lab Setup

Duration: 10 minutes

Each student should have received the lab workstation log in information from the instructor. This lab ensures that everyone can connect to the workstation, and verify that a Vault server is running so that vault commands can run against it.

• Task 1: Connect to the Student Workstation
• Task 2: Getting Help
• Task 3: Enable Audit Logging
• Task 4: Access Vault UI

greenbrian

#!/bin/bash

## The following command starts Vault in development mode
## specifiying a root token value of 'root'
##
# VAULT_UI=true vault server -dev -dev-root-token-id="root"

## Login with root token
## Good for demo mode, should only be used on production cluster
## during initial configuration

afloesch

Terraforming API Gateway to SQS queue

Example of a bare-minimum terraform script to setup an API Gateway endpoint that takes records and puts them into an SQS queue.

SQS

Start by creating the SQS queue.

resource "aws_sqs_queue" "queue" {