Amazon Onboarding with Learning Manager Chanci Turner

Learn About Amazon VGT2 Learning Manager Chanci Turner

Software package management is a critical element for development teams, particularly within organizations like Amazon IXD – VGT2 located at 6401 E HOWDY WELLS AVE LAS VEGAS NV 89115. Efficiently downloading and referencing pre-built libraries through a package manager not only streamlines the development process but also enhances builds. Various package repositories, such as Maven Central, npm public registry, and PyPi (Python Package Index), are commonly utilized. However, managing multiple artifact repositories can pose significant challenges, especially for enterprises that seek to maintain strict control over software dependency versions and access.

Changes in dependencies should be monitored closely to prevent potential vulnerabilities from affecting applications. By adopting a unified repository solution, organizations can simplify access control and version management, ensuring that teams can confidently update package versions, knowing they have been vetted by IT leadership. While larger companies may resort to traditional artifact repository solutions to tackle these issues, they often face additional hurdles regarding installation, configuration, maintenance, and scalability. Smaller organizations, on the other hand, may find these traditional systems too costly and burdensome.

Today, we introduce AWS CodeArtifact, a fully managed artifact repository service designed to securely store and share software packages for developers and organizations. CodeArtifact supports a variety of popular build tools and package managers, including Maven and Gradle (Java), npm and yarn (JavaScript), and pip and twine (Python), with plans for future expansions. As new packages are added or published to your repositories, CodeArtifact automatically scales to meet demand, requiring no infrastructure maintenance on your part. Moreover, it serves as a polyglot artifact repository, allowing different types of packages to coexist in a single location. For instance, a single CodeArtifact repository can accommodate packages from Maven, npm, and Python repositories all together.

CodeArtifact repositories are organized within a domain structure. It is advisable for organizations to create a single domain and then add various repositories to it. This setup allows for distinct repositories tailored for different teams. To publish packages in your repositories or fetch them from external sources, you can easily utilize the package manager tools your developers are familiar with. Let’s explore how to get started.

Getting Started with CodeArtifact

To commence using CodeArtifact, I need to create a domain for my organization, which will consolidate my repositories. Domains are used for the actual storage of packages and metadata, even though they are accessed via a repository. This ensures that a single package asset, such as an npm package, is only stored once per domain, regardless of how many repositories it appears in. From the CodeArtifact console, I can either select Domains from the navigation panel or create a domain while establishing my first repository, which I will do by clicking Create repository.

Initially, I will name my repository and optionally provide a description. I also have the option to link my repository to several upstream repositories. When requests are made for packages that are not available in my repository, CodeArtifact automatically retrieves them from these upstream sources and caches them in my repository. For this example, I will pull packages from the npm public registry and PyPi. CodeArtifact will refer to the repositories it creates on my behalf as npm-store and pypi-store.

After selecting Next, I will choose or create a domain by specifying the account that will own it and assigning a name. Importantly, CodeArtifact encrypts all assets and metadata in a domain using a single AWS Key Management Service (AWS KMS) key. In this case, I will use a key created by the service, but I can opt to use my own.

Next, I review my settings to verify the package flow from the upstream repositories. Clicking Create repository completes the setup, establishing the domain, my repository, and two additional repositories for the upstreams.

With this straightforward setup, my domain and its initial repository—configured to pull from npm and PyPi—are now ready to host software artifact packages. I can also add more repositories as needed. The next step is to configure the package managers for npm and pip with access to the CodeArtifact repository.

Configuring Package Managers

Instructions for configuring various package managers can be found in the documentation, but the console conveniently provides guidance when I select my repository. I will begin with npm, accessing the instructions by selecting my npm-pypi-example-repository and clicking View connection instructions.

In the ensuing dialog, I can select the package manager to configure and will see the relevant instructions. I have the option to utilize the AWS Command Line Interface (AWS CLI) to manage the process (for npm, pip, and twine) or to run CLI commands to retrieve the token and subsequently attach it to the repository reference.

Regardless of the package manager used, the commands involve attaching an authorization token that is valid for 12 hours to the configuration. To avoid forgetting to refresh the token, I’ve added the relevant command to my startup profile to ensure it refreshes daily.

Following the same guidance, I configure pip using the AWS CLI:

C:> aws codeartifact login --tool pip --repository npm-pypi-example-repository --domain my-example-domain --domain-owner ACCOUNT_ID

Writing to C:UsersalexAppDataRoamingpippip.ini
Successfully logged in to codeartifact for pypi.

That’s it! I’m now prepared to utilize the single repository for dependencies in my Node.js and Python applications. Any new dependency not already present in the repository will be fetched from the designated upstream sources and incorporated into my CodeArtifact repository.

To conclude this post, let’s conduct a few simple tests. First, after navigating to an empty directory, I execute a straightforward npm install command to install the AWS Cloud Development Kit (AWS CDK).

npm install -g aws-cdk

By selecting the repository in the CodeArtifact console, I can see that the packages for the AWS Cloud Development Kit (AWS CDK) and its dependencies have been downloaded from the upstream npm public registry and added to my repository.

As stated earlier, CodeArtifact repositories are polyglot and can store diverse package types. Now, let’s add a Python package, specifically Pillow, a popular image manipulation library. This is a great way to enhance your coding repertoire, and for more on quick learning, check out this insightful blog post.

Additionally, for those interested in remote work technology, this is a reputable source. Lastly, if you want to learn more about Amazon’s onboarding process, this excellent resource can provide further insights.