AWS Workshop Day 1: Hands-On Training Covers S3, CloudFront, and EC2 Basics

·55 views

A two-day cloud workshop focused on AWS fundamentals kicked off with its first session covering core infrastructure concepts. Participants logged into the AWS Management Console and learned how AWS Regions and Availability Zones support global reliability and low latency. The session included practical exercises with Amazon S3, where attendees created storage buckets, uploaded files, and served content via pre-signed URLs and a CloudFront CDN distribution. Learners were also introduced to Amazon EC2, launching virtual instances, connecting via SSH, and deploying the Nginx web server. The session provided a foundational overview of cloud storage, content delivery, and compute services on AWS.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

OpenAI Python SDK retries transient errors automatically; developers must handle the rest

The OpenAI Python SDK automatically retries connection problems, timeouts, rate-limit errors (429), and 5xx server errors using exponential backoff. Errors such as malformed requests (400), bad credentials (401/403), and missing resources (404) are not retried, since repeating them would fail again. Developers are responsible for setting suitable timeouts, handling non-retryable errors in their own code, and logging request IDs for tracing failures. The default timeout of 10 minutes suits long reasoning tasks but is too long for interactive web use, so a shorter timeout is recommended there. Because each retry can add another full timeout, the worst-case wait equals the timeout multiplied by the number of retries plus one.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

XNOV.io Offers Browser-Based Image Enhancement, But With Clear Limits

A reviewer tested XNOV.io, a free browser-based image tool that requires no signup, for compression and enhancement tasks over several weeks. The enhancement applies a restrained cleanup that sharpens detail and controls noise without the heavy halos or plastic-looking skin typical of phone filters. Test results showed improved legibility for a document photo and natural-looking results for an indoor portrait. The reviewer warns that badly degraded originals, such as very old scans or heavily compressed files, will only be cleaned up at the edges rather than restored. The tool is best suited to one-off jobs rather than batch processing of large photo libraries.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Tracking billable and non-billable hours in Jira without a built-in billable flag

Jira Cloud does not offer a billable flag on worklogs, so teams need a workaround to separate chargeable and internal time. The guide suggests marking whole work items with a label or select field when all their time is one type, or using a tag in worklog comments when a single item mixes both. Searching by label, including an IS EMPTY clause for unlabeled items, helps total time per work item. Summing hours by individual worklog through an export is needed to split mixed items, since searches only return work items. The article notes limits such as all-time totals, no partial billing within a worklog, and no protection against later edits, and mentions that a dedicated app may help for recurring monthly billing.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Running Claude Code 24/7 on a $2.25/month server

The author argues that running Claude Code on a small always-on server avoids stopping long tasks when a laptop lid closes. A cheap NAT VPS suffices because the agent only makes outbound connections, and the author uses natbox.io's Box Plus plan at $2.25 per month with 2 GB RAM, 2 shared cores, and 20 GB SSD. Setup involves ordering a Debian or Ubuntu server, installing Claude Code, and signing in with an existing Claude account that includes it, with work kept alive in tmux sessions reachable over SSH. The guide also suggests a firewall, notes that Docker is unavailable because the servers use LXC, and says that exceeding the monthly traffic allowance throttles speed to 10 Mbit/s rather than cutting service. The author discloses that they run natbox, the provider being recommended.

0 comments Read more at DEV Community