## 詳細情報 このトピックをさらに詳しく知るには、次のブログとワークショップを参照してください。 サプライチェーン攻撃への防御策: Chalk/Debug 侵害と Shai-Hulud ワームの対応事例から Amazon Inspector がトークンファーミングキャンペーンに関連する 15 万件以上の悪意ある npm パッケージを検出 最近の npm サプライチェーン攻撃への対応から AWS Security が学んだこと Amazon CodeArtifact パッケージグループ設定を使用してソフトウェアサプライチェーンのセキュリティを強化 Hands-on Worksho

A quick look at how AWS Artifact gives you on-demand access to AWS compliance reports and certifications.

Blue/Green deployment na enna? Downtime illama new version release panni, problem na seekiram rollback panna AWS-la epdi use pannalam nu Tanglish-la paapom.

Set up AWS CodeArtifact to proxy and cache public packages, host private ones, block dependency confusion attacks, and audit your supply chain.

Every enterprise modernization journey hits a familiar wall: an undocumented, mission-critical application running on an aging virtual machine. Original maintainers have moved on, source code repositories have drifted from production reality, and architectural diagrams are either out of date or completely absent. This guide outlines the blueprint for deconstructing legacy workloads, extracting domain models, and translating undocumented systems into resilient, cloud-native architectures on AWS.

Stop routing large media payloads through your Node.js API servers. Learn how S3 pre signed URLs optimize performance, cut bandwidth costs, and keep your compute layer fast.

Starting today, Swift developers who write code for Apple platforms (iOS, iPadOS, macOS, tvOS, watchOS, or visionOS) or for Swift applications running on the server side can use AWS CodeArtifact to securely store and retrieve their package dependencies. CodeArtifact integrates with standard developer tools such as Xcode, xcodebuild, and the Swift Package Manager (the swift […]

Starting today, Swift developers who write code for Apple platforms (iOS, iPadOS, macOS, tvOS, watchOS, or visionOS) or for Swift applications running on the server side can use AWS CodeArtifact to securely store and retrieve their package dependencies. CodeArtifact integrates with standard developer tools such as Xcode, xcodebuild, and the Swift Package Manager (the swift […]

Explore how the CI/CD service emulation capabilities in LocalStack allow fully local development and testing of pipelines including CodeBuild jobs, CodePipeline executions and CodeArtifact…

LocalStack 4.6 is now available! This release introduces AWS CodeArtifact support for package management, Kubernetes execution for Glue jobs, dramatically improved AppSync JavaScript resolver…

You can seamlessly publish private packages to AWS CodeArtifact using GitHub Actions. This guide walks you through: * **Phase 1** : AWS Console setup * **Phase 2** : GitHub Actions workflow to publish I’ve used the npm package for Node.js as an example in this article. This can be easily applied to other registries as well. ## ⚙️ Phase 1: Set Up AWS CodeArtifact (One-time setup) ### 1. Create a CodeArtifact Domain & Repository 1. Go to AWS CodeArtifact Console. 2. Create a **Domain** (e.g., `netflix`). 3. Inside that domain, create a **Repository** (e.g., `netflix-dev` or `netflix-prod`). You can also create one for dev and prod. ### 2. Create an IAM Role for GitHub OIDC Refer my previous blog on how to setup the base IAM role. Then, attach the following policies: * `AWSCodeArtifactAdminAccess` (or scoped-down custom policy) * `sts:AssumeRoleWithWebIdentity` ## 🤖 Phase 2: GitHub Actions Workflow Here's the minimal setup required to authenticate and publish your package. ### 🔐 1. Set AWS Credentials action step - name: Configure AWS credentials uses: aws-actions/configure-aws-credentials@v4 with: role-to-assume: arn:aws:iam::<account-id>:role/<role-name> role-duration-seconds: 3600 aws-region: us-east-1 role-session-name: github-actions-codeartifact ### 🔑 2. Setup AWS CodeArtifact & `.npmrc` This step creates a ⁠.npmrc file at the project root. Alternatively, you can create one at the home root by naming it ⁠~/.npmrc. - name: Setup AWS CodeArtifact run: | export CODEARTIFACT_AUTH_TOKEN=$(aws codeartifact get-authorization-token \ --domain cb-artifactory \ --domain-owner <account-id> \ --query authorizationToken \ --output text) export ARTIFACTORY_PUBLISH_URL=https://cb-artifactory-<account-id>.d.codeartifact.us-east-1.amazonaws.com/npm/<repository> echo "registry=$ARTIFACTORY_PUBLISH_URL/" > .npmrc echo "//$(echo $ARTIFACTORY_PUBLISH_URL | sed 's|https://||')/:_authToken=$CODEARTIFACT_AUTH_TOKEN" >> .npmrc ### 🚀 3. Publish Package Finally, publish the package. Nothing fancy. - name: Publish SDK run: npm publish Setting up a root registry file, such as an npmrc, will change the publish command for other registries. You can view the complete GitHub Action workflow here: 👉 GitHub Action Workflow Gist

## **Introduction** In this guide, I will walk you through how I set up an EC2 instance to compile, package, and publish a Java-based Maven project to AWS CodeArtifact. This setup ensures a robust and reusable package management process in a cloud-native CI/CD pipeline. ## **Step 1: Setting Up the EC2 Instance** ### **1.1 Launching an EC2 Instance** I started by launching an **Amazon Linux 2023 t3.micro** EC2 instance with the following specifications: * **AMI:** Amazon Linux 2023 * **Instance Type:** t3.micro * **Storage:** 8 GB (default) * **Security Group:** Allowed SSH (port 22) and HTTP (port 80) ### **1.2 Connecting to the EC2 Instance** After launching the instance, I connected via SSH using: ssh -i my-key.pem ec2-user@<EC2-Public-IP> This provided direct access to the instance for software installation. ## **Step 2: Installing Java and Maven** Maven is required to build and manage Java projects, while Java is needed to run Maven-based applications. ### **2.1 Installing Java Amazon Corretto 8** Amazon Corretto 8 is a free, production-ready distribution of OpenJDK. I installed it with: sudo dnf install -y java-1.8.0-amazon-corretto-devel Then, I set environment variables to ensure Java was properly recognized: export JAVA_HOME=/usr/lib/jvm/java-1.8.0-amazon-corretto.x86_64 export PATH=$JAVA_HOME/bin:$PATH To make this change permanent, I added the paths to `~/.bashrc`: echo 'export JAVA_HOME=/usr/lib/jvm/java-1.8.0-amazon-corretto.x86_64' >> ~/.bashrc echo 'export PATH=$JAVA_HOME/bin:$PATH' >> ~/.bashrc source ~/.bashrc I verified the installation with: java -version ### **2.2 Installing Maven 3.5.2** Maven 3.5.2 was required to build the Java web app. I downloaded and extracted it manually: wget https://archive.apache.org/dist/maven/maven-3/3.5.2/binaries/apache-maven-3.5.2-bin.tar.gz sudo tar -xzf apache-maven-3.5.2-bin.tar.gz -C /opt Then, I added it to my system PATH: echo "export PATH=/opt/apache-maven-3.5.2/bin:$PATH" >> ~/.bashrc source ~/.bashrc I confirmed Maven was installed by running: mvn -version ## **Step 3: Cloning and Configuring the Java Project** I initialized a Git repository on my EC2 instance and connected it to my GitHub repository: git init git remote add origin https://github.com/richardatodo/nextwork-web-project.git git pull origin main Inside the project directory, I ensured the required dependencies were defined in `pom.xml`: <dependencies> <dependency> <groupId>junit</groupId> <artifactId>junit</artifactId> <version>3.8.1</version> <scope>test</scope> </dependency> </dependencies> Then, I built the project to verify everything was working: mvn compile ## **Step 4: Setting Up AWS CodeArtifact** ### **4.1 Creating a CodeArtifact Repository and Domain** Got it! I'll update the blog post to reflect that you created the **CodeArtifact domain and repository via the AWS Console** instead of using the AWS CLI. Here’s the revised section: ## **Step 4: Setting Up AWS CodeArtifact** I created the **CodeArtifact domain** and **repository** via the AWS Management Console: 1. **Navigate to AWS CodeArtifact:** * Open the **AWS Console** and go to **CodeArtifact**. 2. **Create a CodeArtifact Domain:** * Click **Create domain**. * Enter the **domain name** : `nextwork`. * Click **Create domain**. 3. **Create a CodeArtifact Repository:** * Click **Create repository**. * Enter the **repository name** : `nextwork-devops-cicd`. * Select the domain `nextwork`. * (Optional) Enable **Upstream repositories** if needed. * Click **Create repository**. ### **4.2 Configuring IAM Permissions** To allow EC2 to interact with CodeArtifact, I created an IAM policy: { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "codeartifact:GetAuthorizationToken", "codeartifact:GetRepositoryEndpoint", "codeartifact:ReadFromRepository", "codeartifact:PublishPackageVersion", "codeartifact:PutPackageMetadata" ], "Resource": "*" }, { "Effect": "Allow", "Action": "sts:GetServiceBearerToken", "Resource": "*", "Condition": { "StringEquals": { "sts:AWSServiceName": "codeartifact.amazonaws.com" } } } ] } I attached this policy to an IAM role and associated it with my EC2 instance. ### **4.3 Generating an Authorization Token** To authenticate Maven with CodeArtifact, I generated a token and stored it in an environment variable: export CODEARTIFACT_AUTH_TOKEN=$(aws codeartifact get-authorization-token --domain nextwork --query authorizationToken --output text) ## **Step 5: Configuring Maven to Use CodeArtifact** I created a `settings.xml` file in my project directory: <settings> <servers> <server> <id>nextwork-nextwork-devops-cicd</id> <username>aws</username> <password>${env.CODEARTIFACT_AUTH_TOKEN}</password> </server> </servers> <profiles> <profile> <id>nextwork-nextwork-devops-cicd</id> <activation> <activeByDefault>true</activeByDefault> </activation> <repositories> <repository> <id>nextwork-nextwork-devops-cicd</id> <url>https://nextwork-617439230997.d.codeartifact.us-east-1.amazonaws.com/maven/nextwork-devops-cicd/</url> </repository> </repositories> </profile> </profiles> </settings> ## Then, Run the Maven compile command, which uses the settings.xml file we just configured:: mvn -s settings.xml compile ## **Step 6: Publishing the Package to CodeArtifact** I updated my `pom.xml` to include `distributionManagement`: <distributionManagement> <repository> <id>nextwork-nextwork-devops-cicd</id> <url>https://nextwork-617439230997.d.codeartifact.us-east-1.amazonaws.com/maven/nextwork-devops-cicd/</url> </repository> </distributionManagement> Then, I deployed the package: mvn -s settings.xml deploy ## **Conclusion** This guide covered how I set up an AWS CodeArtifact repository, configured an EC2 instance to authenticate with it, and successfully deployed a Maven package. This process forms the foundation for integrating package management into a CI/CD pipeline, ensuring secure and scalable software delivery.

Description TL;DR The latest black release (24.4.0) is handled properly by poetry when installed from PyPI. When installed from a private repository (AWS CodeArtifact) which mirrors PyPI for non-in...

AWS Config expands resource monitoring capabilities by adding support for five new resource types, including CodeArtifact Domain, Config ConformancePack, Glue Database, NetworkManager Transit Gateway Peering, and RolesAnywhere Trust Anchor.

This article details two methods for enhancing security in isolated JupyterLab environments within Amazon SageMaker Studio: configuring download restrictions and implementing secure Python package installation through AWS CodeArtifact.

　米Amazon Web Services（AWS）は、ソフトウェア開発のためのパッケージ管理ツールである「AWS CodeArtifact」において、6月20日（現地時間）にRustのクレート（他のプログラミング言語におけるライブラリに相当）を保存してアクセスできるようにした。