Aptible

aptible

We are back with another Company of the Week feature! Every week, we share an awesome tech brand from our tech company database, making their evergreen mark on the internet. This unique HackerNoon database ranks S&P 500 companies and top startups of the year alike. This week, we are proud to present Aptible, a Platform as a Service (PaaS) that gives startups everything they need to launch and scale apps and databases that are secure, reliable, and compliant. Not only does Aptible support a wide range of languages and frameworks, it also integrates with the tools engineers already love and use. The best part? No manual configuration required! What sets Aptible apart from other PaaS solutions is its commitment to scalability, reliability, and security & compliance. Want to be featured on HackerNoon’s Company of the Week? Request Your Tech Company Page on HackerNoon! Aptible🤝 HackerNoon Writing Contests Aptible was the proud sponsor of the DevOps Writing Contest, which ran for a six-month period and had a whopping $18,000 prize pool. The company partnered with HackerNoon to offer technologists with a wide variety of backgrounds, including DevOps managers, developers, or anyone in the QA team or operations team, to showcase their expertise in DevOps for a chance to win big bucks 🤑 Participants could write on IaaS, PaaS, PaaS vs. IaaS, Automated Deployment, Containerization and Orchestration, Microservices Architecture, GitOps, DevOps Culture, and more, and got to try out Aptible's hosting platform for free to share their learnings and feedback. "Aptible's mission is to enable developers to do more with less infrastructure. We also know that when it comes to infrastructure, there are a myriad of opinions, and strong opinions at that. And that’s why we’re excited to partner with HackerNoon, to get more content written, opinions out in the open, and spur active discussion and knowledge sharing of how infrastructure is being built and utilized," — Tin Nguyen, Head of Marketing at Aptible, said at the time. All in all, the writing contest generated over 260 stories and brought massive brand recall from Aptible’s intended audience with nearly 800k views and generating over 19 days in reading time. Find out how you can sponsor a Writing Contest with HackerNoon here. Meet Aptible: Fun Facts Aptible actually has quite an interesting history. At the time of its founding, the Health Insurance Portability and Accountability Act, or HIPAA, was taking shape with companies scrambling to figure out how to comply with the law. Recognizing this imminent need, Aptible embarked on a mission to simplify HIPAA for developers in healthcare, from solo developers at startups to large-scale development teams who lacked the time/resources to delve into the compliance space. Thanks to Aptible, developers had a platform that made HIPAA compliance achievable from day 1. The rest, as they say, is history. Today, Aptible has expanded its scope to support HITRUST, SOC 2, ISO 27001, and more — establishing themselves as the go-to PaaS not just for digital health companies, but for all dev teams, regardless of industry. How’s that for awesome? 😏 Share Your Company's Story via HackerNoon That's all this week, folks! Stay Creative, Stay Iconic. The HackerNoon Team We are back with another Company of the Week feature! Every week, we share an awesome tech brand from our tech company database , making their evergreen mark on the internet. This unique HackerNoon database ranks S&P 500 companies and top startups of the year alike. Company of the Week Company of the Week tech company database tech company database This week, we are proud to present Aptible , a Platform as a Service (PaaS) that gives startups everything they need to launch and scale apps and databases that are secure, reliable, and compliant. Aptible Aptible Not only does Aptible support a wide range of languages and frameworks, it also integrates with the tools engineers already love and use. The best part? No manual configuration required! What sets Aptible apart from other PaaS solutions is its commitment to scalability, reliability, and security & compliance. Want to be featured on HackerNoon’s Company of the Week? Request Your Tech Company Page on HackerNoon! Want to be featured on HackerNoon’s Company of the Week? Request Your Tech Company Page on HackerNoon ! Want to be featured on HackerNoon’s Company of the Week? Request Your Tech Company Page on HackerNoon Aptible🤝 HackerNoon Writing Contests Aptible was the proud sponsor of the DevOps Writing Contest , which ran for a six-month period and had a whopping $18,000 prize pool . The company partnered with HackerNoon to offer technologists with a wide variety of backgrounds, including DevOps managers, developers, or anyone in the QA team or operations team, to showcase their expertise in DevOps for a chance to win big bucks 🤑 DevOps Writing Contest DevOps Writing Contest $18,000 prize pool Participants could write on IaaS, PaaS, PaaS vs. IaaS, Automated Deployment, Containerization and Orchestration, Microservices Architecture, GitOps, DevOps Culture, and more, and got to try out Aptible's hosting platform for free to share their learnings and feedback. "Aptible's mission is to enable developers to do more with less infrastructure. We also know that when it comes to infrastructure, there are a myriad of opinions, and strong opinions at that. And that’s why we’re excited to partner with HackerNoon, to get more content written, opinions out in the open, and spur active discussion and knowledge sharing of how infrastructure is being built and utilized," — Tin Nguyen, Head of Marketing at Aptible, said at the time. said All in all, the writing contest generated over 260 stories and brought massive brand recall from Aptible’s intended audience with nearly 800k views and generating over 19 days in reading time. Find out how you can sponsor a Writing Contest with HackerNoon here. Find out how you can sponsor a Writing Contest with HackerNoon here. Find out how you can sponsor a Writing Contest with HackerNoon here. Meet Aptible: Fun Facts Aptible actually has quite an interesting history. Aptible At the time of its founding, the Health Insurance Portability and Accountability Act, or HIPAA, was taking shape with companies scrambling to figure out how to comply with the law. Recognizing this imminent need, Aptible embarked on a mission to simplify HIPAA for developers in healthcare, from solo developers at startups to large-scale development teams who lacked the time/resources to delve into the compliance space. Thanks to Aptible, developers had a platform that made HIPAA compliance achievable from day 1. The rest, as they say, is history. Today, Aptible has expanded its scope to support HITRUST, SOC 2, ISO 27001, and more — establishing themselves as the go-to PaaS not just for digital health companies, but for all dev teams, regardless of industry. How’s that for awesome? 😏 Share Your Company's Story via HackerNoon Share Your Company's Story via HackerNoon Share Your Company's Story via HackerNoon Share Your Company's Story via HackerNoon That's all this week, folks! Stay Creative, Stay Iconic. The HackerNoon Team

Meet Aptible: HackerNoon Company of the Week

HackerNoon - Haftanın Şirkəti

Mød Aptible: HackerNoon selskab af ugen

Conoce a Aptible: HackerNoon Compañía de la Semana

Meet Aptible: HackerNoon 週間の会社

Meet Aptible: HackerNoon 주간 회사

Fantaro ny mety: HackerNoon Company ny herinandro

Meet Aptible: HackerNoon долоо хоногийн компани

د اونۍ د شرکت HackerNoon

Meet Aptible: HackerNoon வாரம் நிறுவனம்

Etiketler: Hackernoon Haftanın Şirketi

Building a data scraping application is common for many developers, especially in fields where data collection, analysis, and storage are crucial. Using the Puppeteer, Node.js, and PostgreSQL trio is an excellent approach. is a great choice for this task. It allows you to control a headless browser, which is crucial for scraping dynamic websites. Many websites now use JavaScript to load content, and Puppeteer enables you to interact with and scrape this dynamic content. Puppeteer is well-suited for building scalable and efficient server-side applications. It's non-blocking and event-driven, making it a good fit for handling concurrent requests in a scraping application. Node.js will handle the backend of the data-scraping application. Node.js Storing the scraped data for the app will be handled by because it supports complex queries and indexing, which makes it suitable for storing and retrieving scraped data efficiently. PostgreSQL is a PaaS provider that aids the secure deployment of applications. It also provides database management services, with PostgreSQL being one of its supported databases. Hence, this project will use the managed PostgreSQL service provided by Aptible. Aptible In this tutorial, you'll discover how to build a data-scraping application using Puppeteer, Node.js, PostgreSQL, and Aptible. The application will scrape data from a popular movie streaming app, Netflix, and store it in a PostgreSQL database managed by Aptible. Prerequisites To follow along with this tutorial, you will need the following: A node version of 16.13.2 or greater is installed on your machine. You can install it by following the instructions on the . official Node.js website An Aptible account. Visit the to sign up. Aptible website A fundamental understanding of JavaScript and Node.js. Setting up the project To get started, create a new directory for the project and initialize a new Node.js project in it by running the following commands: mkdir web-scraper
cd web-scraper
npm init -y This will create a file for you with the following output: package.json Wrote to /home/user/web-scraper/package.json:

{
  "name": "web-scraper",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "keywords": [],
  "author": "",
  "license": "ISC"
} Installing dependencies To install the dependencies for the project, run the following command: npm install puppeteer pg dotenv This will install the necessary packages, which are Puppeteer, Node-postgres, and dotenv. Creating the database For the PostgreSQL database, you will use the managed database service on Aptible. To do this, follow the steps below: Log in to your Aptible account and create a new environment. Navigate to the new environment and click on > . Databases New Database Click on the dropdown menu and select . This will create a new PostgreSQL database for you. PostgreSQL 16 Input the Database Handle and click on to create the database. New Database This will provision a new PostgreSQL database for you. You can view the database by clicking the tab on the left menu. Databases Creating a database endpoint To connect to the PostgreSQL database, you will need to create a database endpoint. To do this, follow the steps below: Navigate to the database you created and click on > . Endpoints New Endpoint Include an IP address in the field. This will allow you to connect to the database from your local machine. IP Allowlist After the endpoint has finished provisioning, click on the tab. ConnectionURL Click on the button to copy the connection URL. You will need this to connect to the database. show Create the scraper script. This scraper script will scrape data from Netflix and store it in the PostgreSQL database. To create the script, create a new file named in the root of the project directory and add the following code to it: scraper.js const puppeteer = require("puppeteer");
const { Client } = require("pg");
require("dotenv").config(); The code above imports the necessary packages and loads the environment variables from the file. .env Below is a breakdown of the packages imported: : A headless browser automation library for Node.js used for web scraping. puppeteer : Part of the pg library, a PostgreSQL client for Node.js. Client : A library for loading environment variables from a file, used to load database credentials. dotenv Next, add the following code to the file: scraper.js async function run() {
  const browser = await puppeteer.launch({ headless: "new" });
  const page = await browser.newPage();

  // Navigate to the website you want to scrape
  await page.goto("https://netflix.com/");

  // Extract data from the page
  const data = await page.evaluate(() => {
    const title = document.querySelector("h1").innerText;
    const url = window.location.href;

    return { title, url };
  });

  // Close the browser
  await browser.close();

  return data;
} The code above creates a function named which will be used to scrape data from the Netflix website. run A brief explanation of the code above: is an asynchronous function that launches a headless browser using Puppeteer. run It opens a new page, navigates to , extracts data (title and URL) from the page using a function provided to , and then close the browser. https://netflix.com/ page.evaluate The extracted data is returned as an object. Next, add the following code to the file: scraper.js async function saveToDatabase(data) {
  const client = new Client({
    connectionString: process.env.DATABASE_URL,
    ssl: { rejectUnauthorized: false },
  });

  try {
    await client.connect();

    // Check if the table exists, and create it if not
    const createTableQuery = `
      CREATE TABLE IF NOT EXISTS scraped_data (
        id SERIAL PRIMARY KEY,
        title TEXT,
        url TEXT
      );
    `;
    await client.query(createTableQuery);

    // Insert data into the database
    const insertQuery = "INSERT INTO scraped_data (title, url) VALUES ($1, $2)";
    const values = [data.title, data.url];
    await client.query(insertQuery, values);
  } finally {
    await client.end();
  }
} The code above creates a function named which will be used to save the scraped data to the PostgreSQL database. saveToDatabase A brief explanation of the code above: is an asynchronous function that connects to the PostgreSQL database using the credentials in the environment variable. saveToDatabase DATABASE_URL It checks if the table exists and creates it if it doesn't. scraped_data It then inserts the scraped data into the database using an SQL query. Next, add the following code to the file: scraper.js (async () => {
  try {
    const scrapedData = await run();
    console.log("Scraped Data:", scrapedData);

    // Save data to the database
    await saveToDatabase(scrapedData);
    console.log("Data saved to the database.");
  } catch (error) {
    console.error("Error during scraping:", error);
  }
})(); The code above calls the function to scrape data from the Netflix website and then call the function to save the scraped data to the PostgreSQL database. run saveToDatabase A brief explanation of the code above: This immediately invoked function expression (IIFE) executes the scraping and database saving process. It catches any errors that occur during scraping or database operations and logs them. If successful, it logs the scraped data and a success message. All together, the file should look like this: scraper.js const puppeteer = require("puppeteer");
const { Client } = require("pg");
require("dotenv").config();

async function run() {
  const browser = await puppeteer.launch({ headless: "new" });
  const page = await browser.newPage();

  // Navigate to the website you want to scrape
  await page.goto("https://netflix.com/");

  // Extract data from the page
  const data = await page.evaluate(() => {
    const title = document.querySelector("h1").innerText;
    const url = window.location.href;

    return { title, url };
  });

  // Close the browser
  await browser.close();

  return data;
}

async function saveToDatabase(data) {
  const client = new Client({
    connectionString: process.env.DATABASE_URL,
    ssl: { rejectUnauthorized: false },
  });

  try {
    await client.connect();

    // Check if the table exists, and create it if not
    const createTableQuery = `
      CREATE TABLE IF NOT EXISTS scraped_data (
        id SERIAL PRIMARY KEY,
        title TEXT,
        url TEXT
      );
    `;
    await client.query(createTableQuery);

    // Insert data into the database
    const insertQuery = "INSERT INTO scraped_data (title, url) VALUES ($1, $2)";
    const values = [data.title, data.url];
    await client.query(insertQuery, values);
  } finally {
    await client.end();
  }
}

(async () => {
  try {
    const scrapedData = await run();
    console.log("Scraped Data:", scrapedData);

    // Save data to the database
    await saveToDatabase(scrapedData);
    console.log("Data saved to the database.");
  } catch (error) {
    console.error("Error during scraping:", error);
  }
})(); Creating a file .env The file will contain the database credentials. Create a new file named in the root of the project directory and add the following code to it: .env .env DATABASE_URL=postgres://<username>:<password>@<host>:<port>/<database> Replace the placeholders with the database credentials from the database endpoint you created earlier. Note: Running the scraper script To run the scraper script, run the following command: node scraper.js This will launch a headless browser, navigate to the Netflix website, scrape data from the page, and save the data to the PostgreSQL database on Aptible. You should see the following output: Scraped Data: {
  title: 'Unlimited movies, TV shows, and more',
  url: 'https://www.netflix.com/'
}
Data saved to the database. You can verify that the data was saved to the database by logging into the PostgreSQL database using the credentials from the database endpoint. You can do this by running the following command: psql <connection_url> Replace with the connection URL from the database endpoint. Note: <connection_url> Once you're logged in, you can list the tables in the database by running the following command: \dt You should see the table listed in the output: scraped_data List of relations
 Schema |     Name     | Type  |  Owner
--------+--------------+-------+---------
 public | scraped_data | table | aptible
(1 row) You can view the data in the table by running the following command: scraped_data SELECT * FROM scraped_data; You should see the scraped data listed in the output: id |                title                 |           url
----+--------------------------------------+--------------------------
  1 | Unlimited movies, TV shows, and more | https://www.netflix.com/
(1 row) Conclusion ​​In this tutorial, you learned how to create a data scrapping application using Puppeteer, Node.js, PostgreSQL, and Aptible. To enhance this project, consider adding more functionality to the scraper script. For instance, you can expand it to scrape data from multiple websites and store it in the database. Furthermore, you can extend the application by incorporating a frontend. This addition lets you visualize the scraped data in a web browser, enhancing the user experience.

Build a Data-Scraping App Using Puppeteer, Node.js, PostgreSQL and Aptible

If you faced challenges installing the Aptible CLI on a Linux server, this guide is here to help. Discover with these three simple steps how to install the Aptible CLI on Ubuntu 22.04. Why use the Aptible CLI? The Aptible CLI, like other command-line tools, aids in managing your Aptible resources. With the CLI, you can create, update, and delete Aptible resources. Additionally, it allows you to deploy your applications to Aptible. While there are three primary ways to interact with Aptible's resources, here are a few reasons why you might prefer using the Aptible CLI: The Aptible CLI empowers users to automate repetitive tasks and seamlessly integrate them into scripts or workflows. This script integration proves beneficial for systematically managing multiple environments, stacks, or databases. Automation and Scripting: For users comfortable with command-line interfaces, the Aptible CLI provides a streamlined and efficient way to interact with Aptible resources. Command-line operations can often be quicker than navigating through a graphical user interface. Efficient Workflow: The CLI seamlessly integrates with version control systems, enabling users to track changes to their infrastructure and quickly reproduce configurations across different environments. Version Control Integration: The Aptible CLI enables users to execute commands on their containers remotely. This feature is especially beneficial for tasks like debugging, inspecting logs, or performing maintenance without the need for direct access to the Aptible Dashboard. Remote Access and SSH: The CLI offers granular control over Aptible resources, empowering users to execute specific actions with precision. This capability is advantageous for users who prefer explicit, command-level control. Fine-grained Control: The Aptible CLI caters to users who value automation, command-line efficiency, and the ability to manage Aptible resources programmatically. It is a versatile tool for developers, DevOps teams, and anyone who prefers a command-line interface for managing their infrastructure. Prerequisites This guide provides the solution for installing the Aptible CLI on the Ubuntu 22.04 Linux distribution. To install the Aptible CLI, ensure you have the following: Basic understanding of the command line. If you are new to the command line, check out this to get started. tutorial A Linux server running Ubuntu 22.04. If you don't have a server, you can create one using any cloud provider like AWS, DigitalOcean, or Linode. A user account with sudo privileges. If you don't have a user account with sudo privileges, you can create one by following this . tutorial Three Steps to Install the Aptible CLI on Ubuntu 22.04 Instead of scouring through multiple Google search results, I've condensed the steps to install the Aptible CLI on Ubuntu 22.04 into three simple steps. Let's begin! Step 1 — Download the Aptible CLI Package The Aptible CLI is distributed as a single binary file. To download the Aptible CLI package, execute the following commands in your terminal: Store the Aptible CLI download URL in a variable: TOOLBELT_URL="https://omnibus-aptible-toolbelt.s3.amazonaws.com/aptible/omnibus-aptible-toolbelt/master/390/pkg/aptible-toolbelt_0.19.7%2B20230829220606%7Eubuntu.16.04-1_amd64.deb"

TOOLBELT_SHA1SUM="4ff2cf416c6ae03a76fac5c7d35ff836126256af" Download the Aptible CLI package: curl -fsSLO "$TOOLBELT_URL" Verify the Aptible CLI package: echo "$TOOLBELT_SHA1SUM  aptible-toolbelt_0.19.7%2B20230829220606%7Eubuntu.16.04-1_amd64.deb" | sha1sum -c - This step ensures that you download a secure and verified package before proceeding with the installation. Step 2 — Install the Aptible CLI Once the Aptible CLI package is downloaded and verified, the next step is to install it using the command: dpkg Install the Aptible CLI package: sudo dpkg -i aptible-toolbelt_*.deb Verify the installation: aptible version If the installation is successful, you should see the following output: aptible-cli v0.19.7 toolbelt Step 3 — Clean up The final step is to clean up the Aptible CLI package: Remove the Aptible CLI package: rm aptible-toolbelt_*.deb Verify the removal: ls aptible-toolbelt_*.deb If the removal is successful, you should see the following output: ls: cannot access 'aptible-toolbelt_*.deb': No such file or directory After installing the Aptible CLI, the initial step is to authenticate with Aptible. Once authenticated, you can promptly begin using the Aptible CLI to manage your Aptible resources. Conclusion In this guide, you've discovered how to install the Aptible CLI on Ubuntu 22.04 in three simple steps. Additionally, you gained insights into why using the Aptible CLI can be beneficial and the prerequisites for its installation. If you have any questions or feedback, feel free to comment below. I would love to hear from you!

How to Deploy the Aptible CLI on Ubuntu 22.04

Happy Holidays, Hackers! We are happy to be back with another winner announcement of the DevOps Writing Contest by Aptible and HackerNoon! For those who are reading about the DevOps Writing Contest for the first time - HackerNoon and Aptible bring you an exciting opportunity to showcase your expertise with a $3,000 prize pool for the top 3 #DevOps stories in each round. Need ideas to write? You can write anything related to DevOps. We are interested in reading about the challenges in implementing the DevOps infrastructure and how you deal with them. Click on this template for more details. Those who regularly participate in the contest - your active participation has made this contest a success! We have published hundreds of DevOps stories so far, generating days of reading time. This couldn’t happen without your contribution. All the best! Those who are trying to win the contest by using AI-generated content, plagiarism, or buying bot traffic, we will find out and disqualify you 😇 About Sponsor Aptible’s hosting platform automates the work of provisioning, managing, and scaling infrastructure so developers can focus on what actually matters: their product. Get started for free with Aptible. The DevOps Writing Contest: Round 4 Finalists For selecting the nominations, we picked all the stories with the #devops tag on HackerNoon, published in November. Then, we chose the top stories weighing in the following factors: Number of hours read
The number of people reached
The originality of the content
Relevance to the topics shared by the sponsor. See the contest’s writing prompt here. Here’s the list of the Round 4 finalists: How to Sell A Technical Debt From a DevOps Perspective? by @goal23.
Getting Started With Aptible to Deploy Your First Secure Containerized Application by @emmanuelohaba.
Remarkable Shift From Monolith to Microservices - Empowered by AI-Driven DevOps by @induction.
How to Structure Your K8s GitOps Repository at Scale [Part 1] by @sturgelose.
Serverless NestJS Automation on AWS Lambda by @elegantly.
Networking: How Useful is pyATS in NetDevOps? by @verlainedevnet.
PaaS: Aptible vs Heroku by @aahil.
Bon Appétit: An Introduction to CI/CD and DevSecOps With a Delicious Bakery Story by @z3nch4n.
Spring Boot on Choreo: Connecting a Database by @jaadds.
Telecom's AI Revolution: How Predictive Analytics Optimizes CI/CD Pipelines by @pavanai. Round 4 Winners of The DevOps Writing Contest by Aptible The winner story this month is: https://hackernoon.com/how-to-structure-your-k8s-gitops-repository-at-scale-part-1?embedable=true Kustomizations are mostly based on layering and creating different variants.
This means that for each unique combination, I need a Kustomization file that aggregates all the different services. You might already be imagining multiple folders with a single kustomization file aggregating that unique combination for a specific platform component. Well deserved, @sturgelose! You have won 1500! In the second place, we have: https://hackernoon.com/serverless-nestjs-automation-on-aws-lambda?embedable=true Serverless deployment of a NestJS application involves careful configuration, resource management, and integration of various components. By following the steps and configurations described in this guide, you can build and deploy scalable, efficient, and maintainable serverless applications on AWS Lambda. Wow - your first story on HackerNoon, @elegantly, and it has won a contest! You have bagged $1000 and second place in the DevOps Writing Contest. In the third place, we have: https://hackernoon.com/spring-boot-on-choreo-connecting-a-database?embedable=true In practice, we don’t commit sensitive details like database connection parameters in plain text. Since they’re in a repository, anyone with access to the repo could then change the database. Instead, we use environment variables as placeholders. We can set these variables in our local environment to get the values resolved properly. Congratulations, @jaadds! You have won $500! Here are the next steps to claim your prize: Please contact yes-reply@hackernoon.com and sidra@hackernoon.com using the email ID attached to the winner's HackerNoon account.
We will validate your claim and share a form requesting your bank details for reward distribution.
You will receive your winnings in 2-4 weeks after filling out the form. Please note that you must contact us within 60 days after the winners’ announcement date. The HackerNoon writing contests primarily aim to celebrate quality content and recruit educational stories for our community. We congratulate all the finalists. However, the Editorial team can ban a writer and/or disqualify a story if we find any misconduct like plagiarism, use of AI, copyright infringement, or disinformation. Visit contests.hackernoon.com to learn more about running and upcoming contests.
P.S. We have 4 new contests in line for you with $10,000 of prizes! Happy Holidays, Hackers! We are happy to be back with another winner announcement of the DevOps Writing Contest by Aptible and HackerNoon! For those who are reading about the DevOps Writing Contest for the first time - HackerNoon and Aptible bring you an exciting opportunity to showcase your expertise with a $3,000 prize pool for the top 3 #DevOps stories in each round. DevOps Writing Contest by Aptible and HackerNoon! Need ideas to write? You can write anything related to DevOps. We are interested in reading about the challenges in implementing the DevOps infrastructure and how you deal with them. Click on this template for more details. Need ideas to write? You can write anything related to DevOps. We are interested in reading about the challenges in implementing the DevOps infrastructure and how you deal with them. Click on this template for more details. this template Those who regularly participate in the contest - your active participation has made this contest a success! We have published hundreds of DevOps stories so far, generating days of reading time. This couldn’t happen without your contribution. All the best! Those who are trying to win the contest by using AI-generated content, plagiarism, or buying bot traffic, we will find out and disqualify you 😇 About Sponsor Aptible’s hosting platform automates the work of provisioning, managing, and scaling infrastructure so developers can focus on what actually matters: their product. Get started for free with Aptible. The DevOps Writing Contest: Round 4 Finalists For selecting the nominations, we picked all the stories with the #devops tag on HackerNoon, published in November. Then, we chose the top stories weighing in the following factors: #devops Number of hours read The number of people reached The originality of the content Relevance to the topics shared by the sponsor. See the contest’s writing prompt here. Number of hours read The number of people reached The originality of the content Relevance to the topics shared by the sponsor. See the contest’s writing prompt here. Here’s the list of the Round 4 finalists: How to Sell A Technical Debt From a DevOps Perspective? by @goal23. Getting Started With Aptible to Deploy Your First Secure Containerized Application by @emmanuelohaba. Remarkable Shift From Monolith to Microservices - Empowered by AI-Driven DevOps by @induction. How to Structure Your K8s GitOps Repository at Scale [Part 1] by @sturgelose. Serverless NestJS Automation on AWS Lambda by @elegantly. Networking: How Useful is pyATS in NetDevOps? by @verlainedevnet. PaaS: Aptible vs Heroku by @aahil. Bon Appétit: An Introduction to CI/CD and DevSecOps With a Delicious Bakery Story by @z3nch4n. Spring Boot on Choreo: Connecting a Database by @jaadds. Telecom's AI Revolution: How Predictive Analytics Optimizes CI/CD Pipelines by @pavanai. How to Sell A Technical Debt From a DevOps Perspective? by @goal23 . How to Sell A Technical Debt From a DevOps Perspective? @goal23 Getting Started With Aptible to Deploy Your First Secure Containerized Application by @emmanuelohaba . Getting Started With Aptible to Deploy Your First Secure Containerized Application @emmanuelohaba Remarkable Shift From Monolith to Microservices - Empowered by AI-Driven DevOps by @induction . Remarkable Shift From Monolith to Microservices - Empowered by AI-Driven DevOps @induction How to Structure Your K8s GitOps Repository at Scale [Part 1] by @sturgelose . How to Structure Your K8s GitOps Repository at Scale [Part 1] @sturgelose Serverless NestJS Automation on AWS Lambda by @elegantly . Serverless NestJS Automation on AWS Lambda @elegantly Networking: How Useful is pyATS in NetDevOps? by @verlainedevnet . Networking: How Useful is pyATS in NetDevOps? @verlainedevnet PaaS: Aptible vs Heroku by @aahil . PaaS: Aptible vs Heroku @aahil Bon Appétit: An Introduction to CI/CD and DevSecOps With a Delicious Bakery Story by @z3nch4n . Bon Appétit: An Introduction to CI/CD and DevSecOps With a Delicious Bakery Story @z3nch4n Spring Boot on Choreo: Connecting a Database by @jaadds . Spring Boot on Choreo: Connecting a Database @jaadds Telecom's AI Revolution: How Predictive Analytics Optimizes CI/CD Pipelines by @pavanai . Telecom's AI Revolution: How Predictive Analytics Optimizes CI/CD Pipelines @pavanai Round 4 Winners of The DevOps Writing Contest by Aptible The winner story this month is: https://hackernoon.com/how-to-structure-your-k8s-gitops-repository-at-scale-part-1?embedable=true https://hackernoon.com/how-to-structure-your-k8s-gitops-repository-at-scale-part-1?embedable=true Kustomizations are mostly based on layering and creating different variants. This means that for each unique combination, I need a Kustomization file that aggregates all the different services. You might already be imagining multiple folders with a single kustomization file aggregating that unique combination for a specific platform component. Kustomizations are mostly based on layering and creating different variants. This means that for each unique combination, I need a Kustomization file that aggregates all the different services. You might already be imagining multiple folders with a single kustomization file aggregating that unique combination for a specific platform component. Well deserved, @sturgelose! You have won 1500! In the second place, we have: https://hackernoon.com/serverless-nestjs-automation-on-aws-lambda?embedable=true https://hackernoon.com/serverless-nestjs-automation-on-aws-lambda?embedable=true Serverless deployment of a NestJS application involves careful configuration, resource management, and integration of various components. By following the steps and configurations described in this guide, you can build and deploy scalable, efficient, and maintainable serverless applications on AWS Lambda. Serverless deployment of a NestJS application involves careful configuration, resource management, and integration of various components. By following the steps and configurations described in this guide, you can build and deploy scalable, efficient, and maintainable serverless applications on AWS Lambda. Wow - your first story on HackerNoon, @elegantly, and it has won a contest! You have bagged $1000 and second place in the DevOps Writing Contest. In the third place, we have: https://hackernoon.com/spring-boot-on-choreo-connecting-a-database?embedable=true https://hackernoon.com/spring-boot-on-choreo-connecting-a-database?embedable=true In practice, we don’t commit sensitive details like database connection parameters in plain text. Since they’re in a repository, anyone with access to the repo could then change the database. Instead, we use environment variables as placeholders. We can set these variables in our local environment to get the values resolved properly. In practice, we don’t commit sensitive details like database connection parameters in plain text. Since they’re in a repository, anyone with access to the repo could then change the database. Instead, we use environment variables as placeholders. We can set these variables in our local environment to get the values resolved properly. Congratulations, @jaadds! You have won $500! Here are the next steps to claim your prize: Please contact yes-reply@hackernoon.com and sidra@hackernoon.com using the email ID attached to the winner's HackerNoon account. We will validate your claim and share a form requesting your bank details for reward distribution. You will receive your winnings in 2-4 weeks after filling out the form. Please contact yes-reply@hackernoon.com and sidra@hackernoon.com using the email ID attached to the winner's HackerNoon account. We will validate your claim and share a form requesting your bank details for reward distribution. You will receive your winnings in 2-4 weeks after filling out the form. Please note that you must contact us within 60 days after the winners’ announcement date. The HackerNoon writing contests primarily aim to celebrate quality content and recruit educational stories for our community. We congratulate all the finalists. However, the Editorial team can ban a writer and/or disqualify a story if we find any misconduct like plagiarism, use of AI, copyright infringement, or disinformation. The HackerNoon writing contests primarily aim to celebrate quality content and recruit educational stories for our community. We congratulate all the finalists. However, the Editorial team can ban a writer and/or disqualify a story if we find any misconduct like plagiarism, use of AI, copyright infringement, or disinformation. Visit contests.hackernoon.com to learn more about running and upcoming contests. P.S. We have 4 new contests in line for you with $10,000 of prizes! Visit contests.hackernoon.com to learn more about running and upcoming contests. contests.hackernoon.com P.S. We have 4 new contests in line for you with $10,000 of prizes!

The DevOps Writing Contest by Aptible: Round 4 Winners Announced!

Aptible দ্বারা DevOps রচনা প্রতিযোগিতা: রাউন্ড 4 বিজয়ীদের ঘোষণা করা হয়েছে!

Der DevOps-Schreibwettbewerb von Aptible: Gewinner der vierten Runde bekannt gegeben!

El concurso de escritura DevOps de Aptible: ¡Se anuncian los ganadores de la cuarta ronda!

Le concours d'écriture DevOps d'Aptible : les gagnants de la quatrième ronde sont annoncés !

एप्टिबल द्वारा डेवऑप्स लेखन प्रतियोगिता: राउंड 4 के विजेताओं की घोषणा!

Aptible による DevOps ライティング コンテスト: 第 4 ラウンドの勝者が発表されました!

Aptible의 DevOps 글쓰기 콘테스트: 4라운드 우승자가 발표되었습니다!

O Concurso de Redação DevOps da Aptible: Anunciados os vencedores da quarta rodada!

Конкурс DevOps-писателей от Aptible: объявлены победители четвертого тура!

Aptible'ın DevOps Yazma Yarışması: 4. Turun Kazananları Açıklandı!

Cuộc thi viết DevOps của Aptible: Công bố người chiến thắng Vòng 4!

Aptible 的 DevOps 写作大赛：第四轮获奖者公布！

Have you ever wished you could deploy your codes with just a few clicks without worrying about server configuration, environment, and infrastructure headaches? Well, that's exactly what Aptible enables you to do. Aptible is a Platform-as-a-Service (PaaS) provider that allows users to deploy applications and APIs without worrying about any infrastructure or deployment complexities. With Aptible, you just need to worry about your codes, build awesome functionalities, and make your customers happy. Aptible takes care of everything from application provisioning to orchestration, even with limited prior knowledge. This doesn’t mean you can’t customize your infrastructure environment on Aptible to meet your needs. One of my favorite features of this platform is the Docker image deployment. This feature lets you seamlessly deploy your pre-built Docker images to encapsulate application code and dependencies across environments. With this, you can automate your process and push updates in a matter of minutes. In this guide, I share what I’ve learned to help you get up and deploy through Aptible’s Docker image deployment. In this guide, you will learn: How to set up your Aptible’s environment and app quickly and hassle-free. How to deploy your containerized apps with Aptible More advanced Aptible’s functionalities. Prerequisites Before you get started with this guide, you will need the following prerequisites: Install . Git Create an . Aptible account Install . Aptible CLI Install . This can help you with this. Docker desktop guide from the Docker docs Setting Up Your Aptible’s Environment and App Quickly and Without Any Hassle The Aptible CLI helps you manage your Aptible resources—create, modify, deploy, scale, and delete Aptible resources—directly from the command line. After , you will need to log into Aptible via the CLI using the command below: Installing the Aptible CLI aptible login This will prompt you to input your email and password for authentication. Next, you will need to create your environment and app using the syntax below. Remember to replace  <app name> and <environment name> with the name of your environment and app. Alternatively, you can create your Aptible app and environment on the Aptible dashboard. You can do this by creating and naming your environment. You will be on the shared resource plan if you're on a free trial. After creating your environment, you can simply create and name your app. Right on the dashboard, you must add your . If you don’t have one, you can generate one using the command below. SSH key public key ssh-keygen -t ed25519 -C "youremail@domain.com" You can also learn more about the SSH key through these . As you can see, you can do most of your work right in the Aptible dashboard. GitHub docs Deploying Your Containerized Apps With Aptible Before you can deploy directly from the Docker image, you will need to build your Docker image locally. Now, let’s start by running the commands below to your Docker image to your app: aptible deploy --app "$APP_HANDLE" --docker-image "$DOCKER_IMAGE" Remember to replace and with your app name and Docker Image. "$APP_HANDLE" "$DOCKER_IMAGE" aptible deploy --app "apptest" --docker-image "nginx:latest" This will deploy your Docker image to your Aptible app. As you can see, deploying directly from a Docker image is quite simple. Now, let's take a look at some other functions of Aptible. More Advanced Aptible’s Functionalities While Aptible deployment is undeniably seamless, it's just the tip of the iceberg. Aptible offers various other functionalities that you can explore to streamline your development journey. These functionalities include log visibility, effortlessly adding or removing resources by scaling your applications to adapt to fluctuating demands, and de-provisioning your apps with just a click. Another is the ability to bring your app to the world by simply creating and managing endpoints and enabling seamless communication with external services. The details all about the functionalities and possibilities of Aptible. Aptible documentation Deploy With Apitble? Share It and Get a Shirt! You successfully deployed to Aptible directly from the Docker image in this guide. By following the steps here, you can deploy your code and containerized apps to the Aptible platform. Of course, we just scratched the surface of what can be done with Apitble. For example, you can explore the instead of using the Aptible Dashboard or CLI. Aptible Terraform to manage your resources So, explore this amazing and powerful platform, deploy an app, and get a shirt!

Beginner's Guide to Docker Image Deployment With Aptible (and Get a Free Shirt!)

are an essential component in the DevOps toolkit, providing valuable insights into application and infrastructure performance. Designed to focus on security and compliance, Aptible Logs offers real-time visibility and monitoring capabilities, enabling proactive issue detection and swift troubleshooting. Their utility extends to debugging and root cause analysis, allowing teams to identify and address issues promptly, minimizing downtime. Aptible Logs DevOps Aptible Logs contribute significantly to performance optimization by monitoring resource utilization and facilitating benchmarking and tuning processes. This attention to detail aligns with Aptible's commitment to delivering a secure and compliant hosting environment, making it suitable for businesses in regulated industries. With integrated logging and monitoring tools, Aptible Logs simplifies the operational aspects of system maintenance. This user-friendly approach and transparent pricing ensure accessibility and ease of use for teams adopting the platform. The focus on containerization technologies further enhances scalability and flexibility, catering to dynamic workloads. So, Aptible Logs offers a comprehensive solution for DevOps teams, aligning with the platform's overarching emphasis on security, compliance, and a streamlined operational workflow. Getting started with Aptible Logs: Setting Up # Use the Aptible CLI to configure the Docker log driver
aptible config:set DOCKER_LOG_DRIVER=aptible Aptible Logs begins with a seamless integration into your application deployment. This involves configuring log drivers and, in the case of Aptible, utilizing the powerful Docker log driver. The example above demonstrates how straightforward this process is using the Aptible CLI(Command-line interface). By setting the to "aptible," you signal to the platform that you want to leverage its native logging capabilities. This is the foundation for tapping into the real-time insights and troubleshooting capabilities that Aptible Logs provides. DOCKER_LOG_DRIVER This configuration sets the stage for Aptible Logs to collect, aggregate, and present logs from your containers in a centralized and structured manner. As you progress through this guide, this initial setup will prove crucial for the effective utilization of Aptible Logs in your day-to-day DevOps operations. Aggregation and search capabilities # View aggregated logs for your app
aptible logs Once you've configured Aptible Logs to collect your application's logs, the next step is to navigate the log landscape efficiently. Aptible Logs provides a centralized view of your application's activity, allowing you to access aggregated logs seamlessly. Filtering Logs by time range or component # View logs within a specific time range
aptible logs --start "2023-01-01T00:00:00Z" --end "2023-01-10T00:00:00Z"

# Filter logs by component (e.g., web, database)
aptible logs --component web To enhance your log exploration, consider filtering logs based on time range or component. The examples above demonstrate how to narrow down your log output, making it easier to focus on specific events or periods. Troubleshooting with Aptible Logs # View error logs for your app
aptible logs --filter "level=error" Incorporate Aptible Logs into your troubleshooting toolkit by identifying errors with precision. Use filters like to narrow down logs and focus on issues that require immediate attention. level=error # Trace the flow of requests through your app
aptible logs --filter "request.path=/api/users" Trace the flow of requests through your application to diagnose performance issues. Utilize filters such as to isolate logs relevant to specific components of your app. request.path=/api/users Performance optimization # Extract CPU and memory usage metrics
aptible logs --filter "source=app" --format "timestamp,source,message" Beyond troubleshooting and centralized log aggregation, Aptible Logs empowers you to proactively optimize your application's performance. Extracting meaningful performance metrics, such as CPU and memory usage, becomes a key practice for ensuring efficiency and reliability. The familiar entry point to your application's logs. aptible logs: This filter narrows down the logs to those specifically related to your application. This is particularly useful in a multi-component application where you might want to focus on a specific service. --filter "source=app": The option tailors the log output to include specific fields. In this example, we're extracting the timestamp, source (component), and the log message itself. --format "timestamp,source,message": --format Integration Possibilities with Aptible Logs # Example Grafana configuration for Aptible Logs
datasources:
  - name: Aptible Logs
    type: prometheus
    url: https://logs-api.aptible.com/prometheus Aptible Logs doesn't operate in isolation; instead, it seamlessly integrates with popular monitoring and visualization platforms. One such powerful integration is with Grafana, providing you with a unified and comprehensive view of your application's health. A key section in Grafana's configuration where data sources, like Aptible Logs, are defined. datasources: A user-defined name for the data source, making it easily identifiable within Grafana. name: Aptible Logs: Despite the name, this doesn't mean you're limited to Prometheus data. Grafana has built-in support for Prometheus, and by selecting this type, you enable Grafana to interpret the data from Aptible Logs. type: prometheus: The endpoint URL pointing to the Aptible Logs API. This is where Grafana fetches the log data for visualization. url: : https://logs-api.aptible.com/prometheus Log archiving # Configure log archiving and rotation settings
aptible logs:config --archive-days 30 --rotate-size 100M As your application generates logs over time, effective log management becomes crucial. Aptible Logs offers a solution through log archiving and rotation settings, allowing you to optimize storage, adhere to compliance requirements, and ensure efficient use of resources. Exporting Logs to external services # Send logs to an external syslog server
aptible logs:export --destination syslog --url syslog://external-syslog-server.com This capability extends the reach of your logs, allowing for deeper analysis, integration with other monitoring tools, and the maintenance of a comprehensive view of your infrastructure. Collaboration with team members # Share logs with team members
aptible logs --follow | ssh user@remote-server "tee -a /path/to/remote/log/file.log" Aptible Logs makes this seamless by allowing you to share logs with team members. The provided example showcases streaming logs to a remote server, fostering collaboration as multiple team members can simultaneously view the same logs. Initiates log streaming in real-time. This ensures that as new logs are generated, they are immediately displayed in the terminal. aptible logs --follow: Utilizes the command through SSH to append the streamed logs to a file on a remote server. This creates a shared log file accessible to team members. | ssh user@remote-server "tee -a /path/to/remote/log/file.log": tee Conclusion Beginning with simple configuration and centralized log aggregation, provides real-time visibility, easing troubleshooting and offering a holistic view of system behavior. Aptible Logs Aptible Logs empowers proactive performance optimization. Extracting meaningful metrics enables efficient resource usage, contributing to a seamless user experience. The tool's integration capabilities extend to popular monitoring tools like Grafana, fostering a unified view of application health within DevOps. Aptible Logs doesn't stop at the basics. With advanced features like real-time log streaming, advanced filtering, and exporting logs to external services, it offers versatility tailored to diverse needs. Aptible Logs emerges not just as a log management solution but as a key enabler, unlocking the potential of modern application deployment and DevOps practices. So, mastering Aptible Logs translates to enhanced insights, efficiency, and collaboration in navigating the complexities of the DevOps landscape.

Mastering Aptible Logs for DevOps Excellence

DevOps শ্রেষ্ঠত্বের জন্য উপযুক্ত লগগুলি আয়ত্ত করা

Aptible Logs für DevOps-Exzellenz beherrschen

Dominar los registros aptos para la excelencia en DevOps

Maîtriser les logs Aptible pour l'excellence DevOps

DevOps उत्कृष्टता के लिए उपयुक्त लॉग में महारत हासिल करना

DevOps Excellence のための Aptible ログのマスタリング

DevOps 우수성을 위한 적절한 로그 마스터하기

Dominando logs aptíveis para excelência em DevOps

Освоение журналов Aptible для повышения эффективности DevOps

DevOps Mükemmelliği için Uygun Günlüklerde Uzmanlaşma

Nắm vững nhật ký thích hợp để DevOps xuất sắc

掌握适用的日志以实现卓越的 DevOps

Why spend a ridiculous amount of time and resources trying to set up & manage your infrastructure when you can rely on Aptible to do it for you? Use these three steps to deploy a Docker image from your AWS ECR private repository to Aptible. What is Aptible? Aptible is a platform as a service that provides a scalable environment for deploying applications. In this environment, Aptible delivers development teams infrastructure tools such as storage, servers, load balancers, security & compliance, and more. These tools allow development teams to focus on writing code and deploying applications rather than managing infrastructure. Companies can save money and all the resources needed to set up and manage their infrastructure by relying on Aptible. Aptible offers a pay-as-you-go pricing model, allowing companies to only pay for the resources they use. It also gives a free one-month trial to development teams testing the platform for the first time. Using Aptible, you can deploy any application via the user-friendly Aptible dashboard. It also allows other deployment options, including Infrastructure as Code via Terraform and the Aptible CLI. All these platforms ensure that developers can deploy applications in the most comfortable manner. How to deploy a Docker image from AWS ECR to Aptible Project Overview For this project, we'll use a word counter application that counts the number of words in a sentence. This application will be packaged into a Docker image and deployed to a private AWS ECR repository. We'll then deploy this Docker image to Aptible using the Aptible CLI. JavaScript From this overview, we can see that there are three main steps to complete this project: Build a Docker image and push it to AWS ECR Authenticate AWS ECR with Aptible Deploy to Aptible Step 1: Step 2: Step 3: Prerequisites Before you begin this project, you'll need to have the following: An AWS account. If you don't have one, you can create one on the official AWS website. The is installed and configured with your AWS account. Make sure the AWS CLI has appropriate permissions to access AWS ECR. AWS CLI An Aptible account. If you don't have one, sign up on the . Aptible website The Aptible CLI. You can install it using the . Aptible CLI documentation Docker. You can install it . here Once you have created the following accounts and installed the necessary tools, you can begin with step one of this project. Step 1: Build a Docker image and push it to AWS ECR We'll package a JavaScript word counter application into a Docker image for this step. After that, we'll push this Docker image to a private AWS ECR repository. To build the Docker image, follow these steps: Clone the word counter application: $ git clone https://github.com/Aahil13/Word-counter.git Navigate to the word counter application directory: $ cd Word-counter You'll find all the files and folders for this application in this directory. Part of these files is a containing instructions for building the image. Dockerfile From the , build the Docker image: Dockerfile $ docker build -t word-counter . Verify that the Docker image was built: $ docker images --filter reference=word-counter You should see the following output: REPOSITORY     TAG       IMAGE ID       CREATED          SIZE
word-counter   latest    c3d724e0a19e   12 seconds ago   60MB You can view the application locally using the following command: $ docker run -p 80:80 word-counter Navigate to your browser and point to the URL: . http://localhost:80 On your browser, you see the word counter application: To stop the application, press . CTRL+C With this, we have built the Docker image. Now, you'll push this Docker image to a private AWS ECR repository. To push the Docker image to AWS ECR, follow these steps: Using the AWS CLI, log in to AWS ECR: $ aws ecr get-login-password --region <REGION> | docker login --username AWS --password-stdin <AWS_ACCOUNT_ID>.dkr.ecr.<REGION>.amazonaws.com Replace with your AWS account ID and with the AWS region you want to use. <AWS_ACCOUNT_ID> <REGION> Create the private AWS ECR repository: aws ecr create-repository \
  --repository-name word-counter \
  --image-scanning-configuration scanOnPush=true \
  --region region Tag the Docker image: $ docker tag word-counter:latest <AWS_ACCOUNT_ID>.dkr.ecr.<REGION>.amazonaws.com/word-counter Push the Docker image to AWS ECR: $ docker push <AWS_ACCOUNT_ID>.dkr.ecr.<REGION>.amazonaws.com/word-counter You should see the following output: Using default tag: latest
The push refers to repository [<AWS_ACCOUNT_ID>.dkr.ecr.<REGION>.amazonaws.com/word-counter]
0342869436ee: Pushed
c1f569e0c435: Pushed
29c9ccae1ae2: Pushed
53bd9605a443: Pushed
c140f535da0a: Pushed
aba51e9dc8b1: Pushed
cc2447e1835a: Pushed With this, you have pushed the Docker image to AWS ECR. Now, we'll move on to step two of this project. Step 2: Authenticate AWS ECR with Aptible In this step, we'll authenticate the AWS ECR repository with Aptible. This authentication will give Aptible access to pull the Docker image from the AWS ECR repository. To authenticate the AWS ECR repository with Aptible, follow these steps: Login to Aptible from the CLI: $ aptible login You should see the following output: Email: <EMAIL>
Password:

Logged in as <EMAIL> Authenticate the AWS ECR repository with Aptible. : In this step, we'll run the same command in Step 1 to log in to AWS ECR. However, the ECR Docker login password will be stored in a variable. This variable will then authenticate the AWS ECR repository with Aptible. Note $ ECR_PASSWORD=$(aws ecr get-login-password --region <REGION>) Replace with the AWS region you want to use. This command will store the ECR Docker login password in the variable. <REGION> ECR_PASSWORD $ echo -n "$ECR_PASSWORD" | docker login --username AWS --password-stdin <AWS_ACCOUNT_ID>.dkr.ecr.<REGION>.amazonaws.com Replace with your AWS account ID and with the AWS region you want to use. This command will authenticate the AWS ECR repository with Aptible. <AWS_ACCOUNT_ID> <REGION> : We had to re-authenticate the AWS ECR repository with Aptible because the ECR Docker login password is necessary to deploy an application to Aptible. In Step 1, the password was passed using the flag. This flag ensures that the ECR Docker login password is not stored in the shell history. However, this flag is not supported by Aptible. Therefore, we had to re-authenticate the AWS ECR repository with Aptible, saving the ECR Docker login password in a variable. Note --password-stdin With this, we have authenticated the AWS ECR repository with Aptible. Now, we'll move on to step three of this project. Step 3: Deploy to Aptible This project's final step is deploying the Docker image to Aptible. To do this, we'll be using a single Aptible CLI command. Before executing the command, navigate to the Aptible Dashboard and create an app. You can do this by following these steps: Navigate to the Aptible Dashboard. In the Environments section, select the environment you want to use. Navigate to the Apps tab and click on the New App button. Enter the app name and click on the Create App button. After creating the app, you can deploy the Docker image to Aptible. To deploy the Docker image to Aptible, execute the command below: $ aptible deploy --app "<APP_NAME>" --docker-image "<AWS_ACCOUNT_ID>.dkr.ecr.<REGION>.amazonaws.com/word-counter" --private-registry-username "AWS" --private-registry-password "$ECR_PASSWORD" Replace with your AWS account ID, with the AWS region you want to use, and with the name of the app you created in the Aptible Dashboard. <AWS_ACCOUNT_ID> <REGION> <APP_NAME> You should see the following output: Hurrah! You have successfully deployed the Docker image to Aptible. You can now view the application on Aptible. Navigate to the Aptible Dashboard and select the app you created. You should see the following output: Although we have finished the deployment, we can't access the application yet. To access the application on your browser, you must create an endpoint. To create an endpoint, follow these steps: On the Apps section, select the app and switch to the Endpoints tab below. word-count Click on the New Endpoint button. Select the configurations as shown below: Click on the Save Endpoint button. It will take a few minutes for the endpoint to be provisioned. Once the endpoint is created, you can access the application using the endpoint URL. From the output, you can see that Aptible provisions a secure endpoint for the application. This endpoint is secured using a TLS certificate from Let's Encrypt. Aptible also provisions a load balancer for the application. This load balancer ensures that the application is highly available. : At the time of this writing, Aptible supports the creation of only one endpoint for a free tier account. If you want to create more endpoints, you must upgrade your account. Note Conclusion As displayed throughout this project, Aptible is an excellent platform for deploying applications. Aptible provided all the infrastructure tools needed for deploying the word counter application. Eliminating the need to set up and manage infrastructure. This hands-on project taught you how to deploy a Docker image from AWS ECR to Aptible. You can now deploy any application from AWS ECR to Aptible using the steps outlined in this project. To learn more about Aptible’s services, you can check out the . Aptible documentation More resources: Using Amazon ECR with the AWS CLI Direct Docker image deployment

How to Deploy a Docker Image From AWS ECR to Aptible in Three Steps

With data breaches on the rise, security needs to be top of mind before deploying any new application. But balancing app security with rapid innovation can be a major DevOps bottleneck. How can developers quickly ship secure code without compromising agility? The answer lies in Aptible - a container orchestration platform purpose-built to shepherd applications from code to cloud while automating security, compliance, and best practices every step of the way. In this hands-on guide, we’ll walk through using Aptible to launch your first containerized web application in a fully managed, end-to-end secure environment. Features and Benefits of Aptible With Aptible, software teams do not have to worry about configuring servers, setting up databases, maintaining security policies, monitoring systems, and other DevOps/infrastructure responsibilities. This streamlines the development workflow, making it faster and easier for engineers to ship code from their local environments directly to production deployment. Aptible manages provisioning infrastructure on demand to support deployments while handling monitoring, logging, and auto-scaling based on load. Here are some of the benefits Aptible offers: Git-based Deployment Aptible integrates with Git version control, allowing code changes to be easily pushed from any branch to their robust PaaS for rapid deployment. This automates the build, test, and release processes. The PaaS completely handles provisioning underlying servers, configuring networks, managing databases, applying security policies, monitoring health, and scaling capacity - all with no-ops work required by the development teams. Convenience and Scalability Aptible’s deployment process is not at all complicated. If you have all the requirements (identified below), you can get your app live and running in less than a minute. Plus, it offers on-demand scaling as well as vertical auto-scaling to ensure that your deployment needs are met even as the app grows. You can seamlessly integrate Aptible with your CI/CD tools to ensure a smooth process. Also, it offers flexibility: you can choose different interfaces (Aptible CLI, dashboard, Terraform provider) based on your preferences and needs. Reliability Aptible is poised to reduce downtime to a minimum. With Aptible, you get zero-downtime app deployments, while database downtimes typically don’t last more than a minute and are infrequent. It runs its platform across multiple public cloud regions. Customers can provision stack resources in any supported region for geographic redundancy. If an entire region goes down, traffic can be filed over to apps and databases running in alternate regions. By combining these techniques, resources are redundantly distributed to avoid single points of failure. This keeps applications running smoothly for customers with minimal disruptions to the end-user experience. Compliance and Security Aptible offers users a fully managed platform. This includes encryption, DDoS protection, intrusion detection, vulnerability scanning, VPNs, and role-based access controls. Authentication methods such as MFA and SSO are also supported. cloud application security In addition, with Aptible, you don’t have to worry about compliance because it automatically implements requirements from various security regulation frameworks including HIPAA, HITRUST, and SOC 2. By automating these tasks and streamlining processes into a unified PaaS, Aptible saves developers time and mental energy. They are freed up to focus on writing code and building products rather than Ops activities. This drives faster iteration, innovation, and release velocity. Deploying Your First Application on Aptible You can deploy your app using a custom code or a starter template from Aptible. In this section, we’ll focus on deploying your custom code. The explanation for working with a template comes later, but the steps are essentially the same. The requirements: A Git repository with your application code. You need to provide a Dockerfile, which will be used to build the app’s container image and then to run it on Aptible’s infrastructure. Your apps will only be able to receive traffic via HTTP or TCP, not UDP. However, connections to UDP services such as DNS and SNMP are still allowed. Aptible does not store app data with persistence. If you must, you need a third-party solution or a database. Once you have the requirements, the following are the steps to deploy your app. Open Aptible in your browser and log in to your account. To start the process, select ‘Deploy with Git Push.’ Aptible uses Public Key Authentication. So, on the next screen, you’ll be prompted to add an SSH key. This is tied to the user, and Aptible uses this to authenticate you when you push your code. The following key types are supported: ssh-rsa, ssh-ed25519, ssh-dss. If you don’t have an existing key, check out the documentation for how to generate one using the code below: ssh-keygen -t ed25519 -C "your_email@example.com" The next step requires that you set up the environment by selecting the deployment stack, with regional availability covering the Americas, Europe, and Asia/Pacific. Aptible provides both shared and dedicated stacks. The latter is available at higher pricing tiers. When you push your code to Aptible, select the ‘Custom Code’ option, and follow the instructions to add Aptible’s Git Server. It will typically be in the following format: git remote add aptible git@beta.aptible.com: test1234/test1234.git After that, you need to provision the database and configure the app. This includes selecting the database handle and environment variables. In the final steps, you’ll deploy your code, which will enable you to view logs in real-time, and then make your app live on the internet. Alternatively, you can deploy your code using a starter template. Aptible has templates based on Ruby on Rails, NodeJS, Django, and Laravel available. Each requires similar steps to how you deploy your custom code. You still have to have Git installed, add an SSH key, and set up your environment by selecting your stack. After going through those steps, upon reaching the point where you have to push your code to Aptible, simply select the template you want instead of ‘Custom Code.’ From then on, Aptible takes over filling in the information on the required databases, services, and configurations based on the template you have selected. Once you have gone through those processes, simply save and deploy the code, then launch your app. Conclusion Aptible is a powerful and convenient platform that can help you host your applications in the cloud without worrying about infrastructure, compliance, or security. In this article, you have learned how to deploy your first secure containerized application using Aptible. You have seen how to create an app, deploy it from a Docker image or a Git repository, expose it to the internet using endpoints, and scale and manage it using the dashboard or the CLI tool. To learn more about Aptible and its features, check out and read . And you can always contact our support team if you have any questions or issues. , the website the documentation Feature image source: Unsplash

Getting Started With Aptible to Deploy Your First Secure Containerized Application

আপনার প্রথম সুরক্ষিত কন্টেইনারাইজড অ্যাপ্লিকেশন স্থাপন করার জন্য Aptible দিয়ে শুরু করা

Erste Schritte mit Aptible zur Bereitstellung Ihrer ersten sicheren Containeranwendung

Comenzando con Aptible para implementar su primera aplicación segura en contenedores

Premiers pas avec Aptible pour déployer votre première application conteneurisée sécurisée

अपना पहला सुरक्षित कंटेनरीकृत एप्लिकेशन परिनियोजित करने के लिए उपयुक्त के साथ शुरुआत करना

初めての安全なコンテナ化アプリケーションをデプロイするための Aptible の使用開始

첫 번째 안전한 컨테이너화된 애플리케이션 배포를 위한 Aptible 시작하기

Introdução ao Aptible para implantar seu primeiro aplicativo seguro em contêiner

Начало работы с Aptible для развертывания вашего первого безопасного контейнерного приложения

İlk Güvenli Konteynerli Uygulamanızı Dağıtmaya Aptible'ı Kullanmaya Başlayın

Bắt đầu với Apible để triển khai ứng dụng được đóng gói an toàn đầu tiên của bạn

开始使用 Aptible 部署您的第一个安全容器化应用程序

Protecting sensitive information throughout the development lifecycle is no easy feat. Aptible Enclave, a pivotal component of the Aptible platform, offers a compelling solution. In this article, we will explore how Aptible Enclave takes data security to the next level by providing a secure infrastructure for database management in processes. DevOps Security with Aptible Enclave Ensuring that sensitive information remains secure throughout the entire development cycle can be challenging. This is where Aptible Enclave steps in to bridge the gap between DevOps and data security. Core features of Aptible Enclave: . Aptible Enclave offers a secure platform for managing databases, which are often repositories of highly sensitive information. It ensures that data is protected at rest and in transit, reducing the risk of data breaches and leaks. Secure Database Management . Enclave leverages encryption to secure data both at rest and in transit. This means that even if a malicious actor gains access to the underlying infrastructure or network, the data remains encrypted and unreadable without the proper decryption keys. End-to-End Encryption . Enclave provides robust access control mechanisms to limit who can access the data and what actions they can perform. This fine-grained control helps prevent unauthorized access and potential security incidents. Access Control . Enclave allows you to define and enforce security policies for your databases. This automation ensures that security best practices are consistently followed, reducing the chances of human error. Automated Security Policies . Aptible Enclave is designed with compliance in mind, making it easier for organizations to meet regulatory requirements, such as GDPR, HIPAA, and SOC 2. It also offers auditing capabilities to track and monitor activities related to your data. Compliance and Auditing . Enclave seamlessly integrates with your DevOps workflow, making it easy to incorporate secure data management practices into your application development and deployment processes. Code Integration Code examples to understand the impact: To better understand the impact of Aptible Enclave, let's consider some code examples: # Setting up a secure connection to an Enclave-managed database
import aptible

# Define your Enclave credentials
enclave_credentials = {
    "access_key_id": "your-access-key",
    "secret_access_key": "your-secret-key",
}

# Connect to your Enclave database
db = aptible.enclave.Database(
    id="your-database-id",
    credentials=enclave_credentials
)

# Now, you can interact with your database securely
result = db.execute("SELECT * FROM sensitive_data") In this example, we use the Aptible Enclave Python library to establish a secure connection to an Enclave-managed database. The code ensures that data access is properly authenticated and encrypted. Isolation and encryption Aptible Enclave isolates databases from external access, providing an additional layer of security. Moreover, data in transit and at rest is encrypted to protect it from unauthorized access. Here's an example of isolating a database with Aptible Enclave: version: "2"
services:
  web:
    image: your-app-image:latest
  database:
    image: aptible/database:postgresql-14
    command: postgres -D /data
    volumes:
      - /var/data
    ports:
      - "5432:5432" In this example, we define a service for a database that uses Aptible Enclave. It specifies the image, the command, and the volume, isolating the database and encrypting the data. Automated backups and failover Data backups are crucial for data recovery and business continuity. Aptible Enclave offers automated backup processes to minimize the risk of data loss. Additionally, it supports automated failover, ensuring the high availability of databases. Here's an example of configuring automated backups in : Aptible Enclave version: "2"
services:
  web:
    image: your-app-image:latest
  database:
    image: aptible/database:postgresql-14
    command: postgres -D /data
    volumes:
      - /var/data
    ports:
      - "5432:5432"
  backups:
    image: aptible/database:backups In this example, we introduce a service dedicated to backups, ensuring that data is protected and can be restored as needed. Compliance features For organizations in regulated industries, compliance is non-negotiable. Aptible Enclave simplifies compliance management through features like automated compliance checks, audit logging, and detailed reporting. Here's an example of defining compliance checks in Aptible Enclave: version: "2"
comply:
  containers:
    - name: web
      command:
        - "bundle"
        - "exec"
        - "rails"
        - "server"
      env:
        - name: RAILS_ENV
          value: production
      ports:
        - 3000 In this example, we define compliance checks for a web service, ensuring that the application adheres to regulatory standards. Scalability Aptible Enclave allows for seamless database scaling to accommodate application demands. As your application grows, you can adjust the database infrastructure with confidence, knowing that data security remains intact. Here's an example of scaling a database with Aptible Enclave: version: "2"
services:
  web:
    image: your-app-image:latest
  database:
    image: aptible/database:postgresql-14
    command: postgres -D /data
    volumes:
      - /var/data
    ports:
      - "5432:5432"
    scale:
      count: 3 In this example, we specify a scale count of 3, indicating that the database can be scaled to accommodate the growing application load securely. Conclusion Aptible Enclave is a powerful solution that enhances data security in DevOps. By providing a secure infrastructure for database management it allows organizations to embrace the speed and agility of without sacrificing the protection of sensitive data. In many industries where data security and compliance are non-negotiable, Aptible Enclave becomes a critical tool for success. DevOps practices

Aptible Enclave: Elevating Data Security in DevOps Environments

When deciding to own a house, you have two options. The first option would be to buy a fully built house, leaving you to decorate as you please. The second option is purchasing a plot of land, building from scratch, and handling interior decoration. If you need this house within a limited time, you will most likely choose the first option. In software development, that first option can be likened to . Platform as a Service Platform as a Service (PaaS) is a cloud computing model that provides developers with a platform to create, run, and manage applications without worrying about the complexity of underlying infrastructure management. With PaaS, developers can focus on application development and deployment. At the same time, the PaaS provider takes care of the underlying infrastructure, such as servers, storage, and networking, making it easier and faster to develop and deploy applications. PaaS providers offer developers a comprehensive environment for developing and deploying their software applications in the cloud. This cloud environment includes tools for building, deploying, and scaling applications. With these tools, developers can focus on delivering value without worrying about infrastructure. This article will discuss platform as a service and explore its software development benefits. In this article, you will learn about two PaaS providers - Aptible and Heroku, while highlighting their differences. At the end of this article, your development team will be able to make informed decisions about which PaaS provider best suits their application's needs. What Is PaaS? As earlier explained with the analogy, PaaS offers developers a fully equipped cloud environment to build applications without worrying about the infrastructure - servers, storage, and networking. house The entire infrastructure is delivered via the cloud, and developers only have to focus on writing the application code. PaaS helps companies avoid the expense and hassle of purchasing, setting up, and managing hardware and software needed for application development. These companies can subscribe to a PaaS provider and use the pay-as-you-go model, allowing them to only pay for the resources they use. Platform as a service is one of the three main categories of cloud computing services. Infrastructure as a Service and Software as a Service are two other cloud computing models. The table below shows the differences between these three categories. Category Description Examples Infrastructure as a Service (IaaS) IaaS is the most fundamental cloud computing service. When you use IaaS, you can rent servers, virtual machines, storage, networks, and operating systems from a cloud provider on a pay-as-you-go basis. Amazon Web Services (AWS), Google Compute Engine (GCE), Microsoft Azure, Platform as a Service (PaaS) PaaS platforms help developers build applications. PaaS providers typically include the same services as IaaS offerings but also high-level tools and components to help developers build applications faster. Aptible, Heroku, Google App Engine, Microsoft Azure, OpenShift. Software as a Service (SaaS) The SaaS model allows users to access software applications through the internet on a subscription basis, providing on-demand availability. Using SaaS, cloud providers offer hosting and infrastructure services and handle maintenance such as software updates and security patches. Users connect to the application over the internet, usually with a web browser on their phone, tablet, or PC. Google Workspace, Salesforce, Dropbox, MailChimp, DocuSign, Slack Benefits of PaaS In the fast-paced world of software development, utilizing platforms that allow you to focus on your core business is a no-brainer. PaaS offers a lot of benefits to developers and companies. Some of these benefits are: : Just like our fully built house analogy, PaaS offers development teams a platform that is always ready, updated, and scalable. Infrastructure availability : Companies can save costs by relying on PaaS platforms because they offer a pay-as-you-go model. This payment model allows companies to only pay for the resources they use, saving companies the cost of buying, configuring, and maintaining all the hardware and software. Cost savings : You would agree that buying an already-built house can save you the time it would take to build from scratch. In the same way, development teams could save a lot of time by using PaaS platforms. Reduced development time With a pre-built, up-to-date platform, you can focus on writing code and delivering value to your customers rather than worrying about the underlying infrastructure for your application. Aptible According to the analogy, we established that in order to own a house in the shortest amount of time, the best option would be to buy one. In this case, is that house. house Aptible Aptible is a PaaS that provides developers with a ready-to-use cloud environment for deploying their application or API. This cloud environment handles everything from scaling to database management and even metrics & logs of your application. Aptible, like every other PaaS, offers deployment, infrastructure scalability, and monitoring to development teams. However, Aptible's outstanding features are its commitment to reliability and security & compliance. Development teams have various options for deploying applications using Aptible. They can utilize the Aptible dashboard via the Graphic user interface, the command line interface, or even Infrastructure as Code - Terraform. Heroku If Aptible is the for developers looking for a ready-to-use cloud environment, then can be considered another impressive in the world of PaaS. go-to house Heroku property Heroku is another PaaS provider that lets companies build, deliver, monitor, and scale apps. It is a fully managed cloud platform with integrated data services and a powerful ecosystem for deploying and running modern web or mobile applications. Beyond apps, data lies at the heart of any significant application. Heroku recognizes this and provides a secure, scalable database-as-a-service with various developer tools. The goal is to offer developers immediate access to a scalable, highly available database that complements their development style. Comparison Between Aptible and Heroku By now, you should be convinced of the importance of PaaS and its relevance in software development. You should also have a good understanding of Aptible and Heroku. This section will compare both PaaS offerings and highlight their differences. Below is a table comparing Aptible and Heroku: Feature Aptible Heroku Service type Platform as a Service (PaaS) Platform as a Service (PaaS) Cloud environment Offers a cloud environment optimized for application and API deployment. Provides a cloud platform suitable for a wide range of applications and services. Deployment options Offers deployment options through the Aptible Dashboard, Command Line Interface (CLI), and Infrastructure as Code (Terraform). Provides deployment options through the "Deploy to Heroku" button, and Heroku CLI. Additionally, it also supports Git-based deployments for streamlined code management. Application scaling Supports application scaling for handling increased workloads. Allows applications to scale horizontally to accommodate growing user demands. Database management Offers support for database management within the cloud environment. Provides built-in database services and supports third-party databases for data storage. Monitoring Aptible offers application monitoring tools, ensuring they remain secure and operational. Heroku integrates monitoring and logging services, providing insights into application performance and stability. Integration with other services Integration options with external services are limited. Heroku offers an extensive ecosystem of add-ons and services that can seamlessly integrate with applications. Developer focus Places a strong emphasis on a developer-centric experience, aiming to simplify app deployment, management, and scaling. Offers a developer-centric platform that focuses on enabling developers to create applications efficiently with support for multiple programming languages. Language support Aptible supports various programming languages, enabling developers to work with their preferred language. Heroku is compatible with various programming languages, including Node.js, Ruby, Java, Python, and more, offering flexibility in language choice. Security & Compliance Prioritizes security and compliance, making it suitable for applications with strict security requirements. Maintains a security-focused approach, ensuring application and data security in the cloud environment. Scalability Suitable for businesses of various sizes, offering the capability to scale applications to meet specific requirements. Designed for scalability, Heroku is suitable for startups and enterprises, enabling seamless scaling of applications as they grow. Data services Aptible provides a rich ecosystem of managed data services, facilitating data management and storage for applications. Heroku offers a database-as-a-service approach with data management tools, enabling efficient data handling. Enterprise features Provides enterprise-level controls for advanced management and support for portfolios of applications. Offers enterprise-level support and features, making it suitable for large organizations with complex application needs. Pricing model Utilizes a subscription-based pricing model, making it predictable for budgeting. Adopts a flexible pricing model that allows businesses to pay only for the resources they consume. Integration with Salesforce Limited integration with Salesforce and other enterprise platforms. Provides seamless integration with Salesforce, enabling data synchronization and enhanced capabilities for CRM engagement. Although Aptible and Heroku are both PaaS offerings, these platforms differ. One of the most significant differences is that Aptible is specifically designed for companies that need to meet strict security & compliance requirements. Aptible complies with several industry standards, including HIPAA, PCI DSS, and SOC 2 Type II. On the other hand, Heroku is not explicitly designed for companies that need to meet these requirements. Another difference between Heroku and Aptible is that Aptible uses Docker containers to deploy applications. On the other hand, Heroku uses a buildpack system - a set of scripts used to compile applications and prepare them for deployment. Due to the buildpack system, developers are limited to the types of applications that can be deployed on Heroku. Aptible, on the other hand, allows developers to deploy applications written in any programming language. This feature makes Aptible a more flexible option regarding programming language support. Overall, Heroku and Aptible are both good PaaS providers that offer a variety of features to help developers deploy and manage their applications. The best platform for you will depend on your specific needs and requirements. If you are looking for a platform specifically designed for companies that must meet strict security and compliance requirements, then Aptible is an excellent option. If you are looking for a platform that is easy to use and offers various features, then Heroku is a good option to consider. Conclusion Building applications has never been easier with the aid of PaaS providers such as Aptible and Heroku. These platforms offer a variety of features to help developers deploy and manage their applications in ample time. It would be best to consider using a PaaS provider when deploying an application. Relying on PaaS can save you the time and stress of building and managing infrastructure simultaneously. You may also want to consider Aptible or Heroku, depending on what you specifically need and want. You can learn more about Aptible and Heroku by reading their documentation: Aptible Documentation Heroku Documentation You can also learn about PaaS by reading the following articles: What is Platform as a Service (PaaS)? Platform as a service (PaaS) Explained

PaaS: Aptible vs Heroku

Stories, News & Mentions about APTIBLE

Categories

Trending Topics

Stories, News & Mentions about APTIBLE

Aptible’s Stories on HackerNoon

Categories

Trending Topics