Query values from SSM when deployed, by placing an SSM ARN as the environment variable
I wanted to query secrets from SSM at runtime, to laod them into a pydantic.BaseSettings settings object, but still be able to pass standard values during development (and I guess, if I want, in prod).
I've done a couple of similar implementations before, but they have always felt clunky and involved altering the object after instantiation, or hard coding which values to take out of SSM.
| from threading import BoundedSemaphore | |
| from concurrent.futures import ProcessPoolExecutor | |
| class MaxQueuePool: | |
| """This Class wraps a concurrent.futures.Executor | |
| limiting the size of its task queue. | |
| If `max_queue_size` tasks are submitted, the next call to submit will block | |
| until a previously submitted one is completed. |
| from io import BytesIO | |
| import gzip | |
| import shutil | |
| def upload_gzipped(bucket, key, fp, compressed_fp=None, content_type='text/plain'): | |
| """Compress and upload the contents from fp to S3. | |
| If compressed_fp is None, the compression is performed in memory. | |
| """ |
| #!/usr/local/bin/python3 | |
| import subprocess | |
| import shlex | |
| import json | |
| # function to find the resolution of the input video file | |
| def findVideoMetada(pathToInputVideo): | |
| cmd = "ffprobe -v quiet -print_format json -show_streams" | |
| args = shlex.split(cmd) | |
| args.append(pathToInputVideo) |
| # vim: set fileencoding=utf-8 : | |
| # | |
| # How to store and retrieve gzip-compressed objects in AWS S3 | |
| ########################################################################### | |
| # | |
| # Copyright 2015 Vince Veselosky and contributors | |
| # | |
| # Licensed under the Apache License, Version 2.0 (the "License"); | |
| # you may not use this file except in compliance with the License. | |
| # You may obtain a copy of the License at |
| # www.fduran.com | |
| # exclude a process from being killed by oom killer | |
| echo -17 > /proc/$PID/oom_adj | |
| # The possible values of oom_adj range from -17 to +15. The higher the score, more likely the associated process is to be killed by OOM-killer: https://lwn.net/Articles/317814/ |
