= AWS =
Amazon Web Services

Lambda Java samples:
 * https://docs.aws.amazon.com/lambda/latest/dg/lambda-samples.html
  * https://github.com/awsdocs/aws-lambda-developer-guide/tree/main/sample-apps/java-basic/

== User credentials ==
 * https://docs.aws.amazon.com/general/latest/gr/root-vs-iam.html
 * https://docs.aws.amazon.com/general/latest/gr/aws-access-keys-best-practices.html
 * https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html

Instead of sharing the credentials of the AWS account root user, create individual IAM users, granting each user only the permissions they require.

Follow the best practice of using the root user only to create your first IAM user.

There are two types of credentials:
 * Root user credentials,  allow full access to all resources in the AWS account.
 * IAM credentials, control access to AWS services and resources for users in your AWS account

== Serverless blog web application architecture ==
 * https://github.com/aws-samples/lambda-refarch-webapp
 * https://s3.amazonaws.com/aws-lambda-serverless-web-refarch/RefArch_BlogApp_Serverless.png
  * Amazon Route 53 (routes to specific places based on region)
  * Amazon CloudFront (deliver static content per region hosted inside S3)
  * Amazon Simple Storage Service (S3)
  * Amazon Cognito (Authentication and authorization)
  * Amazon API Gateway (routes requests to backend logic)
  * AWS Lambda (backend business logic)
  * AWS DynamoDB (managed DB)
  * AWS Identity and Access Management (IAM) - web service to control access to AWS resources

== IPv6 info ==
 * https://aws.amazon.com/blogs/networking-and-content-delivery/introducing-ipv6-only-subnets-and-ec2-instances/
 * https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-instance-addressing.html#amazon-dns
 * https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-instance-addressing.html#working-with-ipv6-addresses