arthuralvim

Preface

In general, AWS services can be accessed using

1. AWS web interface,
2. API libraries in a programming language, such as boto3 for Python 3,
3. AWS command-line interface, i.e. awscli.

I opted for the API library since it is

arthuralvim

# coding:utf-8

from elasticsearch import Elasticsearch
import json

# Define config
host = "127.0.0.1"
port = 9200
timeout = 1000
index = "index"

arthuralvim

# -*- coding: utf-8 -*-

from flask import Flask, request, render_template, current_app
from flask_wtf import Form
from wtforms.validators import DataRequired
from wtforms import SelectField, SelectMultipleField, SubmitField


app = Flask(__name__)

arthuralvim

# echo '{}' > event.json; mkdir -p libs; pip install attrs envattrs -t libs; \
# export YOUR_PREFIX_SLACK_CHANNEL=your_project-staging; \
# export YOUR_PREFIX_S3_BUCKET=pyconapac-bucket; \
# export YOUR_PREFIX_THRESHOLD=50; \
# python-lambda-local -l libs/ -f handler -t 5 lambda_pyconapac.py event.json

from typing import Dict

import attr
import envattrs

arthuralvim

event example

TASK_NAME=${1:-'export_logs'}
FROM=${2:-'2017-12-24 12:00'}
TO=${3:-'2017-12-24 12:05'}
cat <<-EOF > event.json
{
    "taskName": "$TASK_NAME",
    "fromTime": `gdate --date="$FROM" +%s%3N`,
 "toTime": `gdate --date="$TO" +%s%3N`

arthuralvim

AWS Batch

• Ref. https://docs.aws.amazon.com/batch/latest/userguide/what-is-batch.html

The goal of this document is submitting a job to AWS Batch and confirming the result in CloudWatch Logs.

Since I've worked on ap-northeast-1 region, The following examples includes this region name.

Setting Up with AWS Batch

• Ref. https://docs.aws.amazon.com/batch/latest/userguide/get-set-up-for-aws-batch.html

arthuralvim

import contextlib
import OpenSSL.crypto
import os
import requests
import ssl
import tempfile

@contextlib.contextmanager
def pfx_to_pem(pfx_path, pfx_password):
    ''' Decrypts the .pfx file to be used with requests. '''

arthuralvim

Using py.test is great and the support for test fixtures is pretty awesome. However, in order to share your fixtures across your entire module, py.test suggests you define all your fixtures within one single conftest.py file. This is impractical if you have a large quantity of fixtures -- for better organization and readibility, you would much rather define your fixtures across multiple, well-named files. But how do you do that? ...No one on the internet seemed to know.

Turns out, however, you can define fixtures in individual files like this:

tests/fixtures/add.py

import pytest

@pytest.fixture

arthuralvim

AWS CLI Cheatsheet

http://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html https://www.youtube.com/watch?v=_wiGpBQGCjU

Setup

arthuralvim

from django.core.management.base import BaseCommand, CommandError
from django.core import serializers

from optparse import make_option

class Command(BaseCommand):   
    """ 
        Generate a fixture file for a specific model.
        Useage: ./manage.py generate_fixtures app.models.MyModel --file=MyModelsOutputFile.json                                                                                              
    """