AWS

Introduction When working at any software, as a developer, you need to know what is going to be delivered to production, for our application code base we use things like git to track changes, keep a history, review and revert if needed. But when we talk about infrastructure resources in our cloud provider, this task is not easy, sometimes because the provider doesn’t have a good API or the tools doesn’t give us what we need, other times is because it is too much complicated, and we are trying to solve something simple as quick as possible, so we do it manually....

Installing the cdk CLI tool with npm $ npm install -g aws-cdk Checking if you have installed it correctly: $ cdk --version 1.94.0 (build 2c1c0eb) Remember that the version number could be different. Setup project In any folder execute the command below: $ cdk init app --language=python ... ✅ All done! This command creates the initial structure of our CDK project, it also outputs others commands, including the one to synthesize our application....

Installing aws CLI tool from source: git clone --depth=1 https://github.com/aws/aws-cli.git cd ./aws-cli pip install . Configuring access keys: $ aws configure AWS Access Key ID: your-access-key-id AWS Secret Access Key: your-secret-access-key Default region name: eu-west-1 Default output format: json

Before we start If you check for alternatives that we have available for SQL and NoSQL database, both of them have some problems. For SQL databases the problem is scalability, you can of course use them for a lot of applications, they will give you flexibility when you want to retrieve your records, but when you grow, starting to have hundreds of terabytes of data, you will start to see problems related to performance, and that will happen with all SQL database because all of them were created for storage optimization and not compute optimization....