Meta issue for research resource naming restrictions in each cloud provider

[viniciusdc]

This is needed to reassure some of our project naming conventions and update any missing constraint present on #761

[viniciusdc]

Naming convention

When you create a new resource on each one of the cloud providers, you will have to provide properties such as a name, project id, bucket, etc... for the resource. As Qhub mainly uses the project name from config to populate those attributes, we must ensure that for such cases, the resource attribute/name meets the following conventions (unless specified differently in the documentation for creating that resource):

Provider	Merged Convention	Source
AWS	- Must be between 3-47 characters in length; - Must begin with an alphanumeric character, and must only contain alphanumeric lowercase characters, dashes, and underscores; - The name cannot start with AWS or aws.	- EKS cluster name - AWS resource group name - S3 bucket
GCP	- Be 1-63 characters in length; - Comply with RFC 1035 conventions; - The first character must be a lowercase letter, and all the following characters must be hyphens, lowercase letters, or digits, except the last character, which cannot be a hyphen.	- google service account id; - google compute network name - google compute subnetwork name
Azure	- Between 3 and 16 characters long; - Start and end with alphanumeric; - lowercase alphanumerics	- AKS cluster name - Storage Account name - Resource Group name - container registry name
DO	- Could not find any conventions.	- NA

[iameskild]

@viniciusdc thanks a lot for the detailed table!!

I think it might be worth including the following restrictions as well:

• AWS
  • "Bucket names must not start with the prefix xn--."
  • "Bucket names must not end with the suffix -s3alias."

Otherwise this looks great :)

[viniciusdc]

@viniciusdc thanks a lot for the detailed table!!

I think it might be worth including the following restrictions as well:

• AWS

  • "Bucket names must not start with the prefix xn--."
  • "Bucket names must not end with the suffix -s3alias."

Otherwise this looks great :)

Hi @iameskild thanks!!! I only looked for the terraform state bucket but didn't check this one. I will add those to the PR directly. 😄

[viniciusdc]

The only thing that ended up not being added was the restriction for AWS that @iameskild suggested above, once we work on #1267 we can add the missing conventions. For now, I will let this as a comment on the mentioned issue and close this one as the research was used to update #761