| # -------------------------------------------------------------------- | |
| # Copyright (c) 2019 LINKIT, The Netherlands. All Rights Reserved. | |
| # Author(s): Anthony Potappel | |
| # | |
| # This software may be modified and distributed under the terms of the | |
| # MIT license. See the LICENSE file for details. | |
| # -------------------------------------------------------------------- | |
| # If you see pwd_unknown showing up, this is why. Re-calibrate your system. | |
| PWD ?= pwd_unknown |
| #!/bin/bash | |
| TOKEN="xxxxxxxxxxxxxxxxxxx" | |
| ZONE_ID=2222222222222222222222222 | |
| # EMAIL=me@gmail.com | |
| # KEY=11111111111111111111111111 | |
| # Replace with | |
| # -H "X-Auth-Email: ${EMAIL}" \ | |
| # -H "X-Auth-Key: ${KEY}" \ |
The default formula use by AWS RDS to calculate the max_connections parameter is: LEAST({DBInstanceClassMemory/9531392},5000)
But It's hard to find the exact value of DBInstanceClassMemory.
So, here are the values I got when I ran the SQL commmand: show max_connections; in some RDS instances:
| Instance type | RAM (GB) | max_connections |
|---|---|---|
| db.t2.small | 2 | 198 |
| db.t2.medium | 4 | 413 |
Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.
| #!/bin/bash | |
| # | |
| # this script will attempt to detect any ephemeral drives on an EC2 node and create a RAID-0 stripe | |
| # mounted at /mnt. It should be run early on the first boot of the system. | |
| # | |
| # Beware, This script is NOT fully idempotent. | |
| # | |
| METADATA_URL_BASE="http://169.254.169.254/2012-01-12" |
| [program:lss] | |
| process_name=Shipper | |
| command=java -jar /usr/local/logstash/bin/logstash-1.1.9-monolithic.jar agent --config /usr/local/logstash/conf/shipper.conf --log /usr/local/logstash/log/shipper.log | |
| user=logstash | |
| startretries=3 | |
| redirect_stderr=true | |
| std_out_logfile=NONE | |
| startsecs=3 | |
| environment=HOME="/usr/local/logstash/" |
| ! -------------------------------------------------------------------------------- | |
| ! This example configuration shows what WE did to get Amazon VPC working with our | |
| ! ASAs. We use version 8.3(1). This config has not been reviewed or otherwise | |
| ! blessed in any way by anyone at Amazon. YMMV. | |
| ! | |
| ! It differs from Amazon's supplied config by using two different sets of | |
| ! crypto maps and ACLs, so it brings both tunnels up simultaneously. | |
| ! | |
| ! For the purposes of the example, the physical datacenter network is 172.16.1.0/24 | |
| ! and the VPC is 10.0.0.0/16. |
| Original header used now: | |
| ### File managed with puppet ### | |
| ## Served by: '<%= scope.lookupvar('::servername') %>' | |
| ## Module: '<%= scope.to_hash['module_name'] %>' | |
| ## Template source: 'MODULES<%= template_source.gsub(Regexp.new("^#{Puppet::Node::Environment.current[:modulepath].gsub(':','|')}"),"") %>' | |
| Problem: When using puppet apply with relative modulepath, the information can be wrong or messy. | |
| Alternative 1: |
| #!/bin/bash | |
| if [ -z "$1" ]; then | |
| echo "Usage: sudo $0 /dev/sdh1" | |
| exit 1; | |
| fi | |
| dd if=$1 of=/dev/null & pid=$! | |
| while true; do | |
| ps -p$pid --no-heading || break; | |
| echo "-- $(date) ------------------"; |
| require 'rubygems' | |
| require 'chef/encrypted_data_bag_item' | |
| secret = Chef::EncryptedDataBagItem.load_secret('data_bag_key') | |
| data = {"id" => "mysql", "root" => "some secret password"} | |
| encrypted_data = Chef::EncryptedDataBagItem.encrypt_data_bag_item(data, secret) | |
| FileUtils.mkpath('data_bags/passwords') | |
| File.open('data_bags/passwords/mysql.json', 'w') do |f| | |
| f.print encrypted_data.to_json |
