In modern DevOps, cloud infrastructures, especially platforms like AWS, GCP, and Azure, play an integral role. These platforms offer robust APIs that enable developers to provision and manage resources dynamically, streamlining operations and costs.

Why use Cloud APIs?

• Automation: Scripted provisioning removes manual errors.

• Scalability: Dynamically adapt to demand.

• Flexibility: Customise per requirements.

• Integration: Blend with CI/CD pipelines and other DevOps tools.

Interacting with Cloud APIs

1. Setting Up:

Before making any requests to a cloud provider’s API, you need to ensure you have the correct permissions and authentication setup.

• Obtaining API Keys or Authentication Tokens:

  • Cloud providers typically use a combination of access keys, secret keys, or tokens for API authentication.

  • For AWS: You'll set up IAM (Identity and Access Management) users and grant them permissions. Once set up, you'll be provided with an Access Key ID and Secret Access Key.

2. Choosing an SDK:

3. Making Requests:

Here, you communicate with the cloud service, requesting various operations.

• Provisioning: This refers to the allocation or reservation of cloud resources. E.g., Creating an EC2 instance or reserving a new RDS (Relational Database Service) instance in AWS.

• Configuration: After provisioning, resources might need additional settings or adjustments. E.g., Adjusting the security group of an EC2 instance or updating the database version in RDS.

• Monitoring: Cloud services often provide metrics, logs, or alerts to monitor the health and performance of your resources.

4. Handling Responses:

Every API call receives a response. Handling these responses correctly is crucial.

Success Responses: Usually, a 2XX HTTP status code (like 200 OK). The response body might contain the details of the newly created resource, confirmation of the action taken, or data you requested.

Error Responses: Cloud APIs can respond with errors for various reasons – rate limits, failed authentication, unavailable resources, etc. For instance, AWS provides detailed error messages within an XML tag in the response. Knowing how to parse and react to these messages is essential. Handling AWS Error Messages

This week is the first build sprint of your in-house project build.

Work through your sprint backlog, assigning user stories to members of the team.

There are no defined spikes for this week.

You may find that you need to manage spikes within your sprints. Remember to follow .

You're encouraged to continue role circles with those who are playing the same role as you.

Working with a client

• Know how to communicate with a client about a technical project

• Know how to manage the expectations of a Product Owner

UX

• Build an intuitive user experience

• Build an application from a set of user stories

Agile Workflow

• Experience an agile workflow

• Understand how agile methodology can provide benefit in the software development cycle

• Follow a sprint plan

Sprints

• Assign yourself to and fulfil user stories

• Work from a sprint backlog

• Manage a backlog of user stories

DevOps

• Host your website with AWS

• Use Terraform to customise deployment and manage AWS resources

• Configure monitoring tools to provide visible and actionable alerts

Week of December 9th

This week is not updated to FAC30