Skip to content

Instantly share code, notes, and snippets.

View ranchodeluxe's full-sized avatar

sudobangbang ranchodeluxe

  • ChopShop
  • Seattle, WA
View GitHub Profile
Estimate summary
Upfront cost,Monthly cost,Total 12 months cost,Currency
0,1649.33,19791.97,USD
,,* Includes upfront cost
Detailed Estimate
Group hierarchy,Region,Description,Service,Upfront,Monthly,First 12 months total,Currency,Configuration summary
My Estimate,US West (Oregon),,AWS Secrets Manager,0,2.01,24.12,USD,"Number of secrets (5), Average duration of each secret (30 days), Number of API calls (2000 per month)"
My Estimate,US West (Oregon),,Amazon Elastic Container Registry,0,97.16,1165.92,USD,"DT Inbound: Internet (0 TB per month), DT Outbound: Internet (1 TB per month), Amount of data stored (50 GB per month), Data transfer cost (92.16)"
@ranchodeluxe
ranchodeluxe / inter-application-comms-ecs-k8s.txt
Last active April 14, 2023 18:57
inter-application communication options in ECS versus K8s
Inter-application communication/networking options in ECS versus K8s with an emphasis on avoiding setting up load balancers:
+--------------+----------------------------------------------+-----------------+-----------------+-------------+
| FEATURE | DESCRIPTION | AWS ECS | KUBERNETES | CONCLUSION |
+--------------+----------------------------------------------+-----------------+-----------------+-------------+
| | Multiple containers per TaskDef/Pod. | | | |
| | Supports inter-container communication | supports | supports | |
| **Sidecar | via loopback on `localhost:<port>`. This | inter-container | inter-container | |
| Networking** | also means port collisions have to be | comms | comms | |
@ranchodeluxe
ranchodeluxe / gist:ed65a04862ce5f54d46cac030e2b53ed
Created March 3, 2023 13:55
`opentelemetry-bootstrap --action=install` output
3/3/2023, 5:52:48 AM f25f239053e947c88640866bb6691653
Installing collected packages: opentelemetry-instrumentation-urllib3 tf-veda-wfs3-service-dev
3/3/2023, 5:52:47 AM f25f239053e947c88640866bb6691653
Requirement already satisfied: deprecated>=1.2.6 in /opt/bitnami/python/lib/python3.10/site-packages (from opentelemetry-api~=1.12->opentelemetry-instrumentation-urllib3==0.37b0) (1.2.13) tf-veda-wfs3-service-dev
3/3/2023, 5:52:47 AM f25f239053e947c88640866bb6691653
Requirement already satisfied: setuptools>=16.0 in /opt/bitnami/python/lib/python3.10/site-packages/setuptools-63.4.3-py3.10.egg (from opentelemetry-instrumentation==0.37b0->opentelemetry-instrumentation-urllib3==0.37b0) (63.4.3) tf-veda-wfs3-service-dev
3/3/2023, 5:52:47 AM f25f239053e947c88640866bb6691653
Requirement already satisfied: opentelemetry-instrumentation==0.37b0 in /opt/bitnami/python/lib/python3.10/site-packages (from opentelemetry-instrumentation-urllib3==0.37b0) (0.37b0) tf-veda-wfs3-service-dev
3/3/2023, 5:52:47 AM f25f239053e94
@ranchodeluxe
ranchodeluxe / addons_example.yaml
Created February 23, 2023 16:54
example of cluster config CNI addon policies
addons:
- name: vpc-cni
version: 1.7.5 # not sure what version we are currently at b/c I don't have any k8 RBAC access
attachPolicyARNs:
- arn:aws:iam::aws:policy/AmazonEKS_CNI_Policy
serviceAccountRoleARN: arn:aws:iam::aws:policy/<whatever>
tags:
team: eks
attachPolicy:
Statement: # just showing what should currenlty exist for this role
@ranchodeluxe
ranchodeluxe / gist:9823cd32430ad64253491320aab34762
Created June 23, 2016 09:54
elasticsearch /_nodes/stats 06/23/2016
{
"cluster_name":"elasticsearch",
"nodes":{
"EYc9thF9ROy-pSMMrX4UoQ":{
"timestamp":1466627259673,
"name":"MN-E (Ultraverse)",
"transport_address":"127.0.0.1:9300",
"host":"127.0.0.1",
"ip":[
"127.0.0.1:9300",
@ranchodeluxe
ranchodeluxe / gist:8d708658c653f9f3966fa3a4deddf62f
Created June 21, 2016 12:50
elasticsearch /_nodes/stats output June 18th
{
"cluster_name":"elasticsearch",
"nodes":{
"Rg-xqnDESdmQnqkuTgHbhw":{
"timestamp":1466461514864,
"name":"Snowfall",
"transport_address":"127.0.0.1:9300",
"host":"127.0.0.1",
"ip":[
"127.0.0.1:9300",
{
"cluster_name" : "elasticsearch",
"nodes" : {
"KtAsV0qoTJe4ES521uQ2GQ" : {
"timestamp" : 1466017122170,
"name" : "Deadly Ernest",
"transport_address" : "127.0.0.1:9300",
"host" : "127.0.0.1",
"ip" : [ "127.0.0.1:9300", "NONE" ],
"indices" : {
{
"id": 1,
"title": "GSMeasurments",
"originalTitle": "GSMeasurments",
"tags": [],
"style": "dark",
"timezone": "browser",
"editable": true,
"hideControls": false,
"sharedCrosshair": false,
@ranchodeluxe
ranchodeluxe / test_dateparser_tzstring_conversions.py
Last active February 9, 2016 19:53
An interesting note about how dateparser parses date strings with tzinfo in them and then an expected way to do it
import re
import pytz
from datetime import datetime
import dateparser
import pytest
def expected_tz_conversion(datetime_obj, pytz_tzinfo_offset):
# keep the day and time, just give it tzinfo
return pytz_tzinfo_offset.localize(datetime_obj)

git pull origin dev

remote: Counting objects: 80, done.
remote: Compressing objects: 100% (65/65), done.
remote: Total 80 (delta 34), reused 11 (delta 11), pack-reused 4
Unpacking objects: 100% (80/80), done.
From https://github.com/Cadasta/ckanext-project
 * branch            dev        -> FETCH_HEAD
Updating 4b73067..b66b3db
Fast-forward