##Using Let's Encrypt certificates with AWS API Gateway
Before starting off with API Gateway set up it's worth mentioning that certificate configuration for this particular service is so far isn't well integrated, therefore different from other AWS services. Despite it using CloudFrount to serve on custom domains it won't let you customize distributions it creates, however all the limitations of CloudFront naturally apply to API Gateway. The most important in this case is the size of the key, which is limited by 2048 bit. Many tutorials provide ready to use terminal commands that have the key size preset at 4096 bit for the sake of better security. This won't work with API Gateway and you'll get an error message about certificate's validity or incorrect chain which won't suggest you the real cause of the issue. Another consideration is that to add a custom domain to API Gateway you have to have a certif
| [user] | |
| name = Ian Webster | |
| email = ian@planetaryresources.com | |
| [diff] | |
| tool = vimdiff | |
| [color] | |
| ui = auto | |
| diff = auto |
| #!/usr/bin/env ruby | |
| require 'socket' | |
| # This script runs every minute, captures stats about redis | |
| # and forwards them to graphite as counter values. | |
| # Graphite/carbon settings | |
| GRAPHITE_HOST="graphite.intra.local.ch" | |
| GRAPHITE_PORT=8125 |
How to use Pelican on GitHub Pages 
Author: Josef Jezek
sudo apt-get install python-setuptools
| /******************************************************************************* | |
| * | |
| * FR_EXP.c | |
| * User Experience Code for the MSP-EXP430FR5739 | |
| * C Functions File | |
| * | |
| * Copyright (C) 2010 Texas Instruments Incorporated - http://www.ti.com/ | |
| * | |
| * | |
| * Redistribution and use in source and binary forms, with or without |