Short Notes on AWS - Revision history

Admin: /* AWS Chalice */

2020-05-20T16:56:34Z

‎AWS Chalice

Admin: /* AWS Chalice */

2020-04-20T11:10:14Z

‎AWS Chalice

Admin: /* Building a Python Layer */

2019-12-26T14:03:41Z

‎Building a Python Layer

Admin: /* AWS Chalice */

2019-11-18T11:53:59Z

‎AWS Chalice

Admin: /* Building a Python Layer */

2019-11-17T12:25:54Z

‎Building a Python Layer

Admin at 19:41, 16 November 2019

2019-11-16T19:41:24Z

Admin at 17:37, 16 November 2019

2019-11-16T17:37:40Z

Admin: /* AWS Lambda (Py) Notes */

2019-11-05T09:08:27Z

‎AWS Lambda (Py) Notes

Admin: /* AWS Lambda (Py) Notes */

2019-11-05T09:06:34Z

‎AWS Lambda (Py) Notes

Admin: /* AWS Lambda (Py) Notes */

2019-11-05T09:03:52Z

‎AWS Lambda (Py) Notes

← Older revision		Revision as of 16:56, 20 May 2020
Line 111:		Line 111:

	On the frontend side, you need to make sure API Gateway does not mess you up - you need to specify <tt>Accept</tt> header of the binary type (not necessarily of the same type as the one returned from Chalice). If you specify <tt>/</tt> as the accepted type, you'll receive base64 encoded data.		On the frontend side, you need to make sure API Gateway does not mess you up - you need to specify <tt>Accept</tt> header of the binary type (not necessarily of the same type as the one returned from Chalice). If you specify <tt>/</tt> as the accepted type, you'll receive base64 encoded data.
		+
		+	=== Getting 403 on a Route ===
		+
		+	Apart of actual 403 response, Chalice will return 403 on a route that does not have the <tt>/</tt> prefix:
		+
		+	<pre>
		+	# this will return 403 :S
		+	@app.route('v1/test')
		+	def v1_test():
		+	return {}
		+
		+	# this will work :)
		+	@app.route('/v1/test')
		+	def v1_test():
		+	return {}
		+	</pre>

	== Building a Python Layer ==		== Building a Python Layer ==

@@ Line 93: / Line 93: @@
+   }
 }</pre>
 == Building a Python Layer ==

@@ Line 110: / Line 110: @@
 $ docker-compose up
-Recreating layer-docker_amzlinux_1 ... done
+Creating network "layer-example_default" with the default driver
-Attaching to layer-docker_amzlinux_1
+Pulling amzlinux (amazonlinux:)...
 $ docker ps
 CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES
-a5107c00ed35        amazonlinux         "sleep infinity"    10 seconds ago      Up 8 seconds                            '''layer-docker_amzlinux_1'''
+a5107c00ed35        amazonlinux         "sleep infinity"    10 seconds ago      Up 8 seconds                            '''layer-example_amzlinux_1'''
-$ docker exec -it layer-docker_amzlinux_1 /bin/bash
+$ docker exec -it layer-example_amzlinux_1 /bin/bash
 bash-4.2# yum -y update

@@ Line 58: / Line 58: @@
 == AWS Chalice ==
-TBP
+Prepare your virtualenv, and install boto3 and Chalice in it.
 == Building a Python Layer ==

← Older revision		Revision as of 12:25, 17 November 2019
Line 107:		Line 107:

	bash-4.2# cd sqlalchemy-layer/		bash-4.2# cd sqlalchemy-layer/
−	bash-4.2# zip -r aws-sqlalchemy-layer.zip python/</pre>	+	bash-4.2# zip -r aws-sqlalchemy-layer.zip python/ -x \*.pyc</pre>
		+
		+	Now you can upload the <tt>aws-sqlalchemy-layer.zip</tt> as a Layer through AWS console.

@@ Line 48: / Line 48: @@
 * POST/PUT body in <tt>event["body"]</tt>
 ** ''note'': stored as string, you have to <tt>json.loads()</tt> or similar
 == AWS Chalice ==

← Older revision		Revision as of 17:37, 16 November 2019
Line 48:		Line 48:
	* POST/PUT body in <tt>event["body"]</tt>		* POST/PUT body in <tt>event["body"]</tt>
	** ''note'': stored as string, you have to <tt>json.loads()</tt> or similar		** ''note'': stored as string, you have to <tt>json.loads()</tt> or similar
		+
		+	== AWS Chalice ==
		+
		+	TBP
		+
		+	== Building a Python Layer ==
		+
		+	We'll be using docker Amazon Linux image.
		+
		+	Below, commands starting with <tt>$</tt> are run on your machine, while those starting with <tt>bash-4.2#</tt> are run within the docker container.
		+
		+	<pre>$ cat docker-compose.yaml
		+	version: "3"
		+	services:
		+	amzlinux:
		+	image: "amazonlinux"
		+	command: "sleep infinity"
		+	volumes:
		+	- ./:/host
		+
		+	$ docker-compose up
		+	Recreating layer-docker_amzlinux_1 ... done
		+	Attaching to layer-docker_amzlinux_1
		+
		+	$ docker ps
		+	CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
		+	a5107c00ed35 amazonlinux "sleep infinity" 10 seconds ago Up 8 seconds '''layer-docker_amzlinux_1'''
		+
		+	$ docker exec -it layer-docker_amzlinux_1 /bin/bash
		+
		+	bash-4.2# yum -y update
		+	>>> bash-4.2# yum -y groupinstall "Development Tools"
		+	>>> bash-4.2# yum -y install Cython
		+
		+	bash-4.2# yum -y install python3-pip.noarch zip
		+	[...]
		+	Installed:
		+	python3-pip.noarch 0:9.0.3-1.amzn2.0.1
		+
		+	bash-4.2# cd /host/
		+
		+	bash-4.2# mkdir -p sqlalchemy-layer/python
		+
		+	bash-4.2# pip3 install sqlalchemy -t sqlalchemy-layer/python/
		+	[...]
		+	Successfully installed sqlalchemy-1.3.11
		+
		+	bash-4.2# pip3 install psycopg2-binary -t sqlalchemy-layer/python/
		+	[...]
		+	Successfully installed psycopg2-binary-2.8.4
		+
		+	bash-4.2# cd sqlalchemy-layer/
		+	bash-4.2# zip -r aws-sqlalchemy-layer.zip python/</pre>

@@ Line 45: / Line 45: @@
 ** ''note'': parameters are stored in arrays, the lambda's parser correctly presumes that there may be multiple values; e.g. <tt>event["multiValueQueryStringParameters"] = {"param": ["value"]}</tt>
 * path parameters in <tt>event["pathParameters"]</tt>
 * POST/PUT body in <tt>event["body"]</tt>
 ** ''note'': stored as string, you have to <tt>json.loads()</tt> or similar

← Older revision		Revision as of 09:06, 5 November 2019
Line 46:		Line 46:
	* path parameters in <tt>event["pathParameters"]</tt>		* path parameters in <tt>event["pathParameters"]</tt>
	* POST/PUT body in <tt>event["body"]</tt>		* POST/PUT body in <tt>event["body"]</tt>
		+	** ''note'': stored as string, you have to <tt>json.loads()</tt> or similar