#aws Checking here before logging a bug. I am facing two issues while creating VPC using awsx. • Firstly, the naming convention of nat gateway, endpoint and internet gateway can be improved. Currently, it names them as

nat gateway -> vpc name + some numeric value

,

endpoint -> just id

, and

internet gateway -> vpc name

. • Secondly, private route tables are not being attached to the s3 endpoint automatically, which means we have to attach them manually after creating VPC.

mws_vpc = awsx.ec2.Vpc(
                resource_name=f"test-vpc",
                enable_dns_hostnames=True,
                cidr_block="10.0.0.0/16",
                instance_tenancy="default",
                number_of_availability_zones=3,
                vpc_endpoint_specs=[
                    awsx.ec2.VpcEndpointSpecArgs(
                        service_name="com.amazonaws.us-east-1.s3",
                        vpc_endpoint_type="Gateway",
                    )
                ],
                nat_gateways=awsx.ec2.NatGatewayConfigurationArgs(
                    strategy=self.vpc_nat_gw_stategy.get("single")
                ),
            )

What's the bug?

@little-cartoon-10569 yes its typo fixed it. I mention the two issues in the above message

The first point isn't a bug, though you could raise a change request. Is the 2nd point a bug? Are route tables being created and then not used?

• Why first one is not a bug, if the awx doesn't provide a option to name the resources created along with it thent it should take care of naming them better right. • yes route tables get created by awsx, but they are not getting attached to the s3 endpoint which also get created along with VPC.

The first one isn't a bug because everything is working as intended. You're suggesting an improvement, not a fix. "Bug" means broken, which is different from I want it to work differently.

Still not sure i agree with you for the first one because its broken by not setting proper resource name to the aws resources that it creates and not tagging them.

awsx

package follows best practice and does most of the setup for you, so it doing things but few things are broken. If i ask to extend the feature then its different.

Well, I use it, and so do many others, and it has not been raised as a problem before. It's good enough that people are able to use the library as-is.

@little-cartoon-10569 again not trying to argue, If the resources create by a package (

aws

) is not named properly or tagged properly its a bug, so bring to attention and fixing it improve the library better that s all trying to do here.