In order to get the most of AWS Blu Insights features, the uploaded artefacts should be properly extracted. See this page for more details.
You need to upgrade your account. Contact us to discuss this further, see the certification page.
Yes. If your initial archive contained embedded ZIP files, AWS Blu Insights will warn you on the Statistics page and will propose a feature to extract them. The project metrics are also updated at the end of the extraction.
No. If you upload files without extensions (which is frequent in Mainframe, iSeries and OpenVMS projects), you can leverage the classification to identify the underlying programming languages. The dependencies and cyclomatic complexity analysis will also rely on this feature.
We allow an import of less than or equal to 10GB. See below if your codebase is larger than that.
We recommend using 7-zip to generate an archive based on the 7z format. It has an better compression ratio than native zip tools.
We recommend you to manually split your codebase into several archives. Once the archives generated, follow these steps:
Yes. This can be done through customized labels and descriptions which can be manually inserted by selecting files or using the bulk import based on Excel files.
It is possible to preview almost all file types (not MS Office files, e.g. .xlsx, Docx…) by clicking on their path in the tables or by clicking on the “View” icon when selected.
Yes. Navigate to Assets > Statistics, click on the “…” button on the upper right corner of the page and select “Download files”. Some browsers may block the download so you need to explicitly allow pop-ups.
If your project contains files having the same names, a tab called Homonym will list them on the Statistics page.
In Assets > Workspace, it is possible to search for words or regular expressions in the project files using the Search button (shortcut Ctrl+Shift+f). Read more.
This can be done in Homonyms page by applying the ‘Homonyms – Identicals’ filter or typing “homonym types = ‘identicals'” in the filter field.
The largest codebase we tested contains 500 000 files cumulating 150 millions of code. If you get a larger codebase, please tell us!
Yes, you only need to generate a presigned URL from your zip/7z file and paste it into AWS Blu Insights.
You can create a codebase project from a legacy source code hosted in an S3 bucket by following these two steps:
NB: Make sure that the presigned URL has not expired before creating the new project.
AWS Blu Insights needs a presigned URL to get access and copy the zip/7z file from the S3 bucket to the AWS Blu Insights infrastructure. Presigned URL is a temporary, secure way to access files inside S3 bucket via a signed URL generated and managed by AWS.
Yes. AWS Blu Insights copies the artefacts from S3 bucket to the infrastructure during the project creation.
No permissions are required. All you have to do is generating the presigned URL and pasting it into AWS Blu Insights while creating a new project. Make sure you use the URL before it expires.
No. Once AWS Blu Insights creates the project, it never accesses again the bucket, so you do not need to keep the artefacts in S3 bucket after the project creation.
The issue pertains to the customer's environment, not AWS Blu Insights itself. The account lacks sufficient permissions, and the customer's network firewall policy is limiting file uploads to the Blu Insights SaaS endpoint.