For symmetic encryption, you can use the following:
To encrypt:
openssl aes-256-cbc -salt -a -e -in plaintext.txt -out encrypted.txt
To decrypt:
| resource "aws_lb_listener" "https" { | |
| load_balancer_arn = aws_lb.frontend.arn | |
| port = "443" | |
| protocol = "HTTPS" | |
| ssl_policy = "ELBSecurityPolicy-2016-08" | |
| certificate_arn = "TODO-CERT-ARN" | |
| default_action { | |
| type = "authenticate-oidc" | |
| authenticate_oidc { |
| resource "aws_lb_listener" "https" { | |
| load_balancer_arn = aws_lb.frontend.arn | |
| port = "443" | |
| protocol = "HTTPS" | |
| ssl_policy = "ELBSecurityPolicy-2016-08" | |
| certificate_arn = "TODO-CERT-ARN" | |
| default_action { | |
| type = "authenticate-oidc" | |
| authenticate_oidc { |
| These are some helpful resources I've found, please feel free to let me know if you have anything to share! | |
| Rust resources | |
| https://github.com/rust-lang/rustlings | |
| https://www.rust-lang.org/ | |
| https://github.com/rust-lang | |
| https://cheats.rs | |
| https://crates.io | |
| https://docs.rs | |
| https://doc.rust-lang.org/book/ |
| #! /bin/bash | |
| # https://nghttp2.org/documentation/h2load-howto.html | |
| sudo apt-get update | |
| sudo apt-get install g++ make binutils autoconf automake autotools-dev libtool pkg-config \ | |
| zlib1g-dev libcunit1-dev libssl-dev libxml2-dev libev-dev libevent-dev libjansson-dev \ | |
| libc-ares-dev libjemalloc-dev cython python3-dev python-setuptools libjemalloc-dev \ | |
| libspdylay-dev | |
| git clone https://github.com/nghttp2/nghttp2.git && cd nghttp2 | |
| autoreconf -i && automake && autoconf |
| import sys | |
| import socket | |
| """ | |
| Resolve the DNS/IP address of a given domain | |
| data returned is in the format: | |
| (name, aliaslist, addresslist) | |
| @filename resolveDNS.py | |
| @version 1.01 (python ver 2.7.3) | |
| @author LoanWolffe |
Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.
In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.
Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j
| CREATE DATABASE MyAccessLogsDB; | |
| CREATE EXTERNAL TABLE IF NOT EXISTS MyAccessLogsDB.Accesslogs( | |
| BucketOwner string, | |
| Bucket string, | |
| RequestDateTime string, | |
| RemoteIP string, | |
| Requester string, | |
| RequestID string, | |
| Operation string, | |
| Key string, |
For this configuration you can use web server you like, i decided, because i work mostly with it to use nginx.
Generally, properly configured nginx can handle up to 400K to 500K requests per second (clustered), most what i saw is 50K to 80K (non-clustered) requests per second and 30% CPU load, course, this was 2 x Intel Xeon with HyperThreading enabled, but it can work without problem on slower machines.
You must understand that this config is used in testing environment and not in production so you will need to find a way to implement most of those features best possible for your servers.