First thoughts after AWS Certified Security - Specialty BETA exam
Last week I made an attempt at passing one of the new AWS Specialty exams - Security.
Posts on AWS.
Last week I made an attempt at passing one of the new AWS Specialty exams - Security.
Combination of AWS API Gateway and Lambda functions is a flag example of every “serverless infrastructure”. When deploying API Gateway with CloudFormation there are two different ways you can define your API: via Swagger template or by directly defining your methods in CloudFormation template.
AWS Lambda and API Gateway are becoming synonymous with “serverless infrastructure” and getting more and more popular.
To deploy them in repeatable way, one of the tools I recommend is CloudFormation - see deploying API Gateway and
Lambda with CloudFormation for the basic
setup. There are many ways you can define
your API and your Lambda, but when connecting the two with CloudFormation there’s usually something that many people
miss, and only notice when {"message": "Internal server error"} is thrown from their API Gateway endpoint.
If you’ve tried running Packer with CentOS on AWS, you probably noticed this:
sudo: sorry, you must have a tty to run sudoI’m not talking about launching an EC2 instance, uploading the zip with WordPress and going through the installer. I’m talking about immutable infrastructure, scalable, self-healing setup of WordPress within AWS.