Here are the seven best practices for getting started on AWS. Learn more about the key aspects you should focus on when getting started with the AWS Cloud.
43. Access everything via CLI, API or Console
Use one of 13 fully supported
SDKs to create or make use of existing AWS
resources within your own code
Leverage a broad ecosystem of open source,
free and commercially licensed tools to work
with AWS Services
Achieve the highest levels of automation to
support continuous deployment, define your
infrastructure-as-code or automate your
development, operations or DevOps processes
Find out more at: aws.amazon.com/developers/getting-started/
Everything is Programmable
Go >> C++ >>
AWS
Mobile
SDK
AWS IoT Device SDK
* Mention prior episode and other series
* Materials Download
* Questions + our SA team
* Social Media
* Feedback & Rate at the end
Smart
Specific - set clear goals, target a specific project or goal
Measurable - understand when you will claim success and use metrics
Achievable - specify goals that are reachable
Realistic - make a goal one that can realistically be achieved, given available resources.
Time bound - understand the timescales, how long will you give yourself to achieve the goal?
An AWS account is 1. An Administrative Boundary 2. Resource boundary 3. Billing Entity
Before posting code into git hub
You can use groups to limit what people can do and roles to limit what instances can do
Give very different access to administrators than developers
For example and instance can only access data in a certain S3 bucket
JSON – Java Script Object Notation is a lightweight data-interchange format.
Because you’re building systems on top of the AWS cloud infrastructure, the security responsibilities will be shared: AWS has secured the underlying infrastructure and you must secure anything you put on the infrastructure or connect to the infrastructure. The amount of security configuration work you have to do varies depending on how sensitive your data is and which services you select.
For IaaS services like Amazon EC2 and Amazon S3, you have more control and therefore more configuration work to do. For EC2 instances, you’re responsible for patching the guest OS on the instances as well as any software you install on them, configuring the security group (firewall) that allows outside access to your instances, and setting up any VPC subnets that the instances reside within, etc. For Amazon S3, you must set the access control policies for each of your storage buckets, set up encryption options for the stored data, and specify backup and archiving preferences.
For PaaS services like Amazon RDS or RedShift or WorkSpaces, you have less security configuring to do. For these services, you don’t have to worry about launching and maintaining instances or patching the guest OS or applications—AWS handles that for you. For these managed services, backups are performed automatically, firewalls are configured, and databases are replicated.
However, there are certain security features—such as individual IAM user accounts and credentials, HTTPS for data transmissions, and user activity logging—that you should configure no matter which AWS services you use.
Our goal, and what our customers tell us they see, is that this ratio is inverted after moving to AWS. When you move your infrastructure to the cloud, this changes things drastically. Only 30% of your time should be spent architecting for the cloud and configuring your assets. This gives you 70% of your time to focus on your business. Project teams are free to add value to the business and it's customers, to innovate more quickly, and to deliver products to market quickly as well.
AWS Elastic Beanstalk is an application container for deploying and managing applications
AWS OpsWorks is a DevOps platform for managing applications of any scale or complexity on the AWS cloud
AWS CloudFormation lets you create and update a collection of related AWS resources in a predictable fashion
Code Commit- A secure, highly scalable, managed source control service that hosts private Git repositories. Eliminates the need to operate your own source control system or worry about scaling its infrastructure.
Code Build Allows customers to build and compile their code using a native AWS managed build service
Code Deploy is a Service that deploys your released code to a "fleet" of EC2 instances
Code pipeline A continuous delivery and release automation service that aids smooth deployments.You can design your development workflow for checking in code, building the code, deploying your application into staging, testing it, and releasing it to production. Similar to Jenkins or Bamboo
AWS Lambda is a serverless compute service that runs your code in response to events and automatically manages the underlying compute resources for you.
AWS Step Functions is a web service that enables you to coordinate the components of distributed applications and microservices using visual workflows.
AWS X-Ray provides an end-to-end view of requests as they travel through your application, and shows a map of your application’s underlying components.To analyze and debug.