| #!/bin/bash | |
| # Source: https://docs.aws.amazon.com/general/latest/gr/sigv4-signed-request-examples.html | |
| [[ -n "${AWS_ACCESS_KEY_ID}" ]] || { echo "AWS_ACCESS_KEY_ID required" >&2; exit 1; } | |
| [[ -n "${AWS_SECRET_ACCESS_KEY}" ]] || { echo "AWS_SECRET_ACCESS_KEY required" >&2; exit 1; } | |
| readonly parameterName="SlawekTestParam" | |
| readonly method="POST" |
| # Ansible playbook AWS - install docker | |
| --- | |
| - name: "AWS - Install docker" | |
| hosts: aws-docker-vms | |
| become: yes | |
| tasks: | |
| - name: Update all packages | |
| yum: | |
| name: '*' | |
| state: latest |
| // In JavaScript, constructors can only be synchronous right now. This makes sense | |
| // from the point of view that a constructor is a function that returns a newly | |
| // initialized object. | |
| // | |
| // On the other hand, it would sometimes be very handy, if one could have async | |
| // constructors, e.g. when a class represents a database connection, and it is | |
| // desired to establish the connection when you create a new instance. | |
| // | |
| // I know that there have been discussions on this on StackOverflow & co., but | |
| // the so-far mentioned counter arguments (such as: doesn't work as expected |
Snake is a fun game to make as it doesn't require a lot of code (less than 100 lines with all comments removed). This is a basic implementation of the snake game, but it's missing a few things intentionally and they're left as further exploration for the reader.
| #python3 | |
| def hook(t): | |
| def inner(bytes_amount): | |
| t.update(bytes_amount) | |
| return inner | |
| BUCKET_NAME = 'your_s3_bucket_name' | |
| FILE_NAME = 'your_s3_file_name' | |
| s3 = boto3.resource('s3') |
| #!/usr/bin/env python | |
| ############################################################################### | |
| # This script downloads an object from AWS S3. If the object was encrypted, | |
| # it will be decrypted on the client side using KMS envelope encryption. | |
| # | |
| # Envelope encryption fetches a data key from KMS and uses it to encrypt the | |
| # file. The encrypted file is uploaded to an S3 bucket along with an encrypted | |
| # version of the data key (it's encrypted with a KMS master key). You must | |
| # have access to the KMS master key to decrypt the data key and file. To | |
| # decrypt, the file is downloaded to the client, the encrypted data key is |
| # Using a lambda function | |
| print(list(map(lambda i: "Fizz"*(i%3==0)+"Buzz"*(i%5==0) or str(i), range(1,101)))) | |
| # Using a for loop | |
| for i in range(1, 101): print("Fizz"*(i%3==0)+"Buzz"*(i%5==0) or str(i)) |
| require "aws-sdk" | |
| require "dotenv" | |
| require "reduce" | |
| Dotenv.load | |
| def local_dir; './_site'; end | |
| def access_key; ENV['AWS_ACCESS_KEY']; end | |
| def secret_key; ENV['AWS_SECRET_KEY']; end |
Run this from an ec2 instance in the us-west-1 region.
It will create two queues and feed messages into the first queue with a timestamp, this message will then be read and the difference between the message timestamp and the current time computed and pushed into a response queue. Reading these times will give you the latency between publishing to a queue and receiving the message.
